Cookie Policy
Enough browser storage to keep you signed in and remember your theme. No advertising, no analytics, no third-party tracking — there is genuinely nothing else here.
The short version
Sage uses the minimum browser storage required to keep you signed in, remember your interface preferences, and protect the account system from abuse. There are no advertising cookies, no analytics cookies, no social media pixels, and no third-party trackers following you between sites. Nothing on this site is sold to a data broker, because nothing on this site is collected for one.
This page is about the web app
Cookies are a browser mechanism. The sage-ai-cli tool you install with pip does not use them — it stores an authentication token in a local configuration file on your own machine, and that token never travels through a browser. The iOS and Android apps use the platform's secure storage rather than cookies. Everything below applies to sageworksai.com in a browser.
Strictly necessary storage
These cannot be turned off without breaking the product, because they are what makes a signed-in session possible:
•
Session and authentication — a token that proves you are signed in, so you are not asked to reauthenticate on every page. Set when you sign in with Google or Apple; cleared when you sign out.
•
Sign-in flow state — short-lived values used during the OAuth handshake to match the response to the request you started. These expire within minutes of completing sign-in.
•
Security tokens — values used to prevent cross-site request forgery on actions that change your account or billing.
Preference storage
These remember how you like the interface. They live in your browser's local storage rather than being transmitted with every request, and losing them costs you nothing but a reset to defaults:
•
Theme — whether you chose light or dark. Stored locally under a single key; the default is dark.
•
Selected model — the model you last picked, so the chat does not reset your choice on reload.
•
Interface state — small things like whether the sidebar is collapsed.
Third parties we do allow
Two categories of third party can set storage on our domain, and both are functional rather than commercial:
•
Identity providers — Google and Apple, during sign-in only. They are the ones authenticating you; their own privacy policies govern what they do on their side.
•
Payment providers — PayPal, Apple Pay, and Google Pay, during checkout only. They handle payment credentials so that Sage never receives or stores your card details.
There is nothing else. No Google Analytics, no advertising network, no session replay tool recording what you type, no embedded social buttons phoning home.
Controlling cookies yourself
Every major browser lets you view, block, and delete cookies and local storage per site, usually under privacy or site settings. Clearing Sage's storage signs you out and resets your theme and model preferences to defaults — nothing else is lost, and your account, conversations, and billing are unaffected. Blocking cookies for sageworksai.com entirely will prevent you from staying signed in, which means the web app cannot work. The CLI will continue to work regardless, since it does not depend on the browser.
Do Not Track
We honour Do Not Track by default, in the sense that there is nothing to honour: we do not track you across sites whether you send the header or not.
Changes and contact
If we ever add a category of storage beyond what is described here, we will update this page and the revision date below before it ships. Questions about cookies, storage, or anything else on this page: support@sageworksai.com. For the fuller picture of what Sage collects and how to delete it, see our Privacy Policy.
Last updated: July 24, 2026