Zerethon IDE
Sign in

Privacy policy

Last updated: 23 October 2026

This policy covers Zerethon IDE (ide.zerethon.com), the online code editor of Zerethon. It says what the IDE stores, for how long, and what leaves it. The general Zerethon privacy policy covers your Zerethon account and the rest of the ecosystem.

Your account

You sign in with your Zerethon account. The IDE receives your account id, name, email address and avatar from Zerethon sign-in; it never sees your password and does not keep sign-in tokens. You can use the editor and run code without an account.

What the IDE stores

  • Projects (signed in): the files, name, language and program input you save. They are private to you and kept until you delete them.
  • Run history (signed in): for each run, the language, status, exit code, timing and the program's output. The code itself is not kept with the run. History is limited to your 50 most recent runs and deleted after 14 days.
  • Runs without an account: the same run record, linked to your browser session by a random token of which only a one-way hash is stored, and counted per network address using a keyed hash — the address itself is not stored. These runs are deleted the day after.
  • Share links: when you share a saved project, a frozen copy of it is stored and anyone with the link can view it until the link expires (1, 7 or 30 days) or you revoke it. The link itself is stored only as a hash. Expired and revoked copies are deleted 30 days later.
  • Skills progress (signed in): which Skills topics you marked as learned or unmarked, and when. Nothing else — not which pages you read. Kept with your IDE account until you use “Reset my progress” on the Skills page, which deletes it (only the time of the reset is kept, so other devices clear their copy too).
  • Server logs: run ids, languages, statuses and durations to keep the service working. Logs never contain your code or its output.

Where your code runs

Each run happens in a fresh, isolated container with no network access, removed when the run ends. The copy of your files made for the run is deleted with it.

Sent elsewhere only when you ask

  • Fix Code and “Generate tables and sample data” (signed in): the code you selected, its problems and, if you tick it, the last run's error are sent to Zerethon Workspace, which uses an AI model to propose a change. This model may be provided by a third-party AI provider. The confirm step shows exactly what is sent; nothing is sent until you press the button. The IDE keeps only a fingerprint (hash) of the code and the request status, for 14 days; Zerethon Workspace keeps the request as a task record.
  • Code completion and error checking: the files you have open are analysed by the IDE's own language server to suggest completions and show errors. They are held only for your editing session and deleted when it ends. Your code is never run there.

Cookies and browser storage

  • A session cookie and a security (CSRF) cookie, needed to sign in and to protect forms.
  • A cookie with the interface language you chose.
  • In your browser only (local storage): your light/dark theme and, when you are signed out, the code you are editing, so a reload does not lose it. It is removed when you discard it or save it to your projects after signing in.
  • In your browser only (local storage): the Skills topics you marked as learned. Signed in, they are also merged into your account (see above).

The IDE shows no ads and uses no third-party analytics or tracking.

Your choices

  • Delete a project or clear your run history at any time in the editor.
  • Revoke a share link at any time.
  • Reset your Skills progress at any time on the Skills page.
  • Clear your browser's storage for ide.zerethon.com to remove anything kept there.
  • Manage or delete your Zerethon account in Zerethon Account.

Contact

Questions about privacy: hello@zerethon.com. We will update this page when the IDE changes what it stores.