DAOS Gmail access

Who connects an account

DAOS is Danil Automations' private automation system. I alone connect my work Gmail account, danil.automations@gmail.com, using Google OAuth. Clients, visitors and people who email me do not grant access to their Google accounts. Their messages may nevertheless be present in my authorized work mailbox.

Permission requested

The requested restricted permission is https://www.googleapis.com/auth/gmail.modify. It can read, compose, send and modify mail in my account. It cannot immediately and permanently delete messages while bypassing Trash. The n8n credential must use Custom Scopes so this is the only Gmail scope requested; broader default permissions are outside the authorized configuration.

How access may be used

Connecting a credential does not by itself enable a workflow or send a message. Each feature may operate only when configured and enabled for the stated purpose.

• Outreach: prepare drafts for my review and manual sending; never automatically send cold first-contact mail.
• Website enquiries: when enabled, prepare a first reply as a draft for my review and manual sending.
• Email Discovery: when enabled after appropriate classification and safety checks, read and classify inbound mail, then possibly reply automatically only to genuine business enquiries or established client conversations. Spam, personal, irrelevant, uncertain and sensitive messages must not receive automatic replies.

The permission may expose addresses, subject lines, headers, message bodies, threads, drafts and mailbox state. DAOS must limit actual operations to enabled, disclosed features. Automatic attachment transfer is outside the approved operating model.

AI, storage and control

When an AI-assisted feature is enabled, selected email information may be sent to the OpenAI API for classification or drafting, potentially including a limited excerpt from a message later determined to be personal or irrelevant. More conversation context may be needed for a genuine business task. That transfer requires my informed consent and review of the actual payload, provider data controls and Google's Limited Use requirements before the feature operates. I do not claim a particular OpenAI retention setting or completed review of a feature that is not enabled. Attachments are not automatically sent.

When I connect the credential, n8n stores OAuth credentials and tokens in the private DAOS environment; database backups may contain copies. The retention targets and their implementation limits are explained in the Privacy Policy. I can revoke access through my Google Account, but revocation alone does not delete previously stored DAOS records or backups. I can also remove the n8n credential and review those copies.

DAOS's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google-derived data is not sold, used for advertising or credit decisions, or used to train a generalized AI model.

Read the Privacy Policy and Terms of Service before authorizing. An owner-facing summary of this scope, the intended uses and possible OpenAI processing should also be shown immediately before OAuth consent; this public page does not replace that notice. Questions can be sent to danil.automations@gmail.com.