Cookie Policy
Effective August 24, 2026Last updated September 5, 2026
What cookies and browser storage Quodra uses, why, and how to control them.
Quodra uses cookies and similar technologies, including browser storage where applicable, to operate, secure and improve the Service.
Some technologies are strictly necessary for functionality requested by you, such as authentication, security or session management. Other technologies, such as optional analytics, are used only in accordance with applicable consent requirements.
This Cookie Policy explains what technologies Quodra currently uses and how you can control them.
1. What Are Cookies and Similar Technologies?#
Cookies are small text files a website asks your browser to store and send back on later visits. Similar technologies include browser storage mechanisms such as localStorage, sessionStorage and IndexedDB, which let an application keep information on your device — for example, your signed-in session or a presentation you are editing — without sending it anywhere on every request.
This policy covers all of these together, because what matters is the same for each: what is stored, why, and who can read it.
2. Technologies Quodra Uses#
Quodra's application session uses browser storage and an authorization header. Optional analytics can also use cookies when configured and enabled with your consent, as described in section 4.
Quodra uses first-party browser storage — localStorage, sessionStorage and IndexedDB — on the application at app.quodra.app. The documentation pages at quodra.app/docs also store a theme preference.
Optional usage analytics are off by default.
3. Strictly Necessary Technologies#
These make the application work when you use it. They operate without optional consent because the functionality you requested cannot exist without them. They are first-party. Signing out ends the session; local document copies, cached data and preferences can remain until removed through the application or your browser's site-data controls. Signing out is not a full erasure of browser data.
| Storage | Kind | Purpose |
|---|---|---|
quodra.api.session.v1 | localStorage | Your signed-in session (who you are, and the tokens that authenticate your requests) |
quodra:sync:queue:…, quodra:sync:metadata:…, quodra:sync:conflicts:… | localStorage | The outbox that saves your edits locally first, so work survives a lost connection, then syncs to your cloud library |
quodra (documents, recoveries, journals) | IndexedDB | Your presentations on this device — the local copy the editor works from |
quodra-circuits, quodra-molecules, quodra-matter-datasets | IndexedDB | Circuits, molecules and datasets you create or upload, stored locally |
quodra:code-trust:… | localStorage | Your per-presentation decision about whether its Python code may run |
quodra:analytics-consent | localStorage | Your analytics choice itself — remembering "no" requires storing "no" |
quodra:last-correlation-id | sessionStorage | A short-lived error reference id, so a bug report can name the failure; cleared when the tab closes |
4. Analytics Technologies#
Optional usage analytics require deployment configuration and your opt-in. The application supports PostHog; the presence of that integration alone does not establish that collection is active. When configured:
- It is off by default and starts only after you turn on "Usage analytics" in Settings → Diagnostics & analytics inside the application.
- With your consent it records a small, fixed list of product events (for example "a presentation was created") with identifiers and counts — never the content of your work.
- It uses localStorage and cookie persistence for its identifier. Automatic page capture and session recording are disabled.
- Turning the switch off stops collection, discards the pending queue and resets the stored identifier. You can change your mind in either direction at any time.
Separately, error diagnostics (Sentry) operate only when configured for the deployment and are not controlled by the usage analytics switch. When operated, they support our legitimate interest in keeping the Service working. Reports may contain an account identifier, error details and technical context. Filtering redacts sensitive field names and recognized tokens, email addresses and URLs before sending, but cannot guarantee removal of every sensitive detail from arbitrary error text.
Operational logs from hosting and the API support reliability and security independently of optional analytics and browser diagnostics. See the Privacy Policy for technical information we may process and the Subprocessors page for the providers involved.
5. Functional Technologies#
These remember choices you make so the application behaves the way you left it. All are first-party browser storage, optional in the sense that the product works without them, and created only by your own actions.
| Storage | Purpose |
|---|---|
quodra-theme, quodra-docs-theme | Light or dark appearance, in the app and the docs |
quodra:tour:… | Which onboarding tours you have already seen |
quodra-folders | The folders you created to organize your library |
quodra-code-prefs, quodra-inspector-w, quodra-rail, quodra-insp, quodra-isec-…, quodra-circuit-panels | Editor layout and code-editor preferences |
quodra-pv-side, quodra-laser, quodra-board-surface | Presenter-mode preferences |
quodra:share-url:… | Share links you created on this device, so reopening the share dialog shows the same link instead of pushing you to mint a duplicate |
quodra:mp-api-key | A Materials Project API key you chose to enter, kept on your device for your own use of that integration |
6. Local Storage and Other Browser Storage#
The storage entries described above are held in your browser. The application uses stored session credentials to authenticate requests and syncs cloud-account content to the Service; configured, consented analytics also transmit their named events. Browser storage is therefore not a promise that the associated information stays only on your device. Clearing Quodra's site data removes local copies, including unsynced edits. Let a sync finish or export your work first.
7. Third-Party Technologies#
Some functionality causes your browser to contact third parties directly. They receive your IP address and standard request information; the other data involved depends on the feature.
- Google Fonts (
fonts.googleapis.com,fonts.gstatic.com) — serves the typefaces. - jsDelivr (
cdn.jsdelivr.net) — serves the Python scientific runtime (Pyodide) and its packages. Package downloads identify the requested files; Python computation runs in your browser. Code or integrations you choose to run can make additional network requests. - Google Sign-In and Google Drive (
accounts.google.com,apis.google.com,www.googleapis.com) — contacted only if you sign in with Google or import a file from Google Drive. The Drive integration can read only files you individually pick. Google's own cookies on Google's domains are governed by Google's policies. - Cloudflare — hosts Quodra's static websites and application files. It also hosts the MCP endpoint, which handles authorized requests from external clients and can carry deck content.
- Google Cloud — hosts Quodra's production API, database, object storage and operational logs. Signed-in use can send account information and User Content to that API, separately from optional analytics.
8. How to Change Your Preferences#
- Usage analytics: open the Quodra application → Settings → Diagnostics & analytics → the "Usage analytics" switch. Off is the default; collection also requires deployment configuration.
- Appearance: the theme toggle in the app and on each docs page.
- Browser storage and cookies: use your browser's site-data controls to view, restrict or clear data for
app.quodra.appandquodra.app. This removes local data, not the cloud copy of an account or its content. Google's own cookies are controlled on Google's domains.
If Quodra ever introduces technologies that require consent beyond what is described in this policy, it will ask first — nothing non-essential is activated by default or by implication.
9. Changes to This Cookie Policy#
We may update this Cookie Policy as the Service evolves. When we make changes, we will update the "Last Updated" date above. If a change introduces a technology that requires your consent, it will not run until that consent is requested and given.
10. Contact#
Questions about this Cookie Policy may be submitted by email: hello@quodra.app
Product: Quodra