Adinand Email Cleaner

Privacy Policy — Adinand Email Cleaner

Last Updated: October 25, 2026

Adinand Email Cleaner was previously published as Zen Inbox Cleaner; this document applies to the app under both names.

At Adinand Email Cleaner, we value your privacy and your peace of mind. Our app is built on the principle that your email data belongs to you. This Privacy Policy explains our commitment to transparency and how we handle your information.

1. Our Privacy-First Approach

Adinand Email Cleaner comes in four forms: the iOS app, the Android app, the Google Workspace add-on for Gmail (§10 describes the add-on), and the Chrome extension (§11 describes the extension). On iOS and Android, your email data stays inside your Google account and on your device — we operate no servers, databases, or cloud infrastructure that touch user data, all processing occurs on-device, and your email content never reaches any system we control. The Workspace add-on works differently, and §10 describes it in full: it is Apps Script code that runs on Google's own servers inside your Google account, not on your device. In all four, we operate no server of our own and your email content never reaches any system we control. The only narrow exception is a small free-tier usage counter (a tally of emails cleaned (trashed, archived or labelled) and bytes recovered — never any email content), which on iOS may sync across your own Apple devices through Apple's iCloud Keychain if you have it enabled. That stays entirely within your personal Apple account and never reaches us or any third party. See §4 for details.

2. Data We Access

Adinand Email Cleaner only accesses the data strictly necessary to help you manage your inbox:

Adinand Email Cleaner does not access or store email body content or attachments.

The list above describes the iOS and Android apps. The Workspace add-on reads headers only, never message bodies, and §10 says exactly what it reads. The Chrome extension also reads headers only, and §11 says exactly what it reads.

3. OAuth Scopes Requested

The iOS and Android apps request three Google OAuth scopes at sign-in, and the Chrome extension requests the same three. The Workspace add-on requests four: the same three, plus https://www.googleapis.com/auth/gmail.addons.execute, which is what allows an add-on to run inside Gmail at all. See §10. These scopes support the following functionality:

The app requests only the permissions essential to its core functionality. The optional Pro in-app upgrade does not require any additional Google OAuth scopes; it is handled by the platform's built-in App Store (iOS) and Google Play (Android) services.

4. Local Data Storage

The app does not log access tokens, refresh tokens, email bodies, or personally identifying message content.

5. Data Deletion & Account Revocation

Because Adinand Email Cleaner operates on-device and does not create or store user accounts on external servers, "deleting" your account is a matter of revoking permissions and clearing local data. You have several paths to do this — all of them are under your control.

Cleanup Rules (Gmail filters). If you created any Cleanup Rules, the underlying Gmail filters remain on your Google account even after you sign out, revoke access, or uninstall the app. To remove them either delete them from within the app (the Rules screen → tap a rule → Delete) before signing out or uninstalling, or remove them later from Gmail directly (Settings → Filters and Blocked Addresses).

Email recovery. Nothing is permanently deleted by the app. Emails the app moves to "Trash" remain there for 30 days under Google's standard Gmail retention policy, during which you can restore them from the official Gmail app or website.

Because Adinand Email Cleaner operates entirely on-device, there is no server-side data to retain or dispose of.

6. Unsubscribe Functionality

Adinand Email Cleaner offers an optional unsubscribe feature that follows the unsubscribe method specified by the sender in their email headers (List-Unsubscribe and List-Unsubscribe-Post, per RFC 2369 and RFC 8058). When you tap "Unsubscribe," the app uses the most direct method the sender supports, in this order:

  1. One-click unsubscribe (RFC 8058). If the sender supports one-click unsubscribe, the app sends a single standard HTTP POST request to the sender's unsubscribe URL on your behalf. The request body contains only the List-Unsubscribe=One-Click form parameter required by RFC 8058. No personal data, no Gmail or Google credentials, no Authorization header, and no tracking identifiers are included. (Android additionally sends a standard User-Agent: Zen-Inbox-Cleaner/1.0 HTTP client identifier, which identifies the application — not you.) The request is sent directly from your device to the sender; we have no servers involved.
  2. Browser redirect. If one-click unsubscribe is unavailable or fails (any non-2xx HTTP response), the app opens the sender's official unsubscribe webpage in your device's secure in-app browser — SFSafariViewController on iOS, Chrome Custom Tabs on Android. You then complete the unsubscribe yourself on the sender's website.
  3. Email (mailto:) fallback. If neither of the above is available, the app opens an email composer pre-filled with an unsubscribe message addressed to the sender — presented in-app on iOS via the system MFMailComposeViewController using your default Mail account configuration, or handed off to your chosen mail client on Android via a standard mailto: intent. You review and send the email yourself.

