Mail Filter — last updated 12 September 2026
Mail Filter runs entirely on one personal computer. It reads the owner's own Gmail messages in order to print a digest on that same computer. No email data is transmitted to the developer, to any server, or to any third party.
The app requests a single Google API scope,
https://www.googleapis.com/auth/gmail.readonly, which is
read-only. For recent messages it reads the sender, subject, date and a short
preview snippet. It cannot send, delete, label, or otherwise alter any
message, and it does not download attachments.
Sender, subject and snippet are passed to a language model that runs locally on the same computer in order to decide which of four groups a message belongs to. The result is printed as a digest and written to a local log file on that computer. The email content is not used for any other purpose.
Everything stays on the user's own computer:
token.json — the Google authorisation token, so the app need not ask permission every runlast_run.json — the timestamp of the last digest, so messages are not shown twicedigest.log — the digests that have been printedThere is no database, no analytics, no telemetry, and no remote backup. The developer has no access to any of these files.
No data is sold, shared, or disclosed to anyone. No third-party service receives message content. The only network connection the app makes is to Google's own Gmail API, to fetch the user's own mail.
Mail Filter's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Because all data is local, the user removes it by deleting the files listed above. Access can be withdrawn at any time from Google Account permissions, which immediately invalidates the stored token.
Questions about this policy: aryangole07@gmail.com