Gmail Mass Unsubscribe — Chrome Extension
None. The extension does not collect, transmit, or store any personal data, email content, or usage information.
All processing happens locally in your Chrome browser. When you start an unsubscribe job, the extension makes API calls directly from your browser to Google's Gmail API on your behalf. These calls are authenticated using Chrome's built-in OAuth2 flow — your credentials are handled entirely by Chrome and Google, not by us.
No request passes through any server we own or operate. There is no backend. There is no database. There is no analytics.
The extension requests the gmail.modify scope, which allows it to:
List-Unsubscribe) to find unsubscribe linksThe extension reads the minimum necessary data from each email (headers and body only to find unsubscribe links). It does not read, store, or transmit email content for any other purpose.
Chrome's local storage is used to remember your preferences (limit setting, trash toggle). This data never leaves your device and is not accessible to us.
Your Google OAuth token is managed entirely by Chrome's identity API. We never see, handle, or store your token or credentials.
We share no data with any third party because we collect no data. The extension communicates with two kinds of external services:
List-Unsubscribe header — the request goes directly from your browser to that sender's domain, exactly as if you had clicked "Unsubscribe" yourself. No data about you is sent beyond what that request normally contains.The full source code is publicly available on GitHub. Anyone can audit exactly what the extension does.
If this policy ever changes, the updated version will be posted at this URL. Given the zero-data nature of this extension, we don't anticipate any changes.
Questions? Open an issue on GitHub.