In all three cases, the actual processing and honoring of the unsubscribe request is performed by the sender, not by Adinand Email Cleaner. We do not collect, store, or transmit any additional personal data as part of this process beyond what is already present in the email's unsubscribe headers and what the sender's own unsubscribe mechanism requires.

7. Third-Party Sharing and Ads

No external servers operated by us. Your device talks directly to the Gmail API.

Third-party dependencies are limited to well-known libraries:

The optional Pro upgrade introduced no analytics, attribution, advertising, crash-reporting, or third-party billing-platform SDKs (such as RevenueCat) on either platform — purchases are handled solely by Apple's first-party StoreKit (iOS) and Google's Play Billing Library (Android). All dependencies are kept up to date to incorporate upstream security fixes.

8. Google API Services User Data Policy — Limited Use

Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

9. Data Protection Mechanisms for Sensitive Data

We treat the following as sensitive: OAuth access tokens, OAuth refresh tokens, the cached email-metadata store, the sender-intelligence index, your Google account email address, and your cleaning history. The mechanisms below protect those categories at rest, in transit, and operationally.

9.1 Protection at rest

9.2 Protection in transit

9.3 Operational protection

We continuously review these practices to ensure user data remains protected against unauthorized access, alteration, disclosure, or destruction.

If we ever become aware of an incident that may have exposed user data, we will notify affected users without undue delay and, where required, the appropriate authorities, in line with applicable data-protection law.

If a vulnerability is discovered in the app, we will publish a patched release through the relevant app store and, where appropriate, notify affected users through the app or our support email.

10. Google Workspace add-on for Gmail

Availability. The Workspace add-on is available to install, free, from its Google Workspace Marketplace listing. This section describes what it does, so that you can check it against the add-on.

Where it runs. The add-on is Google Apps Script code that runs on Google's servers inside your own Gmail account. We operate no server of our own, and the add-on makes no outbound network calls of any kind — none to us, to any analytics service, or to any third party.

What it reads. When you open an email, the add-on reads two headers of that message: From and List-Unsubscribe. It requests message metadata only and never reads message bodies or attachments. To count and to move email it reads the message IDs that Gmail's own search returns, and nothing else about those messages. To show its Cleanup Rules it reads your list of Gmail filters.

What it stores. Nothing about you is stored on any system we operate, because we operate none. The add-on holds two short-lived items in your own Google account's script cache for six hours: the message IDs of the batch you just moved to Trash, so that Undo can restore them, and the sender counts it just measured, so that reopening the same email does not re-count it. Both expire on their own. There is nothing to export and nothing to delete when you uninstall, because nothing persists beyond that window.

What it changes. The add-on makes exactly two kinds of change to your mailbox, and only after you confirm. It moves the messages you chose to Gmail's Trash, where Gmail keeps them for 30 days before deleting them permanently. And, if you ask for it, it creates a Gmail filter that moves future email from that sender to Trash — a filter you can see and delete yourself in Gmail's Settings, and which the add-on can also remove for you. It never deletes email permanently, never sends email, never archives, never applies labels, and never reads or changes anything else.

Your account address. The add-on reads the email address of the signed-in account so it can show you which account you are working in. No other profile information is requested.

Unsubscribing. Where a sender publishes an unsubscribe link, the add-on shows a button that opens that link in your own browser. The add-on does not fetch the link, does not send an opt-out request on your behalf, and sends no email. This is narrower than the iOS and Android apps, which do send one-click opt-out requests as described in §6.

