Atlas

Privacy

Updated 15 October 2026

This page says what Atlas collects, why, and where it goes. Questions: [email protected].

Your code and conversations stay with you

Atlas works on your machine, or in your own company's cloud account. Your source code, your chat with the PA, your documents and your project's data are never sent to us.

Your Atlas account

You sign in to Atlas with your email address: a code and a link are sent to it through an email delivery service. Atlas's service then keeps your email, your name, whether Atlas is for you or for a company, and your organisation. For each Mac you use it keeps a machine code and the Atlas version, and — while a team runs, about once an hour — which projects are running, so that the plan you are on can be checked. People who sign in with your company's email domain join your organisation, and its admin can see who is in it and their Macs.

A company server registers with the same service when it is set up, and checks in hourly with its Atlas version and which projects are awake.

The daily usage report

The Atlas app — every copy downloaded from this website — sends one report a day to Atlas, so we can see that each licence is used as agreed. It contains: a machine code, the licence holder and licence terms, the Atlas and operating-system versions, the computer's host and user name, and for each project its name, its folder path and usage measures (such as how many tasks ran and how long they took). It also contains each project's Atlas log since the last report, with credentials masked. The licence screen in Atlas says this happens.

Logs beyond that are sent only when you choose to send them (Settings → Send logs).

Claude

Atlas's engineers are Claude Code sessions signed in to the Claude account of the person who set the project up. What they send to Anthropic is governed by that account's terms with Anthropic. Atlas stores the sign-in in its own credential store and never shows it to anyone.

Payments

Licences are paid through Lemon Squeezy, which sells them to you as the merchant of record: it takes the payment, charges local tax where it applies, and sends the invoices. Your card or PayPal details go to Lemon Squeezy and its payment processors, never to Atlas. Atlas receives what it needs to give you your licences: your email, your organisation, how many licences you bought and when they renew. Lemon Squeezy's own privacy policy covers what it keeps.

Signing in with DigitalOcean

When Atlas runs in your company's cloud, you can connect your DigitalOcean account by signing in with DigitalOcean. Atlas then holds an access token for that account, inside the Atlas installation in that same account, and uses it only to create and manage what Atlas needs there: its cluster, storage, backups and the databases you ask it for. We do not keep a copy. You can withdraw access at any time from your DigitalOcean account's settings.

Credentials you give Atlas

Passwords and tokens you give Atlas for your project are kept in its credential store on your machine or in your cloud account, given to a tool only when that tool needs them, and masked in every log and report.

This website

This website uses Google Analytics to count visits and see which pages are read. Google sets cookies in your browser for this and receives your browser's address and the pages you visit here. It receives nothing from the Atlas app itself. You can block it with your browser's privacy settings or Google's opt-out add-on.

Keeping and deleting

Usage reports are kept while your licence is active and for one year after. To have them deleted, write to [email protected].