Cookie Policy
Korely is cookieless
Korely.ai does not use cookies for tracking, advertising, profiling, or analytics. The website and the Korely Agents dashboard operate without setting any cookies of their own on your device. This policy describes the technologies we use instead, and any limited exceptions for strictly necessary functionality.
What Are Cookies
Cookies are small text files that websites store on your device to remember information about you. They are commonly used for analytics, advertising, personalisation, and authentication. Under the EU ePrivacy Directive (2002/58/EC, Article 5(3)) and equivalent laws in the UK and other jurisdictions, websites are required to obtain user consent before storing non-essential cookies or other information on your device.
Cookies We Do NOT Use
For full transparency, Korely does not use any of the following:
- Google Analytics, Google Tag Manager, Universal Analytics, GA4
- Facebook Pixel, Meta Pixel, or any social media tracking pixels
- Hotjar, FullStory, LogRocket, or any session-replay tool
- Advertising or retargeting cookies (no Google Ads, no Meta Ads, no programmatic advertising)
- Affiliate tracking cookies
- Third-party widgets that set cookies (e.g., Intercom, Drift, Crisp - we do not use these)
Strictly Necessary Technologies and Preferences
The following technologies are used solely to provide the service you ask for, or to remember a preference you set. They do not require consent under ePrivacy Directive Article 5(3):
| Technology | Purpose | Type |
|---|---|---|
Korely Agents dashboard session (agent.korely.ai) |
Keeps you signed in to the dashboard: the session token, the email address and identifier of your account, the project you have open, your theme, and whether you skipped the setup screen. Signing out removes the session | Local storage on agent.korely.ai (not cookies); strictly necessary, except the theme, a preference you set |
| Sign-in (Firebase Authentication) | Proves who you are when you sign in. Firebase keeps nothing in your browser after you sign in. Signing in with Google, Microsoft or GitHub opens a window served by Google Firebase and by the provider you chose, under their own policies | In memory only, for the duration of the sign-in |
Documentation preferences (korely.ai) |
Remembers the code language tab and the light or dark theme you pick in the documentation | Local storage on korely.ai; a preference you set |
Cloudflare bot management (__cf_bm) |
Distinguishes legitimate users from automated bots and DDoS protection | Strictly necessary cookie, which Cloudflare may set on certain requests to korely.ai; no tracking purpose |
| Payment checkout (Polar) | When you make a payment, checkout is hosted by Polar, our Merchant of Record, on Polar's own domain; any cookies are set there in Polar's third-party context, not on korely.ai | Third-party context only, governed by Polar's own cookie and privacy policy; required to complete a payment |
Audience Measurement (Cloudflare Web Analytics)
For internal audience measurement on the public website korely.ai (page views, referrer, top pages, browser/OS share, country-level geolocation and page-loading speed), Korely uses Cloudflare Web Analytics. This is a privacy-first analytics product from our hosting provider. It measures loading speed from the browsers of real visitors, which requires a small script on the page, so this section describes exactly what that script does and does not do. The Korely Agents dashboard (agent.korely.ai) has no analytics at all.
- No cookies are set. The measurement script contains no reference to
document.cookie. Nothing is written to your browser's cookie store. - Nothing is stored on your device. The script does not use
localStorage,sessionStorageorindexedDB. When you leave the page, nothing of it remains on your machine. - No fingerprinting. The script does not read the canvas, audio or WebGL interfaces that are typically used to build a device fingerprint. It reads your browser's user agent, which your browser already sends with every HTTP request, and timings that the page itself generates while loading.
- No cross-site tracking. Metrics are scoped to korely.ai only and are not shared with any third-party advertising or attribution network. You are not followed from one site to another, because nothing identifies you between one page and the next.
- No profiling. Only aggregated metrics are collected. No user-level profiles are built and no unique-visitor identifier exists.
- IP addresses are not retained at our level. Cloudflare uses the request IP transiently to derive country and to compute aggregate counts, then discards it from the analytics records exposed to Korely.
Content From Other Sites
One blog article loads a library for mathematical notation (KaTeX) from the jsDelivr CDN, which receives your IP address when you open that article. It sets no cookie on korely.ai.
No consent banner required
Consent banners exist because of Article 5(3) of the ePrivacy Directive, which governs storing information on, or gaining access to information already stored in, your terminal equipment. The analytics script writes nothing and reads nothing that was stored, so it falls outside the scope of Article 5(3). What the dashboard and the documentation store in your browser is either strictly necessary to provide the service you ask for, or a preference you set yourself, which the same Article allows without consent. Korely is therefore not required to display a consent banner.
This would change the day we wanted to measure unique visitors rather than visits, because that requires storing an identifier on your device. If we ever do, this page will say so before it happens, and a banner will appear.
Cloudflare, Inc. is contractually bound by a Data Processing Agreement and Standard Contractual Clauses for any incidental processing of EU personal data.
References: ePrivacy Directive Article 5(3); EDPB Guidelines 2/2023 on the technical scope of Art. 5(3) ePD. See also our Subprocessors list.
How to Control Cookies and Site Storage
Because Korely does not use tracking, advertising, or profiling cookies, there is nothing for you to disable on Korely. You can, however, manage cookies and site data in general through your browser settings:
- Chrome: Settings - Privacy and security - Cookies and other site data
- Firefox: Settings - Privacy & Security - Cookies and Site Data
- Safari: Preferences - Privacy
- Edge: Settings - Cookies and site permissions
If you block site data for agent.korely.ai, the dashboard cannot keep you signed in.
When the dashboard's Plan page opens for an account with no active subscription, it asks korely.ai/geo/country for your country, to show prices in your currency. That request sets no cookie and stores nothing on your device; Cloudflare sees your IP address and browser user agent, and we keep nothing of it.
Do Not Track (DNT)
The DNT header is a non-standardised browser signal. Because Korely does not engage in cross-site tracking or profiling regardless of the DNT signal, we treat all visitors with the same minimal-tracking baseline.
Changes to This Policy
If Korely's cookie practices change in the future (for example, if we introduce a feature that requires consent-based cookies), we will update this policy with a new effective date and, where required by law, request your consent through a cookie banner before any non-essential cookie is set.
Contact
For any questions about cookies, audience measurement, or your privacy on Korely:
Korely Privacy Team
Email: privacy@korely.ai
Data Controller: Massimiliano Martella (sole trader)
Address: Via della Bastia 15, 40033 Casalecchio di Reno (BO), Italy
See also: Privacy Policy - Terms of Service - Subprocessors
← Back to Korely