Privacy Policy

Unsubscriber (“we,” “our,” or “us”) is an inbox-control tool for Gmail. It helps you see who emails you, create Gmail filters, attempt unsubscription where email headers support it, and review a read-only history of actions taken in the app.

This Privacy Policy explains what information we collect, how we use it, and your choices. It applies to your use of unsubscriber.me and all associated features.

By using Unsubscriber you agree to this policy. If you do not agree, please do not use the service.

We collect information in two categories:

A. Account and identity information

When you sign in with Google, Firebase Authentication receives your Google account ID, email address, and display name. We store your Firebase user ID (UID) as your account identifier.

B. Gmail mailbox information (only after you connect Gmail)

Connecting Gmail is a separate step from signing in. When you connect, we request read access to your Gmail account. If you later use the Filters feature, you may grant additional permission for the app to create and manage Gmail filters on your behalf. We collect:

• OAuth tokens — your Gmail access token and refresh token, stored server-side in Firestore to allow the app to sync your mailbox. Tokens are stored with application-layer access controls and are used only to call the Gmail API on your behalf.
• Email metadata — for each message fetched, we store: sender address and display name, subject line, a short message snippet (provided by Gmail, typically ~100 characters), date received, read/unread status, Gmail thread ID, and List-Unsubscribe header values when present.
• Sender aggregations — we group messages by sender and store counts, latest activity dates, and classification signals (deal-like, receipt-like) derived from metadata.
• Gmail filter data — when you use the Filters feature, we store a snapshot of your Gmail filters so the app can display which senders are covered.
• Action history — we maintain an append-only log of actions the app performed: filter creations, unsubscribe attempts, permission changes, and related events.
• Sync state — technical metadata tracking which messages have been indexed and where a sync was paused.

We use the information we collect solely to operate the service:

• Authenticate you and protect your account via Firebase Auth
• Fetch and display your Gmail senders, message counts, and recent activity
• Enable you to create, view, and manage Gmail filters from within the app
• Attempt list-unsubscribe requests on your behalf when message headers provide a supported mechanism
• Show you a read-only history of actions the app performed
• Provide optional beta views (Deals, Receipts) that classify messages using heuristics for triage purposes
• Maintain and improve the service

We do not use your Gmail data to build advertising profiles, sell to third parties, or for any purpose unrelated to providing inbox-control features directly to you.

Unsubscriber’s use of Google user data is governed by the Google API Services User Data Policy, including the Limited Use requirements.

Specifically:

• We request Gmail permissions only for features you choose to use. Initial Gmail connection requests read-only access only. Creating or restoring filters requests broader Gmail access only when you confirm that action. Viewing existing filter rules without creating new ones may request a narrower settings permission when you choose that option in the app.
• We use Gmail data to provide inbox organization features — grouping senders, surfacing filter options, and logging app-initiated actions. We do not use this data for purposes beyond operating the service.
• We do not sell, rent, or share your Google account data with third parties for advertising or unrelated purposes.
• You can revoke Gmail access at any time from within the app (Disconnect Gmail) or from your Google Account permissions page.
• Disconnecting from within the app removes our stored OAuth tokens (and asks Google to revoke the grant when possible), and deletes all mailbox-scoped data we stored. Gmail filters you created through the app remain in your Gmail account until you remove them in Gmail directly.
• We do not use Google user data to train machine learning models used outside of delivering our service to you.

We store the following data in Google Firestore:

• Your Firebase UID and linked Google email address
• Gmail OAuth access token and refresh token (server-side only, not exposed to the browser)
• Email metadata per message: sender address, display name, subject, Gmail-provided snippet (~100 characters), received date, read status, thread ID, and List-Unsubscribe header values
• Sender-level aggregations: message count, latest date, unread count, classification signals
• A snapshot of your Gmail filters (for filter-aware sender display)
• An append-only action log of app-initiated events (filter create, unsubscribe attempt, etc.)
• Sync state metadata (pagination cursors, sync status flags)

• Full email bodies. We never store complete message body content on our servers. Message previews visible in the app use the short snippet Gmail provides in metadata, or are loaded on-demand directly from Gmail into your browser when you choose to open a preview — and are not persisted to our database.
• Email attachments. We never access or store attachments.
• Sent mail or drafts. We only access your inbox and message metadata; we do not read sent mail or drafts unless required for a specific feature you initiate (such as a mailto unsubscribe handoff, which opens your local mail app and is not sent by us).
• Passwords. Authentication is handled entirely by Google and Firebase Auth. We never see or store your Google password.
• Payment information. Unsubscriber currently has no paid features and does not collect payment data.

