1. Overview
This Privacy Policy explains how the InboxSwift — AI Reply & Email Writer browser extension ("InboxSwift", "we", "our") handles information when you use it in Gmail, Outlook and LinkedIn. The short version: InboxSwift is built so that your data never needs to reach us.
2. Data we do not collect
- We do not collect or store your emails, message threads or generated drafts on any server we operate.
- We do not collect your name, email address, contacts or browsing history.
- We do not use analytics or tracking scripts inside the extension.
- We do not sell, rent or share any personal data with third parties.
- We do not use your content to train AI models.
- No account or sign-up is required to use the extension.
3. Information stored locally on your device
InboxSwift saves the following only in your browser's local extension storage (chrome.storage). This data never leaves your device unless you export it yourself:
- Your settings and preferences (theme, default tone, provider choice).
- Your AI provider API keys (Groq and/or Google Gemini).
- Your templates and custom signatures.
- Your recent draft history and monthly usage counter.
- Your license key and its cached validation status (Pro users).
Uninstalling the extension permanently deletes all of this data.
4. Email content & AI providers
When you press "Generate", the relevant conversation text and your hint are sent directly from your browser to the AI provider you selected and configured with your own API key:
- Groq (api.groq.com) — subject to the Groq Privacy Policy.
- Google Gemini (generativelanguage.googleapis.com) — subject to the Google Privacy Policy.
This happens only when you explicitly trigger a generation. We are not a party to that request, cannot see it, and receive nothing from it. Please review your chosen provider's policy for how they handle API traffic.
5. License validation (Pro)
If you activate a Pro license, the extension periodically contacts our licensing server at cloud.devsarun.io to verify the license. The only information sent is:
- Your license key,
- the product identifier (
inboxswift), and - a random device identifier generated by the extension (it contains no personal information).
No email content, API keys or personal data are ever included. Validation results are cached locally for several hours, and a short offline grace period keeps Pro working without contacting the server.
6. Voice dictation & microphone
Voice dictation is optional. It runs only when you tap the microphone icon and uses your browser's built-in speech recognition. Microphone access is requested through the standard browser permission prompt, audio is processed by your browser, and the extension never records, stores or uploads audio. You can use InboxSwift fully without granting microphone access.
7. Browser permissions, explained
| Permission | Why it is needed |
|---|---|
| Gmail / Outlook / LinkedIn access | To read the conversation you have open and insert your drafts into the compose box. The extension only runs on these sites. |
| storage | To save your settings, keys, templates and draft history locally. |
| sidePanel | To host the writing workspace next to your inbox. |
| Microphone (optional) | Only when you choose voice dictation; never used otherwise. |
8. Security
All network requests made by the extension use HTTPS. Your API keys are stored in Chrome's extension storage, isolated from websites you visit. Because there is no InboxSwift server holding your data, there is no central database of user content that could be breached.
9. Children's privacy
InboxSwift is not directed at children under 13 and we do not knowingly process any data from them.
10. Changes to this policy
If we change this policy, we will update this page and the "Last updated" date above. Material changes will also be noted in the extension's release notes.
11. Contact
Questions about this policy or your data? Reach us at itsdevsarun@gmail.com or visit cloud.devsarun.io.