What we keep, and who can see it.
Last updated 17 September 2026.
Without an account
Reading the site stores nothing about you on our servers. Tutorial progress, preferences and any runs you try signed out live only in your browser's local storage. If you join the newsletter, we keep your email address and where you signed up from.
With an account
We store your email address and password hash (through Supabase Auth), your profile (name, handle, bio, location, links, avatar), your credit balance and every credit movement, your runs (the model, the prompt and parameters you sent, the cost, and the files that came back), your editor projects, and any MCP connectors you add, including a bearer token if you gave one.
Who sees it
Your runs, projects, connectors, credits and email are visible only to you; the database enforces this per row. Your public profile (name, handle, bio, location, links, avatar and member-since date) is visible to anyone at your profile address. Site editors can see draft content, not your account data.
Where it goes
To generate, the prompt, parameters and any reference files you attach are sent to the model provider (AtlasCloud, which routes to the model vendor) under our account, not yours. Reference files you upload are kept in a private storage folder of your own and shared with the provider through a link that expires within a day. If you add an MCP connector, the handshake and any token you gave are sent only to the server you named.
Deleting
Settings → Danger zone deletes your account and everything above with it. Newsletter emails carry an unsubscribe link.
Cookies
One cookie keeps you signed in. There is no advertising or third-party analytics on the site. The cookie page lists it.
Contact
To ask for a copy of your data, or anything else about this policy, use the contact page.