Demo mode. The add-on includes a demo that runs on twelve fictional sample senders. In demo mode it makes no Gmail calls at all and changes nothing in your mailbox.

11. Chrome extension

Availability. The Chrome extension runs in Google Chrome on a computer. This section describes what it does, so that you can check it against the extension.

Where it runs. The extension runs inside Chrome on your computer. We operate no server of our own. The extension connects only to Google's Gmail API and Google's sign-in service, and to a sender's own unsubscribe address when you choose to unsubscribe (see "Unsubscribing" below). It contains no analytics, tracking, advertising or crash-reporting code, and it sends nothing to us.

Signing in. You sign in through Chrome's own Google sign-in, and the extension requests the three scopes listed in §3. Chrome keeps the sign-in token; the extension holds it in memory while it works and never writes it to storage.

What it reads. For each email in your inbox, the extension reads its message ID, its From and Subject headers, its date and size, and whether it has a List-Unsubscribe header (the header's value is not kept). It requests message metadata only and never reads message bodies or attachments. When you clean a sender, it lists the message IDs of every email from that sender's domain, including archived ones, and nothing else about them. When you choose to unsubscribe from a sender, it reads that sender's List-Unsubscribe and List-Unsubscribe-Post headers from one message, uses them once and does not store them. To show its Cleanup Rules it reads your list of Gmail filters. To keep each account's free allowance separate, it reads your Gmail address from Gmail.

What it stores. The list of senders it builds is held in memory and is gone when you close the extension's page. The only thing the extension writes to your computer is your free-allowance counter, in Chrome's local extension storage, filed under your Gmail address: the number of emails cleaned and, once your first 2,500 are used, the date your current monthly allowance began and the count at that date (the record also has a bytes field, which the extension leaves at zero). It never contains any email content, sender or subject, and it is never written to Chrome sync. Signing out does not erase it. Removing the extension does: Chrome's documentation says local extension data is "cleared when the extension is removed" (Chrome storage API reference, read 23 October 2026).

What it changes. The extension changes your mailbox only after you confirm. It moves the emails you chose to Gmail's Trash, where Gmail permanently deletes them after 30 days (Gmail Help, "Delete messages in Gmail", read 23 October 2026), or archives them, which removes them from your inbox and leaves them in All Mail. If you ask for it, it creates a Gmail filter that moves a sender's future email to Trash or archives it — up to three of these Cleanup Rules — which you can see and delete yourself in Gmail's Settings, and which the extension can also remove for you. It never deletes email permanently, never sends email, and never applies labels.

Unsubscribing. When you choose to unsubscribe from a sender, the extension uses the method the sender publishes, in this order. If the sender supports one-click unsubscribe (RFC 8058), it sends one request to the sender's unsubscribe address containing only List-Unsubscribe=One-Click, with no Google credentials, no cookies and no referrer. Otherwise it opens the sender's unsubscribe page in a new Chrome tab, where you finish yourself. If the sender offers only an email address, it opens your own email program with the unsubscribe message for you to send.

Signing out. Signing out clears the token Chrome holds for the extension and asks Google to revoke the extension's access. You can also remove its access at any time from your Google Account's security settings. Cleanup Rules you created stay in Gmail until you delete them, in the extension or in Gmail's Settings.

Links to this website. The extension's "Privacy policy" and "Get the app" links open pages of this website in a new tab when you click them. The extension does not fetch these pages itself. Visits to this website are counted as described in §7.

Demo mode. The extension includes a demo that runs on twelve fictional sample senders. In demo mode it makes no Gmail calls, stores nothing and changes nothing in your mailbox.

Limited Use. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. §8 applies to the extension as it does to the apps.

12. Children's Privacy

Adinand Email Cleaner is not directed to children under the age of 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information through use of the app, please contact us and we will take appropriate steps to address the matter.

13. Contact

If you have any questions about this Privacy Policy or how your data is handled, please contact us at: support@adinandemail.com