Security
How Archon keeps your work safe, what we haven't done yet, and how to tell us about a problem.
Updated November 13, 2026 · What changed
The short version
- Archon asks first.Nothing you can't undo, like sending an email, happens without your yes.
- Your access sets the limit.Your Archon reads only what you can. Room permissions apply to every answer.
- Agents never see your keys.Keys and sign-ins are sealed with encryption and used for you, not shown.
- Every step is recorded.See what Archon read, did and changed, step by step.
- Keep it on your Mac.A Mac workspace never leaves that Mac.
- Found a problem? Tell us.Write to [email protected]. We won't pursue anyone reporting in good faith.
The rest of this page is the detail. Where the two differ, the detail is what counts.
01Where your work lives
You choose for each workspace. A workspace on your Mac keeps everything on that Mac. An online workspace is kept on our servers at Railway, in the United States, so your team can reach it from anywhere. Each workspace is its own private space: nothing in one is visible from another.
02Who can see what
People see what a workspace's rooms and permissions allow. Each person's Archon works with that person's access and no more, so it can't show you what you couldn't open yourself. An owner decides who is in a workspace and can remove anyone.
03What agents may do
Agents work inside the permissions you set. Before any action that can't be undone - sending an email, adding a calendar event, publishing, paying - Archon stops and shows you exactly what will happen, and waits for your yes. Every step an agent takes is recorded: what it read, what it did and what it changed. Work that runs code does it on a computer of its own, with only the keys that task was given.
04Keys and connected accounts
Keys and sign-ins for the services you connect are sealed with encryption (AES-256-GCM) before they are stored. Agents use them through Archon and never see them. Disconnect a service and its sign-in is deleted; for Google, Archon also revokes its access.
05Signing in
Sign in with a code we email you, or with Google or GitHub; there is no Archon password to steal. Codes and links are kept only as a one-way hash and last ten minutes, and after too many wrong codes, that address takes no more codes that day. A sign-in ends after 30 days unused, after 90 days at most, or when you sign out.
06On the way
Everything between your browser or Mac and an online workspace travels encrypted (HTTPS), through Cloudflare, which also shields the site from attacks. Calls go straight between the people in them, encrypted end to end; when Cloudflare has to relay one, it can't listen in. Calls are never recorded.
07The Mac app
The Mac app sends us no usage data and no crash reports. It gets its updates only from heyarchon.com. A workspace on your Mac never comes to us unless you send something yourself, like a bug report.
08What we haven't done yet
Archon is new, and we would rather say so. We do not yet hold a SOC 2 or ISO 27001 report, and single sign-on beyond Google and GitHub is by arrangement. If your organization needs something specific, tell us.
09Telling us about a problem
If you think you've found a security problem in Archon, write to [email protected] with what you found and how to see it. We will confirm we got it, keep you told as we fix it, and credit you if you like.
Please give us a reasonable time to fix it before telling anyone else, use only your own accounts and workspaces, and don't read, change or delete other people's data. If you act in good faith within these lines, we will not pursue you for it.
10What changed
When this page changes, its date changes and the change is listed here. If a change affects how your information is used or what you agreed to, we email you before it takes effect.
- First published.