What we use
Kinaz currently uses one authentication cookie, one consent cookie to remember your choice, and optional local storage for the selected theme when you allow preferences.
Cookies and storage
How Kinaz uses cookies and local storage
This page lists the cookies and storage mechanisms we found in the current application.
Change or withdraw your choice
You can open Cookie Settings at any time to accept, reject, or change your optional preferences later.
Analytics and marketing
We did not find analytics services, advertising tags, or marketing tracking scripts loading from the current web source code.
Current inventory
Here are the cookies and storage keys the application currently uses.
token
First-party cookie (HttpOnly)
- Purpose
- Keeps a signed-in session active and secures access to protected routes.
- Provider
- KINAZ API
- Duration
- 7 days
- Essential
- Yes
- Where / when it is created
- Set after successful sign-in or sign-up verification.
kinaz_cookie_consent
First-party cookie
- Purpose
- Stores your cookie choice so the banner does not reappear on every visit.
- Provider
- KINAZ Web
- Duration
- 180 days
- Essential
- Yes
- Where / when it is created
- Set when you save a consent choice from the banner or preferences dialog.
kinaz-theme
First-party local storage
- Purpose
- Remembers the theme you selected when you allow site preferences.
- Provider
- KINAZ Web
- Duration
- Until cleared
- Essential
- No
- Where / when it is created
- Written by the theme toggle only after the preferences category is allowed.
Technical notes
The token cookie is HttpOnly, so client-side JavaScript cannot delete it directly. Cookie Settings never removes it and never interferes with sign-in.
If you reject or later withdraw preferences, Kinaz removes the kinaz-theme local storage key and stops writing it again until you allow preferences.