Privacy — QuillSend
QuillSend is a send-only mail app. This document states what the app holds, where each thing goes, and what never leaves the phone. Updated in the same pass as the features it describes (v0.1.0, Nov 16, 2026).
The short version
QuillSend has no server. There is no QuillSend account, no analytics, no tracking, and no copy of anything anywhere except the phone and the user’s own Google account. The only connections the app ever makes are to Google — sign-in/OAuth and the Gmail API — because sending through the user’s Gmail account is the app’s job.
The app says this itself, in its own words, on its first-run screen: Google’s consent screens use generic wording that cannot distinguish a local-only app from a server-backed one, so the distinction is stated by the app, before anything is configured.
What the app stores, and where
All of it on the device, in encrypted storage (EncryptedSharedPreferences under a hardware-backed Android Keystore master key; StrongBox requested where the device offers it):
- The email addresses of the connected Google accounts.
- Each account’s OAuth tokens (AppAuth state: access and refresh tokens issued by Google for the drafts/send scope).
- Each account’s linked certificate alias — a reference string.
- The selected account and the sign-by-default setting.
- Whether the first-run disclosure has been seen.
Certificate private keys are never stored by the app at all. The user picks their installed S/MIME certificate in Android’s own certificate picker; the key stays in Android’s KeyChain vault, non-exportable. At send time the app asks Android to sign with that key. Unlinking a certificate removes only the app’s reference; the certificate itself is managed by Android and is untouched.
What leaves the device, and to whom
- To Google only: the OAuth sign-in/consent exchange; Gmail API calls that list, read, create, update, and delete the account’s drafts; and the final send of a message the user composed. Sent mail lands in the account’s normal Sent folder, like any mail the user sends from Gmail.
- To recipients: the sent message itself, including its S/MIME signature and the signer’s certificate chain (that is what a signature is — the recipient’s mail app uses it to verify the mail really came from the sender).
- To nobody else, ever. No other endpoint exists in the app.
The Gmail access is the single restricted scope gmail.compose: create/read/update/delete drafts and send messages. The app cannot read the inbox, search mail, change labels or settings, or do anything else in the account — it never asks for those permissions.
Backup and transfer
Cloud backup is off (allowBackup=false plus data-extraction rules excluding everything, for both cloud backup and device-to-device transfer). Configuration does not silently ride into a Drive backup or onto a new phone; setting the app up again on a new device is deliberate: connect the account, link the certificate.
Removing things
- Removing an account in Settings erases that account’s tokens and certificate link from the device. The Google account and its Gmail drafts are untouched.
- Uninstalling removes all app storage. The OAuth grant itself can also be revoked at any time in the Google account’s third-party access settings — that is Google’s surface, and it works whether or not the app is installed.
Signing, honestly
A signature proves the mail came from the holder of the certificate. It does not encrypt or hide the message’s contents, and QuillSend never claims otherwise — the distinction is stated on the first-run screen and in the app’s store copy. Encryption is a possible later version; v1 signs only.