Privacy policy
Updated 14 November 2026
What Zode (zode.dev, console.zode.dev and api.zode.dev) collects, why, who processes it and what you can do about it. Questions go to je@zode.dev.
What we collect
- Account. Your email address and name. If you sign in with GitHub or Google we receive your name, verified email address, profile picture and account id from them, nothing else. If you use a password we store only a salted hash of it.
- Sessions. A hash of each session id and when it expires. Signing out, resetting your password or deleting your account ends your sessions.
- Workspaces and sandboxes. Workspace names, members and roles. For each sandbox: its name, size, region, status, the git repository and branch you give it, and when it was created, stopped or deleted.
- API tokens. A hash of each token, its name and when it was last used, including the token
zode logincreates for the CLI. We never store the token itself. - Audit log. Who did what and when in your workspace, so you can see it.
- Beta requests. If you ask for a seat on zode.dev: your email address, how many agents you run and when you asked.
- Technical data. IP address and browser details in server logs and for rate limiting.
- Product use. What you do in Zode, from the console, the CLI, the SDKs or CI: for example that a sandbox was created, which client did it, its size and whether it worked. Recorded against your account id and workspace. Never the names you give things, your repositories, commands, file contents or secrets.
- Error reports and logs. When something fails on our side: the route, the error and a stack trace, with email and IP addresses removed before they leave our servers.
- Visits and session replays, only if you allow analytics. Pages you open on zode.dev and in the console, and replays of console sessions in which every word on screen and everything you type is hidden. Without your OK we only count visits, anonymously and without cookies.
We do not read the contents of your sandboxes. Where the sandbox egress proxy handles your secrets or AI provider keys, it records metadata (host, time, status, token counts and cost), never request or response bodies.
Why we use it
- To run the service you asked for: sign you in, run your sandboxes and show you their state and cost.
- To keep it secure: rate limiting, abuse detection and investigating incidents.
- To email you about your account: sign-in links, address confirmation and password resets.
- To answer a beta request, if you made one.
- To find what is broken or confusing and fix it: product use, error reports and logs, and, if you allow them, visits and session replays.
Our legal basis is performing our contract with you; our legitimate interest in keeping the service safe and working, for security, error reports, logs and product use; and your consent, for analytics cookies and session replays. We do not sell your data or use it for advertising.
Who processes it
| Google Cloud | Belgium (europe-west1). Runs api.zode.dev: accounts, sessions, the database and backups. |
|---|---|
| Cloudflare | DNS, and serves zode.dev and the console app at console.zode.dev. Stores beta requests. |
| PostHog | EU Cloud (Frankfurt). Product use, error reports and logs, and, if you allow them, visits and session replays. |
| Resend | Ireland (eu-west-1). Sends account email. |
| GitHub and Google | Only if you choose to sign in with them. |
How long we keep it
Account and workspace data is kept while your account exists. Sandbox telemetry is kept for your plan's retention period, at most 90 days. When you delete a workspace its encryption key is destroyed, which makes its sandbox disks and snapshots unreadable. Audit records are kept as long as the workspace exists. Session replays are deleted after 30 days. Product use, error reports and logs are kept while your account exists and deleted with it. Beta requests are kept until you ask us to remove them.
Your rights
You can turn analytics off any time under Cookie choices. You can ask to see, correct, export or delete your personal data, or object to how we use it, by emailing je@zode.dev. We answer within 30 days. If you are in the EU or UK you can also complain to your data protection authority.
Changes
If we change this policy in a way that matters, we will email account holders before it takes effect.