Introduction
Welcome to Gmail to Slack ("we," "our," or "us"). We are committed to protecting your privacy. This Privacy Policy explains how our Chrome Extension collects, uses, and safeguards your information when you use our services to clip web content, take screenshots, and save Gmail threads directly to Slack.
1. Information We DO NOT Collect
Zero Content Retention: We do not read, log, or store the contents of your web clips, your screenshots, or your private Gmail emails on our servers.
All core functionalities (compiling emails, capturing screen data, and extracting web text) are performed locally within your browser. When you click "Save," this data is transmitted securely and directly from your browser to Slack's official API. It never passes through our databases.
2. Information We Collect
To provide you with a seamless and secure experience, we collect the following limited data:
- Authentication Data: When you connect your Slack account, we use secure OAuth 2.0. We store your Slack User ID, Name, and Email address securely in our backend database (powered by Supabase) to maintain your connection and subscription status.
- Anonymous Usage Analytics: We use Google Analytics 4 (GA4) to track non-personally identifiable usage data. This includes events like extension installations, uninstalls, and generic button clicks (e.g., "Save Clip", "Take Screenshot") to help us improve the extension.
- Local Storage Data: We store your Slack channels, recent destinations, and active tokens locally on your device's browser using Chrome's secure `chrome.storage.local` API for faster load times.
3. Chrome Extension Permissions Justification
Our extension requires specific permissions to function. Here is exactly why we request them:
activeTab&scripting: Required to capture the title and URL of the current page, and to execute the screenshot-capture logic on the visible tab.identity: Required to securely launch the Slack OAuth login flow without exposing your credentials.storage: Required to cache your Slack channels and Direct Messages locally so the extension opens instantly.- Host Permissions (
mail.google.com,slack.com): Required to inject the floating "Save Thread" widget exclusively into your Gmail interface, and to transmit your saved content to Slack.
4. Third-Party Services
We utilize trusted third-party infrastructure to operate the extension:
- Slack API: To authenticate your account and receive the messages, files, and screenshots you choose to send.
- Supabase: To securely handle the OAuth token exchange and manage user authentication records.
- Google Analytics: To monitor overall extension health and feature usage.
5. Data Retention and Deletion
You have full control over your data. If you wish to revoke our access:
- Open the extension and navigate to the Settings tab.
- Click Disconnect. This will immediately flag your account as uninstalled in our database and wipe all tokens and cached data from your local browser.
- You may also revoke the app's permissions directly from your Slack Workspace settings at any time.
6. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. Any updates will be reflected on this page.
7. Contact Us
If you have any questions, concerns, or feature requests regarding this Privacy Policy or the extension, please reach out to us via our official feedback channel: