Privacy policy

Privacy policy

How Atlas collects, uses, and protects your data — including the Google account data you choose to connect.

01

Overview

Atlas Meeting (“Atlas,” “we,” “us”) provides an AI assistant that joins your video meetings to take notes, render visuals, and produce summaries. This policy explains what data we collect, how we use it, and the choices you have. It applies to atlasmeeting.com and the Atlas service.

We collect the minimum needed to run the service, we do not sell your data, and we do not use your meeting content or Google user data to train machine-learning models.

02

Information we collect

Account information. When you sign up we collect your name, email address, and authentication identifiers through our auth provider (Clerk). If you sign in with Google, we receive your basic Google profile and email address.

Google user data. With your explicit consent, Atlas accesses your Google Calendar events (read-only) to know when meetings are scheduled and who is attending. We request only the scopes needed for these features and never request write access to your calendar.

Meeting data. For meetings you keep, Atlas stores the transcript, summary, decisions, action items, and the visual artifacts it generated. Audio is processed in memory and discarded within 24 hours unless you opt in to retention.

Operational data. Standard logs (timestamps, error traces, aggregate usage) used to operate and secure the service. These do not contain meeting content.

03

How we use Google user data

We use the Google Calendar data you authorize solely to provide user-facing features of Atlas: identifying upcoming meetings so the assistant can join, resolving meeting attendees to send recaps, and showing your schedule inside the dashboard.

We do not use Google user data for advertising, we do not sell it, and we do not transfer it to third parties except as needed to provide the service (see Subprocessors) or as required by law.

04

Google API Services Limited Use disclosure

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.

Specifically, we do not use Google user data for serving advertisements, we limit human access to this data except as required for security, to comply with applicable law, or where you have provided explicit consent, and we do not use or transfer this data for purposes unrelated to providing or improving the Atlas features you requested.

05

How we store and protect data

Data is encrypted in transit (TLS 1.3) and at rest (AES-256). Atlas runs on AWS in the United States. We do not store your Google OAuth refresh tokens ourselves; they are held by our authentication provider (Clerk), which returns a short-lived access token on demand.

Atlas employees do not read your transcripts or summaries. Engineering may access aggregate system logs to diagnose issues, never the content of your meetings.

06

Sharing and subprocessors

We share data only with the service providers needed to operate Atlas: AWS (compute, storage), Anthropic (LLM inference; Anthropic does not train on data passed through its API), Clerk (authentication), and Vercel (frontend hosting).

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

07

Retention, deletion, and revoking access

You can delete any meeting from your dashboard; deletion is immediate and removes the transcript, summary, decisions, actions, artifacts, and audio from our systems. Deleting your account removes all associated data within 7 days.

You can revoke Atlas’s access to your Google data at any time from your Google Account permissions page, or by disconnecting Google in Atlas Settings.

08

Changes and contact

We may update this policy as the service evolves; material changes will be reflected by the “last updated” date below and, where appropriate, an in-product notice.

Questions, data requests, or DPA paperwork — email trust@atlasmeeting.com.