Cookie Policy
Last updated
Most cookie policies describe cookies the site does not have. This one lists what NKable actually stores in your browser, which is very little, and says plainly that analytics is currently switched off.
The short version
NKable sets no advertising cookies, no tracking cookies, and no third-party cookies. There is nothing here to opt out of, which is why you have not been shown a cookie banner.
What the site does use is a small amount of your browser's own storage to remember your preferences, and — only if you sign in — a session token.
1. What is actually stored
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
| theme | Local storage | Remembers light or dark mode so the page does not flash the wrong theme on load | Until you clear browser storage |
| i18nextLng | Local storage | Remembers a language you picked from the switcher | Until you clear browser storage |
| access_token | Local storage and a cookie | Keeps you signed in. Only set if you create an account and sign in | Until you sign out or it expires |
| Per-tool saved work | Local storage | A few tools keep your in-progress work so a reload does not lose it | Until you clear it or clear browser storage |
Everything in that table is strictly necessary or a preference you chose, stays on your device, and is never transmitted to us for tracking. Under UK and EU rules these do not require consent — but you can remove them at any time, as described in section 4.
2. Analytics — currently off
The site includes Google Analytics 4 code, but it is inert: the script only loads when a measurement ID is configured in the environment, and none is. You can confirm this by viewing the page source and searching for googletagmanager — there is no match.
So today: no analytics script, no analytics cookie, nothing sent to Google.
If analytics is switched on in future, we will update this page and the privacy policy before it goes live, and visitors in the UK, EU and EEA will be asked to consent before any analytics cookie is set — because consent has to come first, not after.
3. Cloudflare
Cloudflare sits in front of the site as a CDN and to absorb attacks. It may set a cookie such as __cf_bm to distinguish automated traffic from people. This is a security function rather than tracking, it does not follow you across other websites, and it is not used for advertising. Cloudflare sees your IP address as an unavoidable consequence of routing your request — the privacy policy lists them as a processor.
4. Clearing or blocking storage
Everything in section 1 lives in your browser and is yours to remove. In any modern browser, open developer tools, go to Application or Storage, and clear local storage and cookies for nkable.com. Your browser's privacy settings can also block storage for this site entirely.
If you clear it, nothing breaks — the site simply forgets your theme and language choice, and signs you out if you had an account.
5. Changes
The date at the top of this page changes whenever this policy does. Any change that introduces a new cookie will be reflected here before the cookie is set, not after. Questions: [email protected].