Last updated: 27 October 2026
This policy covers the Google connections and workflow automation operated by Daniel Kam at n8n.danielk.am. The integration is for our own accounts and internal work. Only invited operators may connect accounts. It is not a public service for customers to register their Google accounts.
Contact Daniel at [email protected] with questions about this policy or requests concerning data processed by the integration.
Information the integration accesses
The information available to a workflow depends on the connected account, the Google permissions granted, and the workflow's configuration. It may include:
- Google account information used to identify a connection, together with OAuth access and refresh tokens used to maintain it.
- Google Drive file names, identifiers, metadata and the contents of files selected for a task. Google Docs and Sheets may be read or converted into text or tabular data.
- Spreadsheet contents used for internal records, reporting and workflow inputs or outputs.
- Calendar events, tasks and contact records used by the corresponding connections.
- Gmail information available under the permissions granted to a Gmail connection, such as mailbox settings or message data where authorized.
- Workflow inputs, outputs, execution details and errors, which can contain information retrieved from a connected Google account.
The planned Google Ads connection will use keyword inputs and targeting settings to request keyword ideas and historical search-volume estimates. It is awaiting Google approval. This policy does not mean that Google Ads access has been granted.
How information is used
We use connected account information to perform the internal tasks configured by an authorized operator. These include finding and reading documents, working with spreadsheets, organizing tasks and account information, producing reports, and returning relevant results to our connected tools and assistants.
Google permissions can permit broader operations than an individual task needs. The workflow and the account owner's instructions determine the operations performed. Connecting an account does not authorize unrelated use of its data.
Sharing and connected services
A workflow can pass selected information to the destination services configured for that task. For example, a document lookup can return text to a connected assistant, and a reporting workflow can write results to a spreadsheet. AI services may process information when an operator uses an AI-enabled workflow or assistant.
Hosting and infrastructure providers process information needed to run the integration. Destination services process the information sent to them under their applicable terms and privacy policies. Information may be processed outside Singapore.
We do not sell personal data. Personal data from connected Google accounts must not be used for ad targeting, data brokerage, or training generalized AI or machine-learning models. Any transfer of Google user data must be limited to what is necessary for the authorized workflow and permitted by Google's requirements.
Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable. These restrictions apply even where a general service-provider policy allows broader uses.
Storage and security
The n8n instance is self-hosted and uses a PostgreSQL database. Credentials are managed through n8n's credential system. Workflow data can also appear in execution records, files, reports or other destination systems used by the workflow.
The public n8n service uses HTTPS. Administrative access is restricted to authorized operators. Operators must keep credentials out of public pages, public workflow results and shared reports.
Retention and deletion
Connected credentials are retained while their connection is configured. Execution records and workflow outputs have separate lifetimes that depend on the workflow, n8n settings and destination system. Disconnecting a Google account does not automatically erase information already copied into execution records, files or another service.
To request deletion, email [email protected] and identify the connection or workflow concerned. We will review the request, remove information that is no longer needed, and explain any records that must be retained for an ongoing task or a legal obligation. Copies in backups may remain until those backups are replaced or expire.
Revoking Google access
You can remove the integration's access through your Google Account third-party connections. An administrator can also disconnect or delete the corresponding credential in n8n.
Revocation stops future access through that authorization. It does not delete copies already held by n8n or a destination service. Contact us separately if those copies should also be removed.
Changes and related information
We will update this page when the integration's data practices change. The date above identifies this version.
This policy specifically covers n8n's Google connections. The danielk.am privacy policy separately describes the main website and other services. For Google account data handled by this integration, the restrictions in this policy apply.