ATLASS

Privacy policy

Last updated July 11, 2026 · Atlass is a product of 693 Labs

What we collect

• Account information: your email address and profile details, handled by our sign-in provider, Clerk.
• Your projects: the files, conversations, checklists, notes, and memories Atlass keeps so your projects work across sessions. They are stored in our database and belong to you.
• Usage and billing records: which AI models ran, what each request cost, and error patterns, so your usage meter and our routing stay honest.

How we use it, and what we never do

We use operational metadata (model choices, costs, timings, error shapes, and which routing decisions later needed rework) to make Atlass route smarter and estimate more accurately. This metadata does not include the contents of your projects.

We do not train AI models on your project files, your code, or your conversations, and we do not sell your data. If we ever offer content-level training, it will be a separate, clearly worded, off-by-default choice.

Who touches your data

• AI model providers (such as Anthropic, OpenAI, and Google) receive the messages needed to answer your requests, under their API terms, which do not train on API data.
• Infrastructure: Neon (database), E2B (build sandboxes), Clerk (sign-in), Stripe (payments, when enabled). Each sees only what its job requires.
• If you connect GitHub, your access token is stored in our database and used only to push your own code to your own repositories.

Your controls

• Edit, pin, or delete any memory Atlass keeps, from the Memory tab.
• Export every project file anytime (download as zip, or push to your GitHub).
• Delete a project and everything in it permanently from the project menu.
• Ask us to delete your account and all associated data: hello@atlass.build.

Questions: hello@atlass.build · Terms of service