Arthur n8n

Privacy policy

Last updated: 24 September 2026

Arthur n8n is Dave's personal, self-hosted automation service running on Arthur. It is intended for Dave's own use, with no public registration. This policy covers the service's Google integrations and this public information website at p-eps.uk.

Google data accessed

Google account access is granted through OAuth. Arthur n8n receives authorisation tokens rather than the Google account password. The permissions shown by Google during authorisation determine which data and actions are available to a connected integration.

Depending on the permissions granted and workflows enabled, data may include account identifiers and information from connected Google services, such as emails, files, spreadsheet contents or calendar events. These are examples, not a statement that all of these services are connected. Workflows may read, create, update or delete data only where the granted permissions allow it.

How data is used

Google user data is used to carry out the personal automation tasks configured by Dave, and to inspect or troubleshoot those tasks. It is not used for advertising, sold, or used to train general-purpose AI or machine-learning models.

Storage and retention

OAuth credentials and tokens are held by the self-hosted n8n installation so that authorised workflows can run. Depending on its configuration, workflow inputs, outputs and error details may be retained in execution history, logs, files or backups. This can include Google user data. Data explicitly saved by a workflow may also remain in its destination service.

Retention depends on the configured execution-history settings, manual deletion and any backup arrangements. There is no fixed deletion period stated here. Removing a connection or revoking access does not automatically erase data already saved, execution records or backup copies. Those need to be deleted separately; backup copies may remain until the relevant backups are removed or replaced.

Sharing and access

Data is exchanged with Google to perform authorised operations. A workflow may send selected data to another service or recipient only when Dave deliberately configures that transfer for a personal task. The receiving service's own privacy practices then apply. Hosting, network or backup providers may process data where they are involved in delivering or maintaining the service. Data may also be disclosed where required by law.

Dave may view data in his own workflows and execution records to operate and troubleshoot them. Google user data is not made public merely by connecting an account. This public website does not display workflow data or credentials.

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

Control, revocation and deletion

Dave can stop workflows, remove stored Google credentials from n8n and revoke the application's access through Google Account connections. Revocation prevents further access through that authorisation; it does not undo completed actions or delete existing copies of data.

As the sole intended user and operator, Dave manages deletion directly in n8n and any workflow destinations, logs and backups. This website does not provide an account system or collect deletion requests.

Visitors to this website

These static pages contain no analytics scripts, advertising, forms or application cookies. Visiting them does not grant Google account access. Cloudflare hosts the pages and may process technical request information, such as IP addresses and browser details, to deliver and protect the website. See Cloudflare's privacy policy.

Changes

This policy should be updated before introducing materially different data uses or opening the service to other users. The date above identifies the latest version.