Privacy Policy

Effective date: November 3, 2026

This policy covers Alistair Inbox Assistant, a personal set of command-line utilities operated by Alistair Gillespie to access his own Google accounts through OAuth and Google APIs. It is for the account holder’s own use, not offered as a public service.

Google data accessed

Only data available through the permissions the account holder authorizes may be accessed. Depending on the command and enabled scopes, this can include Gmail messages, message metadata and labels; Drive files and metadata; Calendar events; contacts; and Workspace documents or other resources. The consent screen identifies the requested permissions. The tools access data when the account holder runs a command or requests an operation.

How data is used

Google data is used to perform the account holder’s requested tasks, such as finding or displaying mail, organizing messages, locating files, or reading or managing calendar information. Data is not sold, used for advertising, or used by the operator to build profiles or train a general-purpose AI model.

AI-assisted requests

If the account holder asks an AI assistant to summarize, analyze, draft from, or otherwise work with retrieved Google data, the selected content may be sent to the AI service provider configured for that session so it can fulfill the request. The account holder initiates that processing. The provider’s own terms and privacy settings govern its handling. The tools do not send Google data to an AI service merely because this policy page is viewed.

Storage and retention

This website is a static information page and does not collect or store Google account data. Google data is retrieved from Google over HTTPS and is not intentionally maintained in a separate server-side mailbox or file archive by this site. Message or file content may appear in command output, local terminal history, or an AI assistant’s session records when the account holder uses those tools; retention in those systems depends on their local and provider settings.

OAuth credentials are stored on the operator’s Windows device in the local credential stores used by each command-line tool. Some tools use the operating system keyring or encrypted credential storage; Himalaya’s refresh token is stored in a local configuration file. The device and Windows user account therefore need to be protected. Credentials remain until removed or access is revoked.

Sharing and disclosure

Google data is sent to Google only as needed for the authorized API operations. For an AI-assisted request, selected content may also be sent to the AI provider chosen for that session, as described above. The operator does not sell or share Google data for advertising, marketing lists, or unrelated purposes. Data may be disclosed if required by law or to protect the security of the accounts or tools.

Account holder choices

• Stop using a tool or decline any OAuth permission that is not needed.
• Revoke the app’s access in Google Account connections.
• Delete local credentials from the device when they are no longer needed.

Contact and changes

For privacy questions, contact musictechtoday.info@gmail.com. This policy will be updated if the tools’ data practices change.