ATLASInfrastructure Mail

Atlas Infrastructure Mail P17

Privacy policy

What the integration accesses, why it uses that information, and how the account owner stays in control.

Last updated: November 4, 2026

1. Operator and scope

Atlas Infrastructure Mail P17 is a personal integration operated by Scott Leone. It lets the authorized owner of a dedicated Gmail infrastructure mailbox use configured AI assistants to search and review infrastructure notifications. It is not a public email service and does not offer public account registration.

This policy covers the integration and its public informational website. For questions or privacy requests, contact atlassndcoresys@gmail.com.

2. Information accessed

With the account owner’s authorization, the integration uses the Gmail API with the gmail.readonly scope. Depending on the requested operation, it accesses:

  • The authorized mailbox address, message and thread counts, and related mailbox metadata.
  • Message and thread identifiers, sender and recipient addresses, subjects, dates, snippets, labels, and read/unread status.
  • Message bodies and conversation content needed to answer a request.
  • Attachment metadata, such as names, types, and sizes, where available. The agent tools do not offer attachment downloading; Gmail message responses may include inline MIME data.

Gmail’s read-only permission can cover the authorized mailbox broadly. It is not a Google-enforced restriction to a particular label or notification category. The integration is intended for a dedicated infrastructure mailbox and validates the configured account.

OAuth credentials and access or refresh tokens are used by the integration service to obtain authorized Gmail access. They are not part of the normal mail-tool results returned to AI clients.

3. How information is used and shared

Information is used to carry out owner-requested searches, read relevant messages or threads, list labels, verify the mailbox, and produce summaries or answers about infrastructure notifications.

Google provides the Gmail service. The privately operated n8n service retrieves the requested data and returns it to the authorized client, such as Open WebUI or Hermes. Selected message content is then processed by the AI model configured for that client. This integration is intended for locally operated models. Sending Google user data to an external model provider would require a separate review of that provider and appropriate disclosure and authorization before use.

Google user data is not sold, used for advertising, or used to develop, improve, or train generalized AI or machine-learning models. Access and transfers are limited to providing the user-facing mail-reading features, necessary security or legal obligations, and other uses permitted by Google’s Limited Use requirements. The mailbox owner can read their own results; access by any other person requires an applicable permitted basis, such as the owner’s affirmative authorization.

Atlas Infrastructure Mail P17’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.

Email content is treated as untrusted data. The read-only mail tools do not themselves send mail, delete messages, modify labels, or execute instructions contained in an email.

4. Storage, retention, and security

Original email remains in Gmail. Credentials are held by the privately operated integration service. Retrieved content is processed in the integration and AI client; tool results, summaries, and copied message content may persist in client chat history, notes, operational logs, or backups according to the operator’s configuration.

There is no single automatic deletion period across those systems. Retained copies remain until the operator deletes them or the relevant system’s retention settings remove them. Backup copies may remain until the applicable backup retention cycle completes.

Controls include authenticated access to the mail tools, validation of the configured mailbox, read-only Gmail requests, and HTTPS for Google API access. The public website contains no mailbox data or OAuth credentials. No system can guarantee absolute security.

5. Revoking access and requesting deletion

The account owner can revoke the app’s access through Google Account third-party connections and disable or remove the integration’s credential and client configuration. Revoking access prevents future authorized access but does not automatically erase information already copied into chats, notes, logs, or backups.

To request deletion of retained integration data or ask about backup copies, contact atlassndcoresys@gmail.com. The operator will assess and handle the request across the systems under their control. Please do not include passwords, OAuth tokens, or sensitive email contents in a request.

Deleting copies from the integration does not delete the original Gmail messages. Those remain under the account owner’s control in Gmail.

6. Public website visitors

This static website provides an app description and policy information. It does not read Gmail, collect mailbox credentials, offer a sign-in form, or receive the integration’s email results. It contains no analytics scripts, advertising trackers, or site-set cookies.

The site is designed for GitHub Pages hosting. When served by GitHub Pages, GitHub may process technical information such as IP addresses and request metadata under the GitHub General Privacy Statement. Following an external link takes you to a service with its own policies.

7. Changes to this policy

Updates will be published on this page with a revised date. Material changes to data access, recipients, or use must be disclosed before the changed processing begins, with additional consent obtained where required.