This notice covers cookies and equivalent local-storage mechanisms that KINDI sets on the kindi.me, www.kindi.me, dashboard.kindi.me, admin.kindi.me, docs.kindi.me, and api.kindi.me hosts. KINDI does not use third-party cookies for any purpose on any of these hosts.

The developer documentation at docs.kindi.me sets no cookies. The API host at api.kindi.me sets no cookies of its own beyond the two session cookies described in § II, which it issues on sign-in for the dashboard and the administrative console to consume.

Two cookies, both strictly necessary for the service to function. Neither can be opted out of without disabling sign-in.

Both cookies are set with the HttpOnly, Secure, and SameSite=Lax attributes, and are signed under a server-side secret. The session value is opaque and cannot be decoded by the browser or by any party other than KINDI.

The marketing pages at kindi.me and www.kindi.me set no cookies of their own. Because the session cookie is issued for the whole kindi.me domain, a signed-in browser will present it to those pages, which neither read it nor act on it.

One item of session storage is written on the marketing site. The landing page’s masking demonstration records a flag named kindi-demo-stamped so the animation does not replay on every visit within the same browser tab session. It holds no identifier, is readable only by kindi.me, and is discarded when the tab closes.

KINDI does not set, and does not permit any third party to set, the following on its domains.

• Analytics cookies (no Google Analytics, no Mixpanel, no equivalents).
• Advertising or retargeting cookies.
• Social-media tracking pixels.
• Cross-site identifiers or fingerprinting equivalents.

Site usage is observed only through server-side request logs. Those logs set nothing in your browser and carry no cookie value and no cross-site identifier. They do record the IP address a request came from, which the Privacy Notice lists as personal data and which is kept for the period stated there.

You may clear or block KINDI cookies in your browser settings at any time. Blocking the session cookie disables sign-in; the service will be unable to recognise you between requests, which means you cannot access the dashboard, the playground, your keys, your billing, or the admin console. The public marketing pages remain available.

If KINDI introduces any additional cookie, including a first-party analytics cookie, this notice will be updated at least 14 days before the change takes effect, and the change will be summarised in the version line at the head of this document.