Cookies
What we store in your browser, and why.
A short and complete list. If something is not on this page, SaidClear does not set it.
Effective 9 August 2026
There is no advertising or analytics cookie
SaidClear runs no advertising network, no third-party analytics and no cross-site tracking, so there is no cookie of that kind to disclose and no banner asking you to accept one. A banner would be theatre: the only cookies here are the ones that sign you in and remember your own settings.
Sign-in cookies
When you sign in, Clerk — our identity provider — sets session cookies on this domain. They are what keeps you signed in between page loads, and they are removed when you sign out. If a deployment has no Clerk key configured, no sign-in exists and no such cookie is ever set.
Language and preferences
Your interface language is carried in the URL, not in a cookie. Your theme, your reading language and your workspace draft are kept in this browser's localStorage. They never leave the device and no server reads them.
The service worker and IndexedDB
A service worker caches the app's own files so the workspace opens without a network. Recordings and their transcripts are held in IndexedDB on this device. Both are storage, not cookies, and neither is sent anywhere by being stored.
Clearing all of it
Settings → Data erases everything this browser holds — the workspace, the preferences and every archived recording — and your browser's own “clear site data” control does the same thing from the outside. Signing out removes the session cookies.