1. This website stores almost nothing
The Cofleet marketing site runs no analytics and no advertising pixels, which is why there is no banner on it. The current demo and waitlist forms ask only for your email address. It is sent when you submit and is not saved to browser storage. Earlier questionnaires also asked for company size and needs. What we do with it is in the Privacy Policy. A few things still touch your browser here, and none of them needs your permission:
- If you unlock the private preview, we remember it for the rest of the tab so the next preview page does not ask again. Closing the tab forgets it.
- Our network provider, Cloudflare, may set a security cookie when it checks whether traffic is automated. We do not control when that happens, and at the time of writing no such cookie is issued on this site.
The site also loads fonts from Google's font service, which means Google receives your IP address and user agent as part of that request. That sets no cookie, but it is a transfer, so it is named on the DPA's Subprocessor List.
The remaining register describes application browser storage. The desktop app also keeps local session and interface settings. Earlier Cofleet versions used other storage names, including cofleet-theme (the website's former light/dark switch), cofleet_session, cofleet_oauth_csrf, google_oauth_state, pending_google, cofleet_board_share, graph.* preferences, otto:map-style and otto:map-show-memories; old browser profiles may retain those until cleared.
2. The full register
Local and session storage do the same job as a cookie and the law treats them the same way, so they are listed alongside them. Where a family of keys shares a prefix it gets one row; the prefix is exact, so you can find every member in your browser's developer tools. This table is meant to be complete — if Cofleet set something it does not describe, that is a bug in this page, and we would like to hear about it.
| Name | Kind | Purpose | Category | Retention |
|---|---|---|---|---|
| cofleet-preview-unlocked | Session storage | Website preview unlock for this tab. | Strictly necessary | Until the tab closes |
| otto:session@<API URL> | Local storage | Web app sign-in token and connection settings. Sign-out clears the token. The desktop app stores its session through native storage instead. | Strictly necessary | Until sign-out or storage is cleared; the server session expires after 30 days |
| otto:session@<API URL>#tab | Session storage | Web app workspace/brain selection for the current tab and a sign-in fingerprint to clear that selection when the account changes. | Strictly necessary | Until the tab closes or selection is cleared |
| otto_oidc_state | Cookie | Google/Microsoft sign-in state, nonce and verifier to protect the sign-in or identity-linking flow. | Strictly necessary | 10 minutes; cleared on callback |
| otto_registration | Cookie | Opaque reference to a pending registration attempt; protects registration and email verification before account creation. | Strictly necessary | 10 minutes; cleared on completion |
| otto_registration_invite | Cookie | Preserves an owner invitation while continuing to Google or Microsoft sign-in. | Strictly necessary | 10 minutes; cleared when registration starts |
| otto_session | Cookie | Short-lived authentication for the app’s OAuth authorisation pages. | Strictly necessary | 10 minutes |
| otto_mcp_request | Cookie | Pending connected-tool authorisation request. | Strictly necessary | 10 minutes |
| otto_drive_consent, otto_notion_consent, otto_slack_consent, otto_github_consent, otto_slack_sign_in | Cookie | Bind an explicitly requested connector authorisation or Slack account link to the signed-in user and anti-forgery state. | Strictly necessary | 10 minutes |
| cofleet:usage-stats | Local storage | Your answer on this device to the app's cookie banner. Until you choose Accept all, the app does not report when you open it. | Strictly necessary | Until changed in Settings → Privacy or cleared; clearing it makes the app ask again |
| sidebar_state | Cookie | Whether the app's sidebar was left open or closed. | Strictly necessary | 7 days |
| otto:last-sign-in-provider | Local storage | The sign-in provider (Google or Microsoft) last used on this device, so the sign-in page can mark it "Last used". It names no account. | Strictly necessary | Until replaced or cleared |
| otto:signin-nonce, otto:signin-next | Session storage | Protect web sign-in and return to the requested page. | Strictly necessary | Until consumed or the tab closes |
| otto.chunk-reload-at | Session storage | Prevent repeated reloads when an application update changes asset files. | Strictly necessary | Until the tab closes |
| cofleet:connector-return:<workspace ID> | Session storage | Return to the selected app page after connecting a source. | Strictly necessary | Until consumed or the tab closes |
| cofleet:desktop-consent:<workspace ID> | Session storage | Marks a source connection the desktop app handed to the browser, so the browser can offer to return to the desktop app when it finishes. | Strictly necessary | Until consumed or the tab closes |
| otto:theme, cofleet:recent-chats-expanded, cofleet:sidebar-width, cofleet:chat-context:<user ID>:<workspace ID> | Local storage | App theme, recent-chat expansion, the section sidebar width the person set and chosen chat context; selected context can include brain/source references. | Strictly necessary | Until replaced or cleared |
| otto:memory-limit, otto:nebula-distribution, otto:map-color-by, otto:map-dimension | Local storage | Memory map view settings: how many memories it loads, its layout, colouring and 2D or 3D view. | Strictly necessary | Until replaced or cleared |
| otto.import-failures.<workspace ID>.<brain ID> | Local storage | Which failed imports in a brain you were already told about, so the same failure is not announced twice. | Strictly necessary | Until replaced or cleared |
| cofleet:tour|<user ID>|<step>, cofleet:quick-save-shown | Local storage | Which guided-tour steps you finished and whether the desktop app already showed its quick-save step, so neither repeats. | Strictly necessary | Until replaced or cleared |
| cofleet:touring, cofleet:arrival | Session storage | Whether you chose the guided tour, and the first appearance of the app after onboarding. | Strictly necessary | Until the tab or window closes |
| ["cofleet:brain-creation", <API URL>, <user ID>, <workspace ID>] | Local storage | Track requested brain creation and show completion notifications; the key is a JSON array. | Strictly necessary | Entries removed when acknowledged; otherwise until cleared |
| __cf_bm, cf_clearance, _cfuvid | Cookie | Cloudflare security checks when enabled. These are conditional provider cookies, not analytics. | Strictly necessary | Provider/configuration-dependent; __cf_bm typically 30 minutes, _cfuvid for the browser session, cf_clearance for the configured challenge-passage period |
Strictly necessary means it exists to deliver something you asked for: staying signed in, not being asked the same question twice, keeping the interface the way you left it, or letting a security check tell you apart from a bot. Under the ePrivacy rules these do not need your consent. You should still know they exist, which is why they are listed.
Every row above is strictly necessary, including the one that keeps your cookie banner answer. This site and the app set no analytics cookie, run no session replay and load no third-party analytics script. The app's cookie banner asks one question, about usage statistics, described in section 3. When enabled, the packaged desktop app and the browser dashboard also send restricted error reports to Sentry; they store nothing in your browser and carry no content (see Error diagnostics in the Privacy Policy).
The GitHub consent cookie supports the GitHub connection flow when that connector is enabled. Its presence in this register does not represent availability in a particular deployment.
3. Usage statistics, and what our servers record
Usage statistics, only if you accept them. The first time you open the app in a browser or the desktop app, a cookie banner asks for your choice. If you choose Accept all, that browser or app tells our servers when you open it, as a fixed category without content, names or item identifiers, and our servers pass these counts to PostHog. Until you answer, or if you choose Necessary only, it reports nothing. Your answer is kept on that device as cofleet:usage-stats, and you can change it any time in Settings → Privacy.
Our servers also record which other features ran for your account, from requests the service needs anyway: identifiers and counts, with no analytics cookie or other browser storage involved. These records are covered by the Privacy Policy.
When enabled, our servers send product usage events, AI call metadata and daily and month-to-date model-cost totals per workspace to PostHog's EU cloud (eu.i.posthog.com), and use user identifiers for feature availability checks. DPA 1.3 limits these analytics to service operation, reliability, service improvement and customer usage/cost understanding where offered; an organisation’s previously accepted DPA continues to control until it expressly accepts a new version. They describe which features ran, which model was used, token counts, latency and model cost, with identifiers and fixed category labels. They contain no documents, source text, prompts, outputs, memory content, names, email addresses, URLs, window titles or raw error messages. There is no browser analytics SDK or session replay.
The usage statistics switch is the only product-analytics choice in the app. Clearing browser storage does not disable server-side telemetry; it forgets your cookie banner answer, so the app asks again. Applicable rights, including the right to object to legitimate-interest processing, remain available through markus@cofleet.app as described in the Privacy Policy.
4. Changing your mind
Every entry in the table above is strictly necessary, so the one thing to change is your usage statistics answer: open Settings → Privacy in the app and turn Usage statistics on or off. The change applies at once to that browser or desktop app; each keeps its own answer.
Your browser can still block or delete cookies and storage for a site. That works, though clearing the strictly necessary ones will sign you out and forget how you had the interface set up.
The other server-side records in section 3 sit outside browser controls. Your rights over them, including the right to object, are in the Privacy Policy.