← The Marvellous Suspender
The Marvellous Suspender · Legal

Privacy Policy

Effective 5 November 2026

01 // Data Controller

Giovanni Solone ("Marvellous Codeworks")

E-mail: privacy@marvellouscode.works

02 // Data We Process

The Marvellous Suspender ("TMS" or "the Extension") does not send tabs, sessions, settings or backups to Marvellous Codeworks servers: this data remains exclusively on the user's device or in their personal Google Drive account. The only exception concerns OAuth credentials on browsers where Chrome's built-in sign-in is unavailable, as described under "Third Parties — Cloudflare".

Tab URLs and session structure — when the Google Drive backup feature is enabled, TMS saves a JSON file containing the URLs of open tabs and the window/group structure. The file is written directly to the user's Google Drive account.

Extension settings — stored locally via chrome.storage.local.

Session history — stored locally in the browser's IndexedDB database.

OAuth credentials — on browsers where Chrome's built-in sign-in is unavailable (such as Brave and Vivaldi), connecting Google Drive makes TMS save a Google refresh token in the browser's local storage and keep the access token in session storage, which is cleared when the browser closes.

03 // Purpose

Data is processed solely to enable backup, restoration and management of browsing sessions. No profiling, statistical analysis, advertising or any other processing for commercial purposes is performed.

04 // Legal Basis

Processing is based on the user's explicit consent (Art. 6(1)(a) GDPR), expressed when activating the Google Drive backup feature and granting OAuth authorisation through their Google account.

05 // Third Parties — Google Drive

TMS uses the Google Drive API to save backup files in the user's Google account. Backup files are transmitted directly between the user's browser and Google LLC's servers; Marvellous Codeworks neither receives nor accesses them. Google's Privacy Policy and Terms of Service apply (policies.google.com/privacy).

The OAuth scope requested is drive.appdata: TMS can access only a hidden, app-specific folder in the user's Drive account, not the other files stored on Drive.

06 // Third Parties — Cloudflare

On browsers where Chrome's built-in sign-in is unavailable (such as Brave and Vivaldi), TMS obtains and renews its Google OAuth tokens through tms-oauth-proxy, a Cloudflare Worker operated by Marvellous Codeworks that adds the OAuth client secret and forwards the request to Google. This component is not used on Chrome.

The authorization code, the refresh token and the access token returned by Google pass through the Worker, hosted by Cloudflare, Inc., only for the duration of each request. The Worker does not store these values, does not log the content of requests and responses, and never receives backup files or other Drive content.

Cloudflare may process technical request metadata, such as IP address, date and time, and status code. Cloudflare's Privacy Policy applies (cloudflare.com/privacypolicy). The Worker's source code is public: github.com/Marvellous-Codeworks/tms-oauth-proxy.

07 // Data Retention

Backup files on Google Drive remain in the user's account until manually or automatically deleted (by default TMS retains the last 10 automatic backups). Local data (settings, sessions) remains on the device until the extension is uninstalled or deleted via the settings. OAuth credentials saved locally are removed when the user disconnects their Google account from TMS or uninstalls the extension.

08 // User Rights

Under Arts. 15–21 GDPR, users have the right to access their data, rectify or delete it, object to processing or request restriction, and withdraw consent at any time by revoking OAuth access from TMS settings or from the "Apps & services" section of their Google account.

You may lodge a complaint with your local supervisory authority. In Italy: Garante per la Protezione dei Dati Personali — garanteprivacy.it.

09 // Security

On Chrome, the OAuth token is managed by the browser. On the browsers described under "Third Parties — Cloudflare", tokens are kept in the extension's storage inside the browser. TMS never receives the user's Google password. Data transfer to Google Drive and to the Worker uses HTTPS encrypted connections.

10 // Changes to this Policy

Any updates will be published at this URL. Continued use of the extension after updates are published constitutes acceptance of the changes.

11 // Contact

For any privacy-related requests: privacy@marvellouscode.works

For technical reports: github.com/gioxx/MarvellousSuspender/issues

Last updated: 5 November 2026 · Giovanni Solone ("Marvellous Codeworks")