What Atlas knows about your meetings.

During a meeting, Atlas hears the audio of the call. It does not see your screen, your other tabs, or any documents you have not given it. It does not record video.

With your permission, Atlas can read your calendar events to know when meetings are scheduled. The only time it writes to your calendar is when you schedule a meeting from the dashboard yourself — it never creates or changes events on its own.

For each meeting you keep, Atlas stores: the transcript, the summary, decisions, action items, and the artifacts it drew. Audio is processed as a live stream and is not recorded or stored. Transcripts, notes, and boards are stored so you can revisit them.

Email trust@atlasmeeting.com and we delete a meeting and everything attached to it — transcript, summary, notes, and artifacts.

Your meetings are visible only to you. The only thing that leaves your account is the recap email, and it goes to the recipients you choose.

We do not read your meeting content. Engineering can access aggregate system logs to diagnose issues, never the content.

In the meeting itself: remove Atlas as a participant, the same way you would remove any other guest. You can also pull Atlas out of a live call from that meeting’s page in your dashboard.

Before the meeting: turn off auto-join for any calendar event from your dashboard.

Data is encrypted in transit and at rest. Atlas runs on AWS in US-East.

We use Anthropic’s Claude API for summary and artifact generation. Anthropic does not train on data passed through their API.

The third-party services Atlas relies on to run: AWS (compute, storage, and Claude via Amazon Bedrock), Anthropic (Claude models), Google (Gemini voice models), Deepgram (speech-to-text), Clerk (authentication), Vercel (frontend hosting), Resend (recap email delivery), Exa (web search when the agent researches).

A full list with locations and data categories is available on request: trust@atlasmeeting.com.