Privacy policy

Data accessed

After the account holder authorizes access through Google OAuth, the application can retrieve Gmail message and thread identifiers, sender and recipient information, subjects, message bodies, timestamps, and labels. Relevant message and thread context may be retrieved for classification and review. Attachment retrieval is not part of the initial workflow.

OAuth tokens are stored to maintain authorized access. The application does not collect the account holder's Google password.

How data is used

Gmail data is used to organize the authorized inbox: classify messages, produce summaries, apply labels, archive messages, and review or correct those actions. Processing records can include message identifiers, classifications, explanations, preferences, action history, and errors.

The Gmail permission requested by the application also permits sending. Sending, permanent deletion, and mailbox-settings changes are not part of the intended workflow.

External processing and disclosure

Selected message content and relevant context may be transmitted to configured external AI inference providers to classify or summarize mail. This processing is not confined to the application operator's own systems. Such providers must be selected and configured to handle this data only for the requested application functions, consistently with Google's Limited Use requirements.

The application does not sell Google user data, use it for advertising, or use it to train general-purpose AI or machine-learning models. Transfers of Google user data are limited to providing the described functions, security needs, legal obligations, or the account holder's explicit direction, subject to Google's applicable policies.

The account holder may inspect messages and processing records to review results and resolve problems. The application does not provide public access to those records.

Storage, retention, and deletion

Application storage may contain OAuth credentials, processing and action records, derived preferences, and message content needed for execution, review, or troubleshooting. Access controls protect this storage; stored OAuth credentials are encrypted. Backups may contain copies of application data.

Data is retained as needed to operate the configured workflows, review decisions, and recover from failures. The account holder controls deletion of stored credentials, records, retained message content, and derived preferences. Copies in backups remain until those backups expire or are deleted. External processing is also subject to the selected provider's applicable retention terms and configured controls.

Revoking access

The account holder can stop workflows and revoke access through Google Account connections. Revocation prevents further authorized Gmail access; it does not automatically delete existing application records or backups, or reverse changes already made to Gmail.

This informational website

These pages contain no analytics scripts, advertising, forms, or application cookies. The hosting provider may process ordinary connection data, such as IP addresses and request metadata, to deliver and protect the website. Gmail credentials and message content are not collected through these pages.

Google API Limited Use

Homelab n8n's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Contact and changes

For privacy questions or deletion requests, use the support email shown on the application's Google OAuth consent screen. For this personal-use application, the account holder also administers its data.

This policy will be updated when data practices change. Any expanded access or materially different use of Google data requires the account holder's authorization before it is enabled.