Privacy policy

gmail-dispatcher — last updated 29 August 2026.

gmail-dispatcher is a private tool with a single user: its author, who is also the owner of the only Google Account it ever accesses. This policy describes how it accesses, uses, stores and shares Google user data.

What data is accessed

The application requests these OAuth scopes:

• https://www.googleapis.com/auth/gmail.readonly — read-only access to the operator's own Gmail mailbox. The application never sends, modifies, labels or deletes mail through this scope.
• https://www.googleapis.com/auth/pubsub — to receive change notifications for that mailbox from Google Cloud Pub/Sub.

In normal operation the application reads only message headers — sender, recipients, subject and date — for messages that arrive after it starts watching. It does not read message bodies or attachments to decide whether a message is relevant.

How the data is used

The headers are used for exactly one decision: whether the message is addressed to a recipient address on a whitelist configured by the operator. If it is, the Gmail message id is passed to the operator's own assistant software, running on the same machine, which then reads that message on the operator's behalf and summarises it for them. If it is not, the message is ignored.

The data is not used for advertising, profiling, analytics, training machine learning models, or any purpose unrelated to presenting the operator's own mail back to them.

How the data is stored

The application runs on hardware controlled by its operator. It stores, on that machine only:

• an OAuth token for the operator's own account, in a file readable only by the operating system user that runs the application;
• a Gmail history cursor and a rolling list of the most recent processed message ids, so that a message is not processed twice.

Message content is not stored. Headers are held in memory only for as long as a message is being evaluated.

How the data is shared

Google user data is not sold, and is not transferred to anyone. It does not leave the operator's own machines except in requests back to Google's own APIs. There is no server operated for other people, no analytics provider and no third-party recipient of any kind.

Retention and deletion

The operator can revoke the application's access at any time from Google Account permissions, which immediately ends all access. The locally stored token and cursor can be deleted by removing the application's data files; doing so leaves no copy of any Google user data anywhere.

Limited Use

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

Questions about this policy: jpolcar@gmail.com