Overview
Shadow Ban is a Chrome extension that manages email filters on your behalf. It operates entirely within your browser and communicates directly with Google's Gmail API. No data is collected, transmitted to, or stored on any external server.
Data Collection
Shadow Ban does not collect any data. Specifically:
- No email content is read beyond sender addresses needed to create filters and move messages
- No data is sent to external servers — the extension communicates only with Google's Gmail API
- No analytics or tracking code is included
- No personal information is gathered
Gmail Access
Shadow Ban requests the following Gmail API scopes. All actions happen directly between your browser and Google's servers:
- gmail.settings.basic — To create and delete Gmail filters that route banned senders' emails away from your inbox
- gmail.labels — To create and manage the "Unsubscribe" label where filtered emails are stored
- gmail.modify — To search for and move existing emails from banned senders out of your inbox on ban, and back into your inbox on unban
Use of Google User Data
Shadow Ban accesses Google user data solely to provide the functionality you requested — banning and unbanning email senders. The extension reads sender addresses to create filters, manages labels to organize filtered emails, and moves messages between your inbox and the Unsubscribe label. Shadow Ban does not use Google user data for any other purpose, including advertising, market research, or profiling.
Google API Services Limited Use Disclosure
Shadow Ban's 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. Specifically:
- Shadow Ban only uses Google user data to provide and improve its email filtering features visible to you in the extension
- Shadow Ban does not transfer Google user data to third parties, except as necessary to provide the service, comply with applicable laws, or as part of a merger or acquisition with notice to users
- Shadow Ban does not use Google user data for advertising or to serve ads
- No human reads Google user data unless you provide affirmative consent, it is necessary for security purposes, or it is required by law
Local Storage
Shadow Ban uses Chrome's built-in storage (chrome.storage.sync) to persist the list of banned sender addresses and filter metadata. This data is stored locally in your browser and synced across your Chrome installations via your Google account. It is never transmitted to any external server. Cleanup queue progress is stored temporarily in chrome.storage.local and cleared when processing completes.
Authentication
Shadow Ban uses Chrome's chrome.identity API to request an OAuth token from Google. The token is managed entirely by Chrome and is used to authenticate API calls to Gmail. No tokens, credentials, or authentication data are stored by or transmitted through the extension beyond Chrome's built-in token management.
Data Retention and Deletion
Shadow Ban stores only the list of banned sender email addresses and associated filter IDs in Chrome's sync storage. This data persists as long as the extension is installed. When you unban a sender, their address is immediately removed. If you uninstall Shadow Ban, Chrome removes all stored data associated with the extension. You may also request deletion of your data at any time by contacting tom@pressware.co.
Data Protection
Shadow Ban is designed to protect your data through the following mechanisms:
- All communication with the Gmail API occurs over HTTPS
- No data is transmitted to or stored on external servers — the extension runs entirely in your browser
- OAuth tokens are managed by Chrome's identity API, not by the extension
- The extension requests only the minimum scopes necessary to provide its functionality
- No email content is read, stored, or cached — only sender addresses are accessed during active use
Third Parties
Shadow Ban does not share any data with third parties. The extension communicates only with Google's Gmail API from your browser. No Google user data is transferred to or processed by external services.
Changes to This Policy
We may update this privacy policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision. Continued use of the extension after changes constitutes acceptance of the updated policy.
Contact
If you have questions about this privacy policy, please contact tom@pressware.co.