STRICTLY NECESSARY COOKIES & LOCAL STORAGE POLICY
Atom Forge Studio uses only essential authentication cookies and local browser storage required to operate the application, preserve your chat history, and secure your sign-in session. We do not use third-party advertising, retargeting, or cross-site tracking cookies.
1. How We Use Cookies & Browser Storage
When you use Atom Forge Studio, your browser stores small, strictly necessary data items via HTTP cookies, localStorage, and sessionStorage to maintain your workspace state without requiring you to re-authenticate on every page refresh.
2. Inventory of Cookies & Local Storage Keys
- Session Authentication (
atom_session_token,atom_cached_user): Strictly necessary to authenticate your API requests and synchronize your account across tabs. - Google OAuth & Firebase Security Tokens: Used during Google Sign-In to verify OAuth 2.0 state parameters and prevent Cross-Site Request Forgery (CSRF).
- Account-Scoped Conversation History & Studio Vaults (
atom_studio_chats_*,atom_studio_artifacts_*,atom_extended_thinking): Stored locally per signed-in user so your active coding sessions, artifacts, and model settings remain isolated and persist between visits.
3. Managing & Clearing Cookies
You can clear all locally stored chat sessions at any time using the Clear All History button in the application sidebar, by signing out, or by permanently deleting your account via Account Profile → Delete Account & Data. You may also clear or block cookies directly in your browser settings. For privacy inquiries, email suresh@atomforgestudio.space.