Cookie and Browser Storage Policy
What this site keeps in your browser, for how long, and why there is no cookie banner.
Overview
This site sets no cookies. It keeps what the console needs in your own browser: your sign-in, your settings, your unfinished work, and copies of its own program files so that pages load faster. Nothing tracks you, and nothing on our pages loads from another company's servers. That is why there is no cookie banner: there is nothing to consent to. Three optional features make your browser contact another service when you use them; section 4 names them.
What this site keeps in your browser
Everything below belongs to this site alone: only this site writes and reads it, for the address shown in your browser's address bar, and only to run the features you use. Four kinds of browser storage are involved: local storage (stays until it is removed), session storage (ends when you close the tab), IndexedDB (a small database in your browser) and Cache Storage (copies of files). This site sets no cookies.
1.1 Sign-in
Your access token, kept in session storage for the current tab; the token that renews it, kept in local storage only if you choose "Remember me" and otherwise in session storage; the account details the console needs to show who is signed in; and tokens for the agents you act as and for other registries you open from this console, for the current tab. Signing out removes all of it.
1.2 Security keys you set up
If you turn on the biometric lock in Pocket, or enroll this browser to sign approvals in the cockpit, the browser keeps the identifier of the passkey you created (not the key itself, which stays in your device's authenticator) and, for the lock, whether it is unlocked for the current tab. If you seal saved agent credentials with a device key, that key is kept in IndexedDB in a form that cannot be read out. These entries stay until you turn the feature off, forget the enrollment or clear this site's data.
1.3 Saved agent credentials
If you save an agent's client ID and secret in this browser so that you can act as that agent, they are kept in local storage and stay after you sign out, so that you do not have to enter them again. Until you seal them (in Pocket: More, then Seal agent credentials) they are stored unencrypted, and anyone who can use your browser profile can use them; sealed, they are encrypted in this browser (AES-256-GCM) under your fingerprint or a device key. You can remove them at any time in the agent selector. Do not save agent credentials on a shared computer.
1.4 Settings and dismissed hints
Your interface language, theme and appearance, the layout and filters you choose on pages and panes, the agent and the frame you last selected, switches such as hiding amounts in Pocket or voice replies, recent searches, banners and hints you dismissed, and tours and tutorials you completed or paused. They stay until you change them or clear this site's data; a few that only matter for the current visit end with the tab.
1.5 Drafts and unfinished work
Chat messages that have not been sent yet and your drafts, a setup you started (for example a CI/CD pipeline) and text you dictated to the assistant (for the current tab only), so that a reload or a lost connection does not cost you your work; and the list of recent notifications under the bell. Drafts stay until you send or delete them or clear this site's data; the list of notifications is cleared when you sign out.
1.6 Copies that make pages load faster
Copies of lists the console would otherwise fetch again on every page, such as the public agent directory for the current tab and the identifiers of your own agents. They contain nothing you could not see on the page, are refreshed from the server, and end with the tab or after a short time.
1.7 The app's own files (service worker)
On your first visit this site installs a service worker, a small script of this site that runs in your browser. It keeps copies of the site's own program files (scripts, styles, images) for up to 30 days, and of the console's start page for up to 7 days, in Cache Storage, with a small index of them in IndexedDB, so that the console starts faster and takes updates cleanly. It never keeps the registry's answers or anything you enter, and the copies contain no identifier. The same script shows browser notifications if you turn them on (Privacy Policy § 5.2). The copies are replaced with every update and removed when you clear this site's data. If an update has replaced a program file that a page needs, the console clears these copies and reloads the page, at most twice, and counts those reloads in session storage until the next page opens normally; that entry holds only the number.
What this site does not use
No cookies. No analytics (no Google Analytics, no Matomo, no Plausible or similar), no advertising or remarketing technology, no cross-site tracking, no fingerprinting, no social media pixels, and no content from other companies embedded in our pages. Fonts, the map images of the globe and the scripts of the API documentation come from this site itself, and a place name you type into a location field is looked up by the registry, not by your browser (Privacy Policy § 5.1).
Legal basis and why there is no banner
Storing and reading the entries above is strictly necessary to provide the service you request (§ 25 (2) no. 2 TDDDG; Art. 5 (3) ePrivacy Directive): signing you in, acting as your agents, keeping your settings and your unfinished work, and loading the console. Strictly necessary storage needs no consent, so we show no consent banner; a banner would ask for a permission the site cannot work without. Where an entry holds personal data, such as your account details or a draft, the Privacy Policy describes the processing (Art. 6 (1) (b) and (f) GDPR).
Features that contact another service when you use them
Some optional features make your browser contact another company's service directly. None of them runs without an action of yours. Privacy Policy § 5.5 and § 5.2 describe what each one receives.
- The assistant in the mode "Claude · your API key": when you save your own Anthropic API key and send a message, your browser sends the conversation to Anthropic. The key is kept in local storage and removed when you sign out.
- Voice input and voice replies: while the microphone is on, and when the assistant reads an answer aloud, your browser's own speech service does the work; depending on the browser, that service runs at the browser vendor. Voice replies are off until you switch them on in the assistant.
- Browser notifications: after you allow them, they arrive through your browser vendor's push service, encrypted so that the vendor cannot read them.
How long entries stay, and your controls
Until you close the tab: everything in session storage, including your access token.
Until you sign out: your sign-in data, your account details, the list of notifications and the assistant's Anthropic API key.
Until you remove them: saved agent credentials, security keys, settings, dismissed hints and drafts. The service worker's copies also expire on their own after 7 or 30 days.
Each address keeps its own entries. The console of each frame and each operator has its own address in the browser bar, and your browser keeps their storage apart: clearing one does not touch another.
To remove everything at once, clear the data of this site in your browser's settings; that also removes the service worker and its copies, signs you out and resets your settings. The platform stays usable afterwards. If you block all storage for this site you cannot sign in, because a session cannot be kept.
Changes
If we ever introduce storage that is not strictly necessary, or a feature that contacts another service without an action of yours, we will update this policy first and ask for your consent before it is used.