Privacy Policy

Last Updated: May 2, 2025

Welcome to Unsubscriber ("we," "us," or "our"). This Privacy Policy explains how we handle your information when you use our web application accessible at [Your App URL] (the "Service"). By using the Service, you agree to the terms outlined in this policy.

Information We Access

When you authenticate with your Google account, we request permission to access certain information from your Gmail account solely for the purpose of providing the Service:

• Email Headers (Read-Only Scope): We access the headers (like 'From', 'Subject', 'Date', and 'List-Unsubscribe') of your recent emails. This is used to identify potential subscriptions and extract unsubscribe links or email addresses. We do not read the body content of your emails with this basic permission level.
• Email Modification (Optional Scope): If you choose to enable the "Archive emails" feature, we request additional permission to modify your emails (gmail.modify scope). This permission is used exclusively to move processed emails from your Inbox to your Archive (by removing the 'INBOX' label). We do not delete emails or modify them in any other way.

How We Use Information

• Identifying Subscriptions: Email headers are scanned locally in your browser or transiently on our server during the scan process to find 'List-Unsubscribe' information.
• Facilitating Unsubscribes: We use the extracted unsubscribe links (HTTP links or mailto: addresses) to help you unsubscribe. HTTP links may be opened directly or processed via a server proxy. Mailto links will typically open your default email client.
• Archiving (Optional): If you grant permission and enable the feature, we use the Gmail API to remove the 'INBOX' label from selected emails after processing unsubscribe requests.

Data Storage and Security

We are committed to protecting your data. Here's how we handle storage and security:

• Transient Processing: We do not store your email content or headers persistently on our servers. Information required for identifying unsubscribe links (email headers) is processed transiently in memory during the scan request within our secure cloud function environment and is discarded immediately after the scan results are provided to you.
• Authentication Tokens: Google OAuth 2.0 tokens (access and refresh tokens) grant the application access to your Gmail data according to the scopes you approve. These tokens are sensitive and are stored securely:
  • Tokens are stored encrypted within your server-side session, managed by our hosting provider's secure infrastructure (e.g., Vercel).
  • Access to these tokens is strictly limited to the necessary application functions for communicating with the Gmail API on your behalf.
  • All communication between your browser, our servers, and Google's servers uses HTTPS encryption to protect data in transit.
• Minimal Scope Usage: We request the minimum necessary permissions (scopes) from Google to perform the app's functions (reading headers, optionally modifying labels for archiving). We do not request broader access than required.
• Compliance: Our data handling practices adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Data Retention and Deletion

We believe in minimizing data retention. Here's our policy:

• Email Data: As stated above, email header data is processed transiently and never stored after the scan request is complete.
• Authentication Tokens: OAuth tokens stored in your session are retained only for the duration of your active session. They are automatically deleted when:
  • You explicitly log out of the Service.
  • Your session expires due to inactivity (as managed by the hosting platform).
• Account Deletion / Revocation: You have full control over the application's access to your Google Account. You can revoke Unsubscriber's permissions at any time via your Google Account settings (https://myaccount.google.com/permissions). Revoking permissions immediately invalidates any stored tokens, effectively deleting the application's ability to access your data.
• Inactive Accounts: While tokens expire with sessions, we do not currently implement a separate process for deleting inactive user *accounts* themselves, as we do not store user account information persistently outside of the session tokens. If you revoke access via Google, the connection is severed.

Third-Party Services

• Google Authentication: We use Google OAuth for authentication. Your interaction with Google is governed by Google's Privacy Policy.
• Hosting: The application is hosted on Vercel. Vercel's privacy policy applies to the infrastructure.
• Analytics: We use Umami for simple, privacy-focused analytics (page views, feature usage) to improve the service. Umami does not use cookies and anonymizes IP addresses.

Your Choices and Rights

• Permissions: You can review and revoke the permissions granted to Unsubscriber at any time through your Google Account settings (https://myaccount.google.com/permissions).
• Logout: Logging out clears your session and stored authentication tokens.

Open Source

Unsubscriber is open source. You can review the code on GitHub to verify how your data is handled.

Changes to This Policy

We may update this Privacy Policy. We will notify you of any changes by posting the new policy on this page. You are advised to review this Privacy Policy periodically for any changes.

Contact Us

If you have any questions about this Privacy Policy, please contact us via [Your Contact Method - e.g., GitHub Issues, Email].