Privacy Policy
Inbox Referee — AI Tone Coach for Gmail
Effective July 23, 2026 · Last updated July 23, 2026
The short version
Inbox Referee runs entirely in your browser. It has no account and no backend of its own. When you analyse a thread, it sends the cleaned message text plus the minimal context the model needs — the subject line, the sender and your own email addresses, any draft you have open, and the message count — to the one AI provider you choose (OpenAI, Anthropic, or MiniMax), authenticated with an API key only you hold. It never sends your contacts, your wider inbox, or your labels and filters, and there is no analytics or telemetry. There is no SaaS Master server that could receive any of it.
1. Who this policy covers
This policy explains how the Inbox Referee — AI Tone Coach for Gmail browser extension (“the extension”, “we”, “us”) handles your information. The extension is published by SaaS Master (Veeme Media). It applies only to the extension itself.
2. Information the extension accesses — and why
The extension requests only the browser permissions it needs to do its job. Each one is listed below in plain language:
- storage
Save your settings, your API key, the on-device analysis cache, and per-sender stats — all locally.
- sidePanel
Render the analysis panel in Chrome's side panel next to Gmail.
- host: mail.google.com/*
Run the content script that reads the visible thread text from the Gmail page. Nothing else on the page is accessed.
- host: api.openai.com / api.anthropic.com / api.minimax.io
Make the LLM API call to the one provider you configured, using your own key, to produce the analysis and drafts.
3. Where your data is stored
Everything the extension keeps lives in your browser's local extension storage (chrome.storage.local) on your device: your API key (stored as plaintext, used only to authenticate your own provider requests), your settings, a 5-minute per-thread analysis cache, and per-sender stats such as thread count, average tone, and escalation count. None of it is transmitted to us — there is no 'us' server. Removing the extension deletes all of it, and Settings → Purge all data clears it on demand.
4. Network requests
- The only outbound requests go directly from your browser to the single AI provider you configured, and only when you ask it to analyse a thread.
- That request includes the subject line, sender and your own email addresses, the cleaned message bodies (quoted reply history stripped), any draft you have open, and the message count. It never includes your contacts, your inbox contents, your labels or filters, or any analytics.
- There is no SaaS Master backend and no third-party scripts. Per OpenAI's and Anthropic's published API terms, inputs are not used to train their models; your key is sent only as the request's authorization header and is not stored by the provider afterward.
5. What we do not do
- We do not collect, sell, or rent your personal information.
- We do not use analytics or tracking inside the extension.
- We do not require an account, a login, or a subscription.
- We do not transfer your data to third parties for advertising or any other purpose.
6. Data retention and deletion
Because your data lives in your own browser, you are always in control of it. You can clear it at any time from within the extension or by removing the extension, which deletes its local storage. Any files you export are saved by you and are not tracked by us.
7. Children's privacy
The extension is a general-purpose productivity tool and is not directed to children under 13, and we do not knowingly collect any information from them.
8. Changes to this policy
If we make material changes to this policy, we will update the “Effective” date above and post the revised policy at this URL. Continued use of the extension after an update means you accept the revised policy.
9. Contact
Questions about this policy or your data? Email us at [email protected].
Inbox Referee is built by SaaS Master.