Privacy Policy

Information we access

• Google identity information used for sign-in and access control, such as name, verified email address, and profile image.
• For a Gmail account an authorized Atlas One owner or administrator connects: Inbox messages from a one-time ten-calendar-day pilot window. When that window is unusually large, Atlas One saves bounded recent batches and continues filling in the remaining pilot period on later refreshes. Later refreshes use Gmail change history to retrieve new or changed items from the prior secure synchronization point. Atlas One receives message headers returned by Gmail (including sender and subject), received time, labels, Google-provided snippet, and attachment filenames or counts. Spam and Trash are excluded. To create a conversation-level executive brief, Atlas One may process the readable text of an email message during synchronization. The raw message body is not stored in the Atlas One archive; only the resulting derived brief is retained. Attachment contents are not downloaded or copied automatically. When an approved owner or administrator explicitly chooses “Save attachments to Drive,” Atlas One retrieves only the selected attachment and copies it to the configured Atlas One Drive archive.
• For a connected account’s primary Google Calendar: up to 300 nearby and upcoming events per refresh, including title, date and time, time zone, location, organizer, and the Google event link. A declined response is used only to omit that event. Private or confidential events are reduced to “Private event,” without location, organizer, or link. When the account holder also approves Calendar editing, authorized users may create events and may edit or delete only events created through Atlas One.
• Encrypted Google authorization tokens needed to refresh connected information without collecting a Google password.

How we use Google user data

Atlas One uses Google identity information for sign-in, access control, connection management, and security auditing. It uses connected Gmail and Calendar information only to create the requested organization-wide email brief, identify possible follow-ups, and show selected calendar events to approved Atlas One users. “Business” and “Personal” are briefing categories, not separate privacy boundaries; all approved users who have the relevant Atlas One permission can see the shared briefing.

Gmail access supports briefing. An approved owner or administrator may send only a reviewed, explicitly confirmed reply from a mailbox that has granted Gmail sending permission. Atlas One cannot send automatically, change, or delete Gmail messages. Calendar changes require both the account holder’s Google authorization and an Atlas One role with calendar editing permission. Atlas One does not add guests or send invitation updates, and it does not edit or delete Calendar events created outside Atlas One.

An approved owner or administrator may explicitly save attachments from an original Gmail message to the configured Atlas One Drive archive. Atlas One does not automatically copy attachments or change the original Gmail message.

Optional AI summaries

When an Atlas One owner enables optional AI summaries, the bounded readable email text needed to prepare a professional executive brief may be sent to the configured AI provider. Atlas One does not retain or use Google Workspace API data to develop, improve, or train generalized or non-personalized AI or machine-learning models, or for advertising. The feature remains off until the owner configures the provider and can be disabled at any time.

Storage, retention, and deletion

• Google refresh tokens are encrypted with authenticated encryption before storage.
• Processed email metadata and derived summaries—including account, sender, subject, received time, a derived executive summary, labels, and attachment count—support approved historical search. Raw email bodies and attachment contents are not retained in the Atlas One archive. Attachments explicitly saved by an approved owner or administrator are retained in the selected Google Drive folder. On each successful Gmail refresh, records older than 365 days are removed. Routine Gmail-history refreshes reflect Inbox moves and Gmail deletions. If Google expires that history cursor, Atlas One uses a conservative recovery: older cached items it cannot re-verify move to searchable history instead of remaining marked as current Inbox. Disconnecting the source removes the applicable cached data.
• Each Calendar refresh retrieves up to 300 selected nearby events per connected primary calendar. Atlas One may also retain nearby events created through Atlas One so approved users can safely manage them. Limited Calendar change audit records identify the acting user, connected account, action, request, and time without storing the event title.
• Disconnecting an account erases its locally stored authorization token and purges its cached Gmail and Calendar information.
• Limited audit records may be retained for security, troubleshooting, and administrative accountability.

Service providers and disclosure

Atlas One relies on service providers needed to operate the workspace, including Google APIs, Supabase authentication, and Cloudflare hosting and data storage. Google user data is disclosed only to these service providers as necessary to operate the user-facing Atlas One features described here and with the connecting user’s consent, or when necessary for security or to comply with applicable law. We do not sell, rent, or transfer Google user data for advertising, data brokerage, creditworthiness, or lending.

Google API Limited Use

Atlas One’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your choices

An authorized Atlas One owner or administrator can exclude a connected source, disconnect an account, or remove a user’s Atlas One access. A Google account holder can also revoke the connection in their Google Account settings. Revoking access in Google stops future access but does not itself erase Atlas One’s existing cache; use Disconnect in Atlas One or email us to request deletion. To request access, correction, or deletion, email atlas@atlasglobe.net.

Security and policy updates

We use HTTPS, access controls, encrypted authorization tokens, bounded data collection, and audit records to reduce risk. No system is completely secure. We may update this policy as Atlas One changes and will revise the effective date shown above.