Data & permissions
Privacy policy
This policy explains how Node1 n8n Gmail, operated by Phil Loper, handles data for its private Gmail labeling workflow. It covers this workflow and its public information pages.
What the app accesses
After you authorize Google access, the app can retrieve your Gmail account address, message and thread identifiers, message headers such as sender, recipient and subject, timestamps, message text or snippets, and label information. The workflow retrieves messages matching its configured filter. Attachments are not intentionally downloaded by this workflow.
Google issues OAuth access and refresh tokens so the app can run without receiving your Google password. The requested permission is https://www.googleapis.com/auth/gmail.modify. It permits reading and modifying mail, including broader capabilities such as composing or sending. This workflow uses the connection to read matching messages and apply labels.
Why the data is used
The app uses email data to classify messages and apply one of four fixed labels: Action, Receipts, Newsletters, or Review. A local model on Node1 receives a bounded subject, sender, and message snippet for classification. Invalid model output is routed to Review. Execution data helps the owner inspect results and diagnose problems.
The current workflow does not send, archive, or delete emails. It does not sell Google user data, use it for advertising, or use it to train or improve general-purpose AI models.
Where data is processed and stored
The n8n workflow and Ollama model run on the owner's Node1 computer. The classifier does not send message content to a hosted AI model. n8n may save retrieved message data and node outputs in its local execution database. OAuth credentials are stored using n8n's credential encryption.
Successful and failed execution history is configured for automatic pruning after 14 days, subject to an additional 1,000-execution limit and the normal pruning schedule. Credentials remain until removed or revoked. Owner-restricted local backups can retain database contents and credentials beyond the execution-history period until those backups are deleted. Access controls protect the editor and backup location; these are not promises that every local file or backup is independently encrypted.
Service providers and disclosure
Google processes API and authorization requests. Cloudflare provides the private editor's access gateway and can process traffic needed to deliver that service. These public information pages are hosted through OpenAI Sites and Cloudflare; hosting services can process ordinary connection information such as IP addresses and request metadata. This site has no added advertising analytics, mailbox forms, or Gmail API connection.
The workflow does not share Gmail data with advertisers or data brokers. Human access to Google user data is limited to the account owner and access specifically authorized by the user, or circumstances permitted for security investigations or legal obligations. Further uses or transfers require an appropriate basis and, where required, renewed consent.
Use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements.
Your choices and deletion
You can unpublish the workflow in n8n to stop automatic runs, disconnect or delete the Gmail credential in n8n, and revoke the app from your Google Account connections. Revocation stops future authorized access but does not automatically erase previously stored execution history or backups.
To request deletion of retained app data or backups, contact loper.phil@gmail.com. The operator will verify the request and address the relevant local records and backups. Removing app data does not delete the original emails or labels from Gmail; the mailbox owner manages those in Gmail.
Changes and contact
This page will be updated if the workflow's data practices change. New uses of Google data beyond this disclosure require an updated notice and renewed consent where required. Contact: Phil Loper, loper.phil@gmail.com.