When you create a Gmail filter through Unsubscriber, that filter is created in your actual Gmail account via the Gmail API. It is your filter, governed by your Google account. We store a reference copy in our database to display it in the app; disconnecting from Unsubscriber deletes our copy but does not remove the filter from Gmail.

When you restore a sender, the app may delete Gmail filters that Unsubscriber created for that sender. It does not remove filters you created directly in Gmail or change messages already labeled by those filters.

Unsubscribe actions work as follows:

• HTTP unsubscribe:When a sender’s message headers contain a List-Unsubscribe URL, the app sends an HTTP request to that URL from our server on your behalf after you confirm (required for RFC 8058 one-click POST). A successful response does not guarantee you will stop receiving mail; that depends on the sender honoring the request.
• Mailto handoff: When headers only provide a mailto: address, the app opens your local mail application with a pre-filled draft. We do not send that email for you. The action log records that the handoff was initiated, not that an email was sent.

Unsubscriber uses the following third-party services to operate:

• Google Firebase (Auth, Firestore, App Hosting)— authentication, database, and hosting. Your data is stored in Firestore under Google’s infrastructure and subject to Firebase’s Privacy and Security terms.
• Google Gmail API — fetching message metadata and managing filters on your behalf, subject to Google API Terms of Service.
• Google Cloud Platform — the underlying infrastructure for the above services.
• Google Analytics (Firebase Analytics) — optional, privacy-oriented product telemetry when enabled in our deployment (funnel and reliability events only; no email content, subjects, bodies, or message identifiers). Governed by Google’s Privacy Policy. You can limit collection via browser/Google privacy settings; we do not use this data for advertising.

We do not use advertising networks, behavioral ad retargeting, or social tracking pixels.

We retain your data for as long as your account is active or as needed to operate the service. Specifically:

• Disconnecting Gmail in the app deletes your stored Gmail OAuth tokens and all mailbox-scoped data from our database — including messages, sender aggregations, filter snapshots, and the action log. We attempt to revoke the grant with Google when possible.
• Revoking access only in Google Account settings stops new Gmail API access but does not automatically delete data we already stored. Use in-app Disconnect or contact us for deletion.
• Firebase Auth account (your sign-in identity) is not deleted automatically when you disconnect Gmail. If you want your Firebase Auth record removed, contact us at privacy@unsubscriber.me.
• We may retain anonymized or aggregated usage data that cannot reasonably be linked to an individual for service improvement.

We take reasonable precautions to protect your data:

• All communication between your browser and our servers uses HTTPS.
• Gmail OAuth tokens are stored server-side only and are never sent to the browser.
• API routes verify your Firebase ID token before processing any request.
• Firestore security rules deny all direct client-side access; all reads and writes go through our server-side API with authentication checks.

No method of internet transmission or electronic storage is completely secure. We cannot guarantee absolute security, but we implement industry-reasonable practices appropriate for an early-stage product.

• Don’t connect Gmail: You can sign in to Unsubscriber without connecting Gmail. The app will prompt you to connect when you want to use inbox features, but you are not required to.
• Disconnect Gmail: Use the Disconnect option in the app to revoke our OAuth access and delete your mailbox data.
• Revoke via Google: Visit myaccount.google.com/permissions to revoke access at any time. This disables our ability to access your Gmail but does not automatically delete data we already stored. Contact us if you want that data deleted.
• Data deletion request: Email privacy@unsubscriber.me to request deletion of your account and any associated data we hold.

Unsubscriber is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe we have inadvertently collected such information, contact us and we will delete it promptly.

Unsubscriber is operated from the United States. If you access the service from outside the United States, your information will be transferred to and processed in the United States. By using the service, you consent to that transfer. We do not make specific representations about compliance with laws of other jurisdictions (such as GDPR or CCPA) at this stage of the product.

We may update this Privacy Policy as the product evolves. When we make material changes, we will update the effective date at the top of this page. Continued use of the service after changes are posted constitutes acceptance of the updated policy.

Questions about this policy? Email us at privacy@unsubscriber.me.