Legal
Last updated: 16 October 2026
This Cookie Policy explains how Disqua ("we", "our", "us") uses cookies and similar technologies when you visit disqua.com or use the Disqua console application at console.disqua.com. We have designed our cookie usage to be minimal and privacy-respecting. The website and the Service are operated by:
Baby Data s.r.o.
Roháčova 188/37, 130 00 Praha 3 — Žižkov, Czech Republic
Company ID (IČO): 06956042 · VAT ID (DIČ): CZ06956042
Registered in the Commercial Register maintained by the Municipal Court in Prague, Section C, Insert 291953
Email: privacy@disqua.com (data protection) · hello@disqua.com (general)
Cookies are small text files that are stored in your web browser when you visit a website. They allow the website to recognise your browser on subsequent visits and remember certain information about you, such as your login session or preferences. Cookies are widely used to make websites function properly and to provide information to the website's owners.
Cookies can be classified in several ways:
Disqua uses a very small number of strictly necessary and functional cookies. We do not use advertising cookies, retargeting cookies, or any cookies that track your behaviour across websites. All cookies we set are first-party cookies, scoped to disqua.com and its subdomains (such as www.disqua.com and console.disqua.com).
The following list describes every cookie set by Disqua:
Purpose: Session cookie of the Disqua console application (console.disqua.com). It contains only a random session identifier; the session itself (including your login state and the CSRF protection token that secures form submissions) is stored on our servers. Without this cookie you cannot stay logged in.
Expiry: 7 days, extended while you are active.
Can it be disabled? No. This cookie is strictly necessary for the Service to function.
Purpose: Set by the console for disqua.com and its subdomains while you are logged in, so that the marketing website can show a "Dashboard" link instead of "Log in". It contains only your display name (shortened) and is not readable by scripts.
Expiry: 7 days; removed when you log out.
Can it be disabled? Yes. Deleting it has no effect other than the website showing the "Log in" link.
Purpose: Stores your language choice in the Disqua console when you switch the language. The marketing website does not need this cookie — its language is part of the page address (for example /de/).
Expiry: 1 year.
Can it be disabled? Yes. Without it, the console falls back to its default language selection.
Purpose: Set on www.disqua.com only if you choose to view the previous design of the website; it remembers that choice.
Expiry: 30 days.
Can it be disabled? Yes. Without it, the current design is shown.
The console stores your light/dark theme preference in your browser's local storage, and — to support offline reading and writing — keeps a local copy of recently opened conversations (IndexedDB and the service worker cache). This data stays on your device and is not a cookie; the offline copy of conversations is deleted when you log out.
Payments are completed on pages hosted by Stripe (checkout.stripe.com and billing.stripe.com). Stripe may set its own cookies on those pages, which are governed by Stripe's own cookie and privacy policies.
We do not use the following types of cookies or tracking technologies:
We use OpenAnalyticsAPI to count page views on www.disqua.com, console.disqua.com and status.disqua.com, so we can understand which pages are used and improve them. OpenAnalyticsAPI is operated in the European Union and does not use cookies; IP addresses are anonymised.
Instead of cookies, the analytics script stores a randomly generated identifier in your browser's localStorage (_oaa_uid) and a short-lived session identifier in sessionStorage (_oaa_sid, renewed after 30 minutes of inactivity). These identifiers do not contain your name, email address or account details and are not used for advertising or shared with advertising networks. If an opt-out has been recorded, the script stores an opt-out flag (_oaa_optout) and stops sending page views. You can also remove these entries at any time by clearing your browser's site data for disqua.com.
Our analytics provider is listed on our Sub-processors page.
You can manage, restrict, or delete cookies through your browser settings. Below are instructions for the most common browsers. Note that disabling the strictly necessary session cookie (connect.sid) will prevent you from using the Disqua console.
Go to Settings → Privacy and security → Cookies and other site data. You can clear all cookies, block cookies by site, or see all cookies currently stored in your browser.
Go to Settings → Privacy & Security → Cookies and Site Data → Clear Data. You can manage exceptions to allow or block cookies per site under Manage Exceptions.
Go to Preferences → Privacy → Manage Website Data. You can remove all website data or remove data for specific sites. On iOS, go to Settings → Safari → Clear History and Website Data.
Go to Settings → Cookies and site permissions → Manage and delete cookies and site data. You can see, block, and delete cookies per site.
For more information about managing cookies, visit allaboutcookies.org.
We may update this Cookie Policy from time to time to reflect changes in our cookie usage or applicable law. When we make material changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically. Continued use of the Service after any changes constitutes acceptance of the updated policy.
Last updated: 16 October 2026.
If you have questions about our use of cookies or this Cookie Policy, please contact us at:
privacy@disqua.com