Back to CodeOrbit
Cookies Policy
This page explains how CodeOrbit uses cookies and browser-side storage, especially for sign-in and temporary coding sessions.
Last updated: April 9, 2026
What this page covers
- This page explains how CodeOrbit uses cookies, local storage, and similar browser-side storage.
- It is written in simple language so users can understand what stays in the browser and what does not.
Essential cookies
- If you choose to sign in, CodeOrbit and its authentication provider may use essential cookies to keep your session active and secure.
- These cookies help basic account flows work correctly, such as sign-in, sign-out, and protected account actions.
- The consent modal now lets users choose between Necessary Only and Accept All on a per-browser basis.
Browser storage for product state
- Some signed-in experiences may use browser storage to remember editor preferences or restore synced workflows faster.
- Guest playground sessions are intentionally treated as temporary, so refreshing the page without being signed in should reset that local coding state instead of restoring old work.
What we do not promise
- Third-party services such as authentication, hosting, analytics, or AI providers may have their own cookie behavior.
- If you deploy CodeOrbit publicly, you should review all connected services and update this policy for your exact setup.
Your control
- If you choose Necessary Only, CodeOrbit should only rely on essential storage needed for the product to function correctly.
- If you choose Accept All, CodeOrbit can remember the broader consent preference for future optional browser-side features.
- You can clear cookies and browser storage through your browser settings at any time.
- If you clear storage, signed-out temporary state and some saved browser-side preferences may disappear.
If you run CodeOrbit as a public product, review this cookies policy together with your privacy policy and the exact behavior of every connected service.