IdleSubs

Privacy policy

How IdleSubs handles information for Google sign-in, subscription discovery and management, and cross-device syncing.

Last updated:

Data handling at a glance

Google sign-in information

Purpose
Identify the account and associate subscriptions: Google account ID, email address, name and profile picture URL.
Where it is processed
Google authenticates you. The ID token is sent to our self-hosted authentication service for verification; account records are stored in Cloudflare D1.

Gmail search results

Purpose
Read sender, subject and date after you click Scan to find candidates, without opening email bodies.
Where it is processed
Processed only on your device; candidates are stored in chrome.storage.local and are not uploaded.

Complete browsing history

Purpose
Discover subscription clues and assess usage locally.
Where it is processed
Complete history is not uploaded. Subscription-related timestamps and automatic check records are included in the sync categories below.

Subscriptions and related activity

Purpose
When sync is enabled: subscriptions, visit timestamps, ordering, automatically checked sites and times, and deletion records.
Where it is processed
Processed by our self-hosted service and stored in Cloudflare D1; removable using “Disable and delete cloud data”.

Sign-in sessions

Purpose
Maintain and manage sessions: session token, creation and expiry times, IP address and browser user agent.
Where it is processed
Handled by our self-hosted authentication service on Cloudflare Workers and Cloudflare D1.

1. Scope and operator

IdleSubs is operated by the IdleSubs product developer, referred to as “we” in this policy. This policy covers subscription management, manual entry, email discovery, history discovery, account sign-in and optional cross-device syncing in the browser extension.

We record time since subscription products were last used to help you decide whether to keep them. We do not automatically cancel subscriptions. The email in section 9 can be used for data deletion requests and questions about their progress.

2. Google sign-in: data and purposes

Google sign-in requests only the basic openid, email and profile scopes. We receive the Google account ID (sub), email address, name and profile picture URL to authenticate you, create or identify your IdleSubs account, display account information and associate the account with its subscription data. The email address, name, Google account ID and picture URL are saved in the account database.

The extension uses chrome.identity.launchWebAuthFlow for Google sign-in and sends the resulting ID token to our self-hosted authentication service. The server verifies its signature before establishing an IdleSubs session. This sign-in flow does not use a Client Secret.

Google sign-in requests no sensitive or restricted scopes and no gmail.readonly permission. It does not read email through the Gmail API or use sign-in to access Google Drive, contacts, calendars or other Google service data. Email discovery is a separate local browser feature described below.

We do not ask you to provide your Google password to IdleSubs. Google sign-in data is not used for advertising, data sales, credit assessment or purposes unrelated to the product.

3. Email discovery and browsing records

Email discovery does not use the Gmail API. Only when you click Scan does the extension use the optional https://mail.google.com/* site permission to read sender, subject and date from search result lists on the Gmail page already signed into in your browser. It does not open email bodies.

Scanning and analysis happen locally. Candidate scan results are stored only in chrome.storage.local and are not uploaded. Candidates do not prove payment; you can review them and add products to your subscription list. Added subscription records become list data and sync as described in section 4 if you enable cloud syncing.

History discovery analyzes browsing records locally to find subscription candidates and assess usage. Complete browsing history is not uploaded. However, subscription-related visit timestamps and sites and times automatically opened by extension checks are uploaded when sync is enabled, as detailed in section 4.

History discovery and subsequent usage tracking are different operations. Email scanning being click-triggered does not mean all usage tracking is click-triggered. Browser observations may not cover other devices, browsers or standalone applications.

4. Optional cloud syncing and exact fields

Cloud sync data is stored on the server only after you enable cloud syncing. Google sign-in and enabling sync are separate steps. Even without sync, account and session information is processed as described in sections 2 and 5.

Synced subscription list fields are name, website URL, price, plan, renewal date and last-used date. Manual ordering also syncs so your list can be restored across browsers and devices.

Sync includes the last 90 days of visit timestamps for each subscription. Timestamp entries contain time only, without URLs, but are associated with the relevant subscription. The subscription list itself contains URLs, so these records are not anonymous.

For extension check status and consistency across devices, sync also includes sites and times automatically opened during extension checks (the last 100 days), and deletion records (the last 90 days). Automatic check records contain site information and are separate from the URL-free visit timestamp entries.

5. Accounts, sessions, providers and security

Our self-hosted authentication service uses Better Auth and runs on Cloudflare Workers. Account and cloud sync data is stored in Cloudflare D1. Better Auth is the software used by the service; Cloudflare provides the runtime and database infrastructure. We do not use Supabase or Firebase.

