Privacy policy
emailz is a single-user personal application, operated by one individual against his own Gmail mailboxes. This policy describes what it accesses, why, and where that data goes.
Who this covers
There is exactly one user: Andrew Popov, who is also the developer and operator. The application is connected to three mailboxes, all belonging to him. It is not distributed, not offered to the public, and has no mechanism by which another person could connect an account. If you have arrived here without owning this application, none of your data is involved.
What Google data it accesses
emailz requests a single Google permission,
https://www.googleapis.com/auth/gmail.modify. That scope is used for these
purposes and no others:
| Capability | Why it is needed |
|---|---|
| Read message headers and previews | To compose the daily digest of what arrived, and to answer the owner's questions about his own inbox. |
| Apply and remove labels | To archive a message, mark it as read, or file it under a label when the owner asks. |
| Move messages to trash | To discard a message when the owner asks. Messages go to Gmail's trash; the application never permanently deletes mail. |
| Read a Google Voice mailbox | Google Voice delivers each inbound text message as an ordinary email. Reading that mailbox is how text relaying works, because Google Voice has no push API. |
The application never sends email as the user, and never permanently deletes anything.
Where the data goes
On the owner's own hardware
The application runs on a small server in the owner's home. Message data it retains — conversation history and its own operational logs — is stored locally in a SQLite database on that machine. It is not hosted with any third-party provider.
Sent to a language model API
This is the one place data leaves the owner's hardware, and it is stated plainly rather than buried. To write the daily digest, the application sends the sender address, subject line, and a truncated preview snippet of recent messages to a large language model API (Anthropic's Claude API) so that it can be summarised into a few sentences.
Full message bodies are never sent. Attachments are never sent. The summarising prompt explicitly instructs the model to treat all mail content as untrusted data, to follow no instruction contained inside an email, and never to reproduce a one-time passcode, verification code, or password-reset link.
Nowhere else
Google user data obtained through this application is never sold, never used for advertising, never used to train any model, and never shared with any other person or service.
Retention and deletion
Retained data lives in a local database that the owner controls and can delete outright at any time. Revoking the application's Google access immediately ends all further reading and all triage.
Limited Use
This application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access
Access can be withdrawn at any time from Google Account permissions, with no action required on this side.
Contact
Questions about this policy: andrewvpopov@gmail.com.