Privacy Policy

Last updated: April 15, 2026

Tip: use the # next to each section title to copy or share a direct link to that section.

This Privacy Policy describes how the Junk Mail Cleaner browser extension (“Extension,” “we,” “us”) handles information when you install and use it. By using the Extension, you agree to this policy.

1. Who provides the Extension #

The Extension is published on the Chrome Web Store. The developer identity and contact options shown on the store listing are the official ways to reach the publisher of this Extension.

2. Summary #

No publisher servers for your Gmail data. The Extension does not send your Gmail content or metadata to, or store it on, any server operated by the publisher. Mail-related requests go from your browser directly to Google’s OAuth and Gmail API endpoints; copies you see in the UI may also be cached only on your device as described below. That direct, local-first architecture is a core privacy and security property of the product.
The Extension lists unread inbox mail grouped by sender (“Groups”), lets you open a per-sender list of subjects and snippets (“Emails”), search those lists on your device, refresh with incremental updates when possible, and run bulk actions you choose—mark as read or move to Trash—with an undo step when the Extension offers it—all via Google’s Gmail APIs.
We do not sell your personal information. We do not use the Extension to show advertising or to run third-party analytics in the Extension package as distributed.
Processing needed to operate Gmail features happens between your browser, Google’s OAuth and Gmail APIs, and limited local storage on your device—as described below.

3. Information the Extension accesses #

When you sign in with Google and grant permissions, the Extension may access Gmail data needed for its features, including:

Message metadata—for example message identifiers, sender (“From”) information, subject lines, snippets, and internal dates—so the Extension can list unread mail, group by sender, and perform actions you request.
Labels and message state—for example unread status and Trash/Inbox—so the Extension can mark messages as read or move them as you direct.
Subject lines and snippets—shown in the per-sender email list and used for local search (together with sender information) without sending your search text to us or to a separate backend.
Account profile summary—from Gmail’s users/me/profile endpoint (for example total message and thread counts) for the summary shown in the Extension UI.

The Extension requests OAuth scopes consistent with this use, including Gmail read and modify capabilities as required to list unread mail and change labels or trash state. Google’s authentication and API services process requests according to Google’s Privacy Policy.

4. How information is used #

Information from Gmail is used only to:

Display unread senders, subjects, snippets, counts, and related UI in the Extension.
Perform actions you explicitly initiate (for example mark as read, move to Trash, or undo within the snackbar flow when available).
Filter and search sender and message lists entirely on your device (no separate search service).
Open Gmail in a browser tab to a specific message when you choose that action, using standard Gmail web URLs.
Cache limited metadata and indexing data on your device to reduce repeat API calls, support incremental refresh, and improve responsiveness (see below).

We do not use Gmail content to train generalized artificial intelligence models for unrelated purposes. The Extension does not add unrelated functionality beyond managing and displaying Gmail information as described.

5. Local storage on your device #

The Extension uses Chrome’s storage capability to save small amounts of data locally, such as:

Cached Gmail message metadata (for example sender, subject, snippet, and related fields) keyed by message id, to avoid refetching the same data when possible.
A local sender index and related bookkeeping (for example message id sets and checksums) so refreshes can reuse prior results when messages are unchanged.
UI state such as selected senders or messages, the active tab (Groups vs. Emails), and which sender’s messages you were viewing—so selections can persist while the popup is closed and reopened.
A flag indicating whether an initial unread scan has completed, so the Extension can explain first-load vs. later refresh behavior.

This data stays on your device unless you clear extension data or uninstall the Extension, subject to how your browser and Google account manage tokens and caches.

6. Authentication (OAuth) #

Sign-in uses Google OAuth through Chrome’s identity features. Access tokens are handled by the browser and Google as part of the normal OAuth flow. You can revoke the Extension’s access to your Google account at any time through your Google Account permissions or by removing the Extension from Chrome.

7. Permissions explained (Chrome) #

The Extension may declare permissions such as:

identity—to obtain OAuth tokens so the Extension can call Google APIs on your behalf after you consent.
storage—to persist the local caches and light settings described above.
tabs—to open Gmail in a new browser tab when you choose to open a message from the Extension (for example from a message row).
Host permissions for Google APIs, Gmail on the web, and (in the Extension package) fonts—so the Extension can call Gmail APIs, open mail.google.com when you open a message in Gmail, and load UI fonts from Google’s font services.

The Extension does not send your Gmail data or usage events to analytics or advertising endpoints operated by the publisher. Like any extension, technical messages may appear in the browser’s developer console on your machine during debugging; they are not a substitute for a remote analytics product and are not transmitted to us as part of normal use.

8. Marketing website #

The project’s public website (for example pages hosted on Firebase Hosting) is static HTML and CSS. We do not operate a login or account system on that site, and the site does not run first-party analytics or advertising scripts in the shipped pages.

The home page may embed a demo video from YouTube (Google). When you play or interact with the player, YouTube may process data (such as IP address or device information) under Google’s Privacy Policy and YouTube’s privacy information. If you prefer not to load the player, avoid playing embedded videos on our site or use browser controls to block third-party content.

9. Servers operated by the developer #

The publisher does not operate an application backend that receives, processes, or stores your Gmail messages or Gmail-derived metadata. Functionality runs in your browser: API calls use your OAuth token to reach Google’s infrastructure only. Aside from ordinary hosting of static marketing pages (which do not receive your Gmail data through the Extension), we do not provide a service endpoint for the Extension to upload inbox contents, search queries, or usage telemetry tied to your mail.

Google still processes Gmail and account requests on Google’s own systems under Google’s policies; this section refers only to infrastructure operated by the Extension publisher.

If a future version introduces a developer-operated backend that handles Gmail data or identifiers, this policy will be updated before that version is published, and the Chrome Web Store listing will reflect any new data practices.

We do not sell, rent, or trade Google user data. We do not share Gmail message content or Gmail-derived metadata with data brokers, advertisers, analytics providers, or other unrelated third parties.

Google user data is disclosed or transferred only in the following limited cases:

To Google services you authorize: The Extension sends API requests directly to Google (OAuth and Gmail API) to provide the features you request.
On your device: Data may be stored in Chrome extension storage locally on your browser profile so the Extension can function.
If required by law: We may disclose information only when legally required (for example a valid court order or legal process).
Business transfer: If the project is involved in a merger, acquisition, or asset sale, users will be notified before any policy changes affecting Google user data take effect.

Except for the cases above, Google user data is not transferred to external parties.

11. Data protection and security mechanisms #

We apply technical and organizational safeguards designed to protect sensitive data and reduce unauthorized access risk:

Local-first architecture: Gmail data processing happens in your browser extension context, and the publisher does not run a backend that ingests Gmail content.
OAuth 2.0 via Google and Chrome identity: Authentication and token issuance are handled by Google and Chrome identity flows; the Extension does not collect your Google password.
Encryption in transit: Requests to Google APIs are sent over HTTPS/TLS.
Least-privilege access: The Extension requests only scopes and Chrome permissions needed for listed features.
User controls: You can revoke OAuth access in your Google Account and clear extension storage or uninstall the Extension to remove local cached data.

12. Data retention and deletion #

Local caches and flags can be removed by clearing the Extension’s storage or uninstalling the Extension.
Revoking app access in your Google Account stops new API access with that consent.

13. Children #

The Extension is not directed at children under 13 (or the age required by your jurisdiction). Do not use the Extension if you are not old enough to consent to processing of your information where you live.

14. International users #

Google processes data according to its policies and your account settings. If you use Gmail and this Extension, Google’s infrastructure may process data in various regions as described by Google.

15. Changes to this policy #

We may update this Privacy Policy when the Extension or legal requirements change. The “Last updated” date at the top will change, and for material changes we will take reasonable steps to notify users (for example via the Chrome Web Store listing or in-Extension notice where appropriate).

16. Contact #

For privacy questions, use the contact or support channel provided on the Extension’s Chrome Web Store listing (publisher email or support link, if shown).

Junk Mail Cleaner is an independent project and is not affiliated with, endorsed by, or sponsored by Google LLC. Gmail and Chrome are trademarks of Google LLC.