Account records store an email address and name. For password-based accounts, passwords are stored as salted PBKDF2 hashes. Google sign-in accounts also store the Google account ID and profile picture URL. These are separate from your Google password, which we do not receive.

Session records contain a session token, creation and expiry times, IP address and browser User-Agent (UA) to maintain and manage sign-in sessions. Sessions are valid for 60 days and are renewed automatically with daily use. Expiry makes a session invalid; it does not mean its database record has been physically deleted.

The server identifies accounts through authentication and sessions, and passwords use the salted hashing described above. Protect your account and devices and do not share session tokens or verification codes. No system can guarantee absolute security.

Cloudflare processes the account, session and sync data hosted on its infrastructure. Its privacy policy describes platform-related data handling. Messages you send to our deletion email are also processed through Google’s Gmail email service.

Cloudflare privacy policy

6. Use, sharing and Limited Use

IdleSubs will comply with the Google API Services User Data Policy, including applicable Limited Use requirements, in its use of information obtained through Google APIs, including Google sign-in, and its transfer to other applications. We also comply with Chrome Web Store user data and Limited Use requirements, including protections for information read from web pages and derived results.

Information is used only for the disclosed authentication, account profiles, subscription discovery and management, usage assessment, cloud syncing you enable, and the security, operations and user request handling needed for those features. We do not sell user data or use it for advertising, data brokerage, credit assessment or lending.

Google handles sign-in authentication. Cloudflare provides infrastructure for our self-hosted authentication service and database. Data provided to service providers is limited to what the relevant features need. Apart from disclosed features with required consent, transfers are restricted to security or abuse handling, legal requirements, or a merger, acquisition or asset transfer with explicit prior user consent.

Human access is restricted to your explicit agreement to view specific data, security needs, legal requirements or internal operations using aggregated data where applicable policy permits. These provisions do not cause original Gmail search lists or complete browsing history to be uploaded to our servers.

Google API Services User Data PolicyChrome Web Store Limited Use requirements

7. Retention and deletion

Account and general sync records are kept until you delete the relevant cloud data or request account deletion. Synced subscription visit timestamps and deletion records are automatically limited to the most recent 90 days, and sites and times from automatic extension checks to the most recent 100 days. Session validity and renewal are described in section 5.

Delete cloud sync data: when turning off cloud sync in the extension, choose “Disable and delete cloud data”. This immediately deletes the current account’s sync data from the server. It does not delete the account or clear local data from other browsers or devices. If you enable syncing again later, the local list can be uploaded again.

Delete your account: there is currently no self-service account deletion button in the extension. Email towangchuan@gmail.com to request deletion, which the developer performs manually in the database. Account deletion cascades to sessions, password records and synced data. You can ask about progress using the same email; no fixed processing time is currently promised.

“Immediately deletes” and “cascades” refer to operations in the service database, not a promise of immediate erasure of infrastructure backup copies. Backup deletion schedules have not yet been confirmed. Uninstalling, signing out, clearing local data or revoking Google authorization does not replace cloud data or account deletion.

8. Google authorization, browser permissions and choices

You can manage your connection to IdleSubs and revoke authorization in your Google Account. Revocation affects future Google access; it does not automatically delete the account and sync records held by IdleSubs or necessarily terminate an existing IdleSubs session. Use section 7 to request deletion.

Google sign-in authorization and browser site permissions are managed separately. Revoking Google authorization does not mean the extension’s permission to read an already signed-in Gmail page is revoked. You can remove Gmail site access in browser extension settings, disable the extension or uninstall it.

You can review candidates before adding them, view, edit and delete subscription records, and decide whether to enable cloud syncing. Deleting a single local record differs from removing all cloud sync data. To remove all cloud sync data, use the explicit “Disable and delete cloud data” option.

Manage or remove Google Account connections

9. Data deletion and contact

Account and data deletion requests: towangchuan@gmail.com. The IdleSubs developer uses this email to receive and process deletion requests. You can also ask about request progress or data handling related to deletion.

Include your IdleSubs account email and the request so the relevant account can be identified. Identity verification should use only necessary information. Do not send Google passwords, verification codes, ID tokens, session tokens or complete email and browsing records.

towangchuan@gmail.com

10. Policy updates

The latest update date is shown on this page. Material changes to access, purposes, sharing or syncing will be clearly explained before the relevant processing starts, with affirmative consent obtained as required. Continued use does not replace consent required for new sensitive data access.

This policy describes current-version practices. Google authorization screens, in-product notices and actual access should remain consistent with it. We will update this explanation when features change.