Privacy Policy

1. Who this covers

This policy explains what [LEGAL ENTITY NAME] (“we”, “us”) collects when you use Atlas, what we do with it, and who else touches it. Atlas is a private beta; the service, and therefore this policy, is deliberately narrow.

2. What we collect

Account information. Your email address, your name if you gave one, and an identifier from the sign-in provider (email code or Google). Sign-in itself is handled by Neon Auth.

Workspace content. Whatever you and your teammates put into a workspace: journal entries and account balances, contacts, tasks, pipelines, pages the assistant builds, and the standing rules and facts you approve for it to remember. This includes any personal information about your customers, vendors, or staff that you choose to record.

Chats and uploads. Every message you send to the assistant and every reply, plus receipt images and PDFs you upload. Uploaded files are stored in Cloudflare R2 and served back only to signed-in members of your workspace.

Usage records. For each model call we keep the token counts and the estimated cost, and a log of the tool actions the assistant took (for example “posted a journal entry”). This is how the per-workspace daily usage limit and the activity feed work.

Feedback. If you use “Send feedback”, the text you type and your email address are emailed to us through Resend. Nothing else about that report is stored.

Technical logs. Vercel, which hosts the app, keeps ordinary request and function logs (IP address, timestamps, errors) for a limited period as part of running the service.

3. How we use it

To run Atlas for you, and for nothing else: to store and show your workspace, to generate the assistant’s responses, to enforce who can see what, to keep the service within its usage limits, and to fix problems. We may look at your data directly when you ask for help, when we are investigating a bug or an integrity problem in the books, or to carry out a deletion request. We do not sell your data, share it for advertising, or use it to train AI models.

4. Who else processes it

Atlas runs on other companies’ infrastructure. Each of these receives only what it needs for its job, under its own terms:

• Anthropic — generates the assistant’s responses. Your chat messages, uploaded receipts, and the parts of your workspace the assistant looks up to answer you are sent to Anthropic’s API for each request.
• Neon — hosts the Postgres database that holds everything above, and runs sign-in (Neon Auth). Data is stored in AWS’s us-west-2 region (Oregon, United States).
• Vercel — hosts and runs the web application and keeps its technical logs.
• Cloudflare (R2) — stores receipt images and PDFs you upload.
• Google — only if you choose to sign in with Google. Google handles that sign-in and tells us your email address and name.
• Resend — only if you use “Send feedback”; it delivers that one email to us.

We have an account with Twilio for a future text-message channel, but it is not connected during the beta and processes nothing. No other third party receives your data unless the law requires it.

5. Channels that are off

The beta is the web app only. Atlas does not connect to your email account, does not receive forwarded email, and does not receive text messages. If we turn either channel on later, we will update this policy first and say exactly what would be read.

6. Who inside Atlas can see it

Your data is visible to the members of your workspace, according to the permissions the workspace owner grants each of them. A workspace is isolated from every other workspace at the database level. The people who operate Atlas can access the database for the support, debugging, and deletion purposes described above.

7. Cookies and local storage

Atlas sets a session cookie to keep you signed in and a cookie recording which workspace you have open. Your browser’s local storage holds a few preferences (theme, whether the sidebar is collapsed, whether you have seen the tutorial). None of these are used for tracking, and there are no third-party analytics or advertising cookies.

8. Retention and deletion

We keep your data for as long as your account and workspace exist. Inside the app you can delete chat conversations and the facts and standing rules the assistant has stored. Posted journal entries are a ledger and are not deleted individually.

To delete your account, or an entire workspace and everything in it, email [CONTACT EMAIL] from the address on the account. During the beta there is no self-serve delete; we carry the request out by hand and confirm when it is done. Copies may persist briefly in provider backups and logs before they age out.

9. Security

Connections are encrypted in transit. Each workspace’s rows are separated by database-level row security in addition to checks in the application, and actions that move money or change who has access require an explicit approval from you. No system is perfectly secure, and this is beta software; keep your own records of anything important.

10. Your rights

You can ask us what we hold about you, ask for a copy, ask us to correct it, or ask us to delete it, by writing to [CONTACT EMAIL]. We honor these requests for everyone regardless of where you live.

11. Children

Atlas is for businesses and is not directed at anyone under 18. We do not knowingly collect information from children.

12. Changes and contact

When this policy changes, the version and date at the top change with it, and for anything material we will tell you by email or in the app before it takes effect. Questions go to [CONTACT EMAIL].