What Unfair can do with your mailbox
You connect Gmail once, with Google's own consent screen. Unfair asks for one permission, the Gmail scope that lets it read, label and create drafts. It uses it for exactly three things: reading mail as it arrives, putting its labels on it, and placing a draft reply in the thread. Your sent mail is read once, at connection, to learn how you write.
Unfair cannot send email. This is not a setting. The code that talks to Gmail has no send operation, the engine's own mail interface has none either, and an automated test fails the build if a send call ever appears in the source. A draft waits in your drafts folder until you send it, or delete it.
Where it runs
Everything runs on Microsoft Azure in the European Union. The application and its database are in Sweden Central, and the AI models that read and write are called through Azure's EU data zone, so your mail is not processed outside the EU. The models are Azure's; your mail is never used to train them, by Microsoft's terms or by ours.
What it keeps
Unfair keeps what it needs to do the job and no more: the drafts it wrote and what became of them, short summaries of long threads, and the lead record you see in the portal (who the conversation is with, what stage it is at, what was asked and promised). Answers from the models are cached briefly, for a day in most cases and at most seven, and then expire. The mailbox access token is encrypted before it is stored, with keys held outside the database.
Erasing a lead erases everything about that person: the records, the drafts' text, the summaries and the cached answers, in one action. Erasure is final and wins over any write still in flight.
Isolation
Every workspace is isolated from every other one. The database enforces this on every table that holds customer data: a query that is not scoped to a workspace returns nothing, rather than someone else's mail. Our own operations tools show counts, health and settings, never the content of a customer's mail; a test suite keeps it that way.
Who processes data
| Microsoft Azure | Hosting, database, message queue, and the AI models, all in the EU. |
|---|---|
| Gmail, through the Gmail API with the one permission above, and sign-in with your Google account. | |
| Azure Communication Services | The few emails Unfair itself sends to us, such as an access request from this site. Never to your contacts. |
Access and operations
Access to production is held by the two founders, through Microsoft accounts with multi-factor authentication and roles granted per resource. Secrets live in a key vault, not in code or configuration files. Every change to the service goes through a reviewed pull request and an automated build with the tests above before it reaches production.
Status
Unfair is in a closed beta. Before it opens to the public it will complete Google's verification for applications that use restricted Gmail scopes, including the independent security assessment that comes with it.
Questions, or something to report
Write to hello@unfair.app. A security report gets a reply from a founder, and we will say what we did about it.