Privacy policy

Applies to mail-triage. Last updated October 5, 2026.

Who uses it

mail-triage is a personal tool built and used by its owner for the owner's own two Gmail accounts. It is not offered to anyone else, and no other person's account is connected to it.

What Google data it accesses

With the owner's authorization, mail-triage uses the Gmail API scopes gmail.modify and gmail.settings.basic to read message headers, snippets and labels; to apply labels, archive, star and move mail to Trash; to send the owner's own digest email; and to create and remove Gmail filters. It cannot permanently delete mail. It does not read attachments.

Where the data goes

• Processing runs on the owner's own computer. Sorting state is stored locally there. OAuth tokens are stored in the macOS Keychain.
• For mail from unknown senders, the sender address, subject, a short snippet, whether a List-Unsubscribe header is present, and Gmail's inbox category are sent to one AI model provider (Anthropic or OpenAI) solely to choose a label. These providers do not use API data to train models by default.
• Push alerts sent through ntfy.sh contain no message content, only a label name and an account tag.
• For an unsubscribe the owner has approved, a single standard one-click unsubscribe request (RFC 8058) may be sent to the sender's own unsubscribe address.

What it never does

Gmail data is not sold, shared for advertising, or transferred to anyone other than as described above. mail-triage's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Removing access

The owner can revoke access at any time at myaccount.google.com/permissions, which stops all processing. Local state can be deleted from the owner's computer.

Contact

privacy@digitalframeworks.org