Cookie policy
Last updated: May 2026 · NKZ OS / Nekazari
1. Who we are
This policy describes cookies and similar technologies used when you browse documentation on nkz-os.org and when you use the Nekazari web application served from the production domain shown in your browser. The data controller for the product deployment is the organisation operating that environment (e.g. tenant operator). This page gives layer-2 detail as recommended by the Spanish AEPD cookie guides: inventory, purposes, and retention.
2. First layer (summary)
- Strictly necessary: session / security cookies required to authenticate and operate the platform.
- Optional analytics: only loaded if you enable the category in the in-app preferences panel (currently no third-party marketing pixels are injected in the open-source host build).
- Similar technologies: the consent choice itself may be stored in
localStorageon your device to remember your decision.
3. Cookie table (representative)
| Name / key | Type | Purpose | Duration |
|---|---|---|---|
| nkz_token | HTTP — First party | Authenticated API session (JWT in HttpOnly cookie via API gateway). | Session / aligned with token expiry |
| Keycloak / OIDC | HTTP — Identity provider | Login flows for the hosted Keycloak realm (authentication). | Per IdP configuration |
| nkz_cookie_consent_v2 | localStorage | Stores your consent category choices for the web client. | Until cleared by you or version bump |
| Optional analytics | Script / cookie | Only if you opt in; measurement to improve the product. Not used for behavioural ads in the default OSS configuration. | Depends on tool if enabled |
Separate deployments (e.g. optional modules, OAuth2 proxies, or third-party SaaS) may add their own cookies: those services publish their own notices and should be listed in your tenant operator’s documentation.
4. Legal bases & consent
Strictly necessary cookies are used to provide the service you request (session, security). Optional analytics rely on your consent obtained through the banner / settings screen. You may withdraw consent at any time via Cookie settings in the application footer or Settings page; withdrawal does not affect login cookies until you sign out, because authentication remains strictly necessary for access to protected areas.
5. Minors
The service is intended for professional / organisational use. If you are under 14 and use a deployment that requires consent, your parent or guardian must provide consent where applicable law requires it.
6. Changes
When we materially change cookies or purposes, we bump the policy notice version in the client so you can review and update your choices.
7. Contact
Questions about this policy: use the contact channel published by your tenant operator, or for NKZ OS open-source matters see nkz@nkz-os.org.