Skip to content

Privacy Policy

Effective September 19, 2026

What Atlas is

Atlas is a personal productivity and organization system. It helps a person plan their day and keep tasks, projects, calendars, knowledge, decisions, and related records in one private workspace. Atlas is currently available by invitation.

Information Atlas may process

Depending on how an account is used, Atlas may process:

  • account and profile information used to sign in, such as an email address
  • workspace content the user creates, including tasks, projects, notes, knowledge, decisions, and related records
  • calendar information from calendars the user chooses to connect, described below
  • workspace configuration, such as appearance and which calendars are shown
  • operational logs needed to run and diagnose the service

Atlas processes this information to provide the workspace features the user asks for. It does not collect additional categories of personal information beyond what those features require.

Google Calendar data

When a user connects Google Calendar, Atlas asks Google for two read-only permissions: to see the list of the user's calendars (https://www.googleapis.com/auth/calendar.calendarlist.readonly) and to view the events on them (https://www.googleapis.com/auth/calendar.events.readonly). Atlas uses that access only to:

  • list the calendars in the Google account, so the user can choose which ones Atlas shows;
  • read events from the calendars the user chooses — each event's title, start and end time, location, description, organizer name, and number of attendees — to show them in Atlas's Calendar and Today views and in the user's daily briefing.

Atlas cannot create, change, or delete Google Calendar events. Attendee names and email addresses are not stored or shown.

What Atlas stores from Google

  • The Google account's email address, to show which account is connected. It is deleted when the user disconnects.
  • The access credential (an OAuth refresh token), encrypted at rest with a key that is kept separately from the database. It is never shown to users or written to application logs, and it is deleted immediately when the user disconnects or reconnects.
  • Which calendars the user chose to show in each workspace. This is deleted when the user disconnects.
  • Daily briefings, which include the titles and times of that day's events. Each briefing is deleted automatically no later than 90 days after it was created.
  • If the user marks a calendar event complete or tracks it as a meeting, the event's calendar and event identifiers (not its title) are stored with that record. Meeting notes the user creates from an event start with the event's title.

Event descriptions, locations, and organizer names are shown to the user but are not stored by Atlas.

AI features

Atlas's AI features are optional. When they are turned on:

  • Daily briefing summaries and Ask Atlas answers are written using Anthropic's Claude API. For Google Calendar events, Atlas sends only each event's title, start and end time, and whether it is cancelled (and, for meetings, the number of attendees). Event descriptions, locations, organizers, and attendee details are never sent.
  • If the user turns on spoken responses, the text Atlas speaks is converted to audio using OpenAI's text-to-speech API. That text can include the title and time of the user's current or next calendar event. Voice commands the user records are transcribed using OpenAI's speech-to-text API; they contain only what the user says.

Atlas does not use Google user data to develop, improve, or train generalized or non-personalized AI or machine-learning models. Atlas does not opt in to sharing Google Calendar data with Anthropic or OpenAI for training or improvement of their general-purpose models. These services may retain API data for limited periods for security, abuse prevention, and other purposes described in their applicable commercial terms.

How Google user data is shared

Atlas does not sell Google user data. Atlas does not use Google user data for advertising. Atlas does not transfer Google user data to unrelated third parties for their own purposes, and does not use it to determine creditworthiness or for lending.

Google user data is processed only by the service providers that run Atlas: Railway (application hosting and database), Cloudflare (network delivery, storage for notes, and encrypted backup storage), Backblaze (encrypted backup storage), and, for the AI features above, Anthropic and OpenAI. They process it only to provide their service to Atlas.

People do not read a user's Google Calendar data unless the user asks for help and agrees to it, it is necessary for security, or the law requires it.

Limited Use

Atlas'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 the Limited Use requirements. Information received from Google APIs is used only to provide or improve user-facing Atlas features.

Disconnecting and deleting data

A user can disconnect Google Calendar at Settings → Connections → Google Calendar → Disconnect. Atlas then immediately deletes the stored Google credential, the user's calendar choices, and the stored Google account email. Daily briefings created while connected are deleted as they reach 90 days.

Disconnecting deletes Atlas's copy of the access, but Google keeps its own record that the user granted Atlas access. To remove that as well, visit myaccount.google.com/permissions and remove Atlas.

To ask for Google-derived data to be deleted, email the address below. Atlas completes deletion requests within 30 days. A request deletes the Google credential, calendar choices, calendar and event identifiers, daily briefings, and the stored Google account email, and removes titles copied from Google Calendar where they can be told apart from text the user wrote. Meetings and notes the user wrote are kept unless the user asks for them to be deleted too. Security logs about sign-in and account activity, which do not contain Google Calendar content, are kept as long as needed to protect the service.

The periods above apply to Atlas's active systems. Atlas also keeps encrypted disaster-recovery backups of its database. They are not used for ordinary processing, and information deleted from active systems may remain in them.

Security

We use reasonable technical and organizational safeguards appropriate to the system. No method of storage or transmission is completely secure, and this policy does not claim otherwise.

Contact

Atlas is operated by Cody Kringlie. For privacy questions or deletion requests, email [email protected].