Cookie Policy

Cookies are small text files stored by your browser when you visit a website. They allow websites to remember information about your visit, such as your login status and preferences. Cookies can be “session” cookies (deleted when you close your browser) or “persistent” cookies (stored for a set period).

Similar technologies include localStorage and sessionStorage, which we also use for storing non-sensitive user preferences (e.g., UI theme selection, dismissed banners).

Quantinger's authentication does not use a cookie at all — your login session is held in your browser's local storage, sent as an Authorization header, not as a cookie. The table below lists every cookie the codebase actually sets, checked directly in-browser rather than assumed from a generic template:

Verified by direct in-browser inspection and a cold HTTP request against the live site on 2026-08-10 — this table describes what is actually set today, not a generic list of cookies a site like this typically has.

We do not currently set any functional, analytics, or marketing/advertising cookie — confirmed by inspecting the frontend source directly (no Google Analytics, no tag manager, no advertising pixel is wired anywhere in the code). This is not a policy promise about the future: the Content-Security-Policy header does pre-authorize google-analytics.com and googletagmanager.com as infrastructure readiness, so that an analytics integration can be added later without a separate infrastructure change. If and when that happens, this policy — and the consent banner's actual gating behavior for that new, non-essential cookie — will be updated and tested before it ships, and fresh consent will be obtained rather than assumed.

We will never use analytics data, if and when it exists, to build advertising profiles or sell insights about you to third parties.

We do not use advertising cookies, retargeting pixels, or third-party tracking tags of any kind. There is no Facebook Pixel, Google Ads tag, or similar technology on Quantinger.

Some third-party services we use may set their own cookies, conditionally, on specific pages — see the verified table in Section 2 for what was actually observed:

• Cloudflare — cf_clearance and __cf_bm cookies are set only when its bot detection / DDoS protection challenge triggers, not on every visit. When set, they are security-necessary and operate under Cloudflare's privacy policy.
• Vercel — may set cookies for routing and performance optimisation on the frontend CDN.
• Paddle — sets cookies on the checkout/billing page only, for payment processing and fraud prevention under Paddle's own terms.

Our consent banner: On your first visit, a banner appears at the bottom of the screen. You can choose “Accept All” (strictly necessary + analytics when available) or “Strictly Necessary Only”. You can revisit this choice via the “Cookie settings” link in the footer.

Browser settings: All modern browsers allow you to view, manage, and delete cookies. Disabling strictly necessary cookies will prevent you from logging in or using the Service.

• Chrome: Settings → Privacy and security → Cookies and other site data
• Firefox: Settings → Privacy & Security → Cookies and Site Data
• Safari: Settings → Privacy → Manage Website Data
• Edge: Settings → Cookies and site permissions

For questions about our use of cookies: support@quantinger.com