Cookies
There is no banner, because there are no cookies
You have just read a cookie page without first dismissing a cookie dialog about the cookie page. We would like a moment to enjoy that.
Last reviewed: 20 September 2026. This page covers ikonekt.com. The service at app.ikonekt.com is a signed-in application and necessarily works differently; its own terms cover it.
The whole policy, in one line
No cookies. Neither this website nor the services it uses set any — not necessary ones, not functional ones, not analytics, not advertising.
That is not a stance we arrived at after a workshop. It is a consequence of the site having nothing that needs one: no basket, no scripts from other companies to smuggle one in, and analytics that needs none — visits are counted by Observer, castomo's own cookie-less analytics, which stores nothing on your device. The one sign-in it offers, in the demo on the home page, keeps its session in local storage rather than in a cookie.
There is one form — the access request — and it does not need a cookie either. It posts to itself and draws the answer straight into the page it came from, which is exactly the round trip a session cookie is normally introduced to survive. The cost of doing it that way is that refreshing the page after sending offers to send it again, and your browser will ask you first; we would rather have that small friction than a cookie banner.
What we use instead
The accessibility panel in the header lets you choose a colour theme, a text size, wider spacing and reduced motion. Those choices are kept in your browser's local storage, which is a different mechanism from a cookie in the way that matters: it is never sent to the server on its own. A cookie travels with every request. Local storage sits in your browser and stays there, unless a script on the page reads a value and sends it — which on this site only the demo on the home page does, with the keys marked sent below, and the chat button once you open it, as described under the table.
| Key | What it holds | Why |
|---|---|---|
ikk:theme | light, dark or contrast | So the page does not go back to the wrong colours on your next visit. |
ikk:size | large or xlarge | So you do not have to enlarge the text every time. |
ikk:spacing | wide | Wider letter, word and line spacing, for readers who need it. |
ikk:motion | reduce | Turns off animation and smooth scrolling. |
ikk:try-drafts | The areas you counted in the demo, at most 20: each one's id and title and, until you save it to an account, the key that opens it. Sent to castomapi-try when the demo opens or saves that draft. | So you can come back to an area, and so nobody without the key can open it. |
ikk:try-pending | Which area you were saving or sharing, while you are away signing in. | So it happens when you come back. Removed once you are back and signed in. |
ikk:try-pkce | A one-time random value for a sign-in you started. Sent once, to castomo accounts. | Proves the sign-in coming back belongs to this browser. Removed on your return, and refused after 30 minutes. |
ikk:try-session | Your castomo sign-in, once you sign in through the demo. Sent to castomapi-try and castomo accounts when the demo acts for your account. | So saving and sharing do not ask you to sign in again. |
Each of the four accessibility keys is written only when you choose that setting, and only that setting. There is no identifier, no visitor number and nothing that could distinguish you from anybody else who also prefers dark mode — which, for the record, is most people.
The demo's keys are written only when you use the demo. They hold the areas you counted and, once you sign in, your sign-in to your castomo account — which does tell castomo who you are, because that is what signing in is for.
Only if you open the chat: castomo.chat.<widget id>.returning (the value 1) and, while the chat is open, castomo.chat.<widget id>.open, on this site; and castomo.chat.<widget id>.token and castomo.chat.<widget id>.visit on chat.castomapi.com. Nothing is written before you open it. Clearing your browser's site data removes them.
How to remove them
Clear site data for ikonekt.com in your browser, or use a private window, and they are gone. The site then behaves exactly as it does for a first-time visitor: it follows your operating system's own light or dark setting and its reduced-motion preference, without being told anything.
A small confession: we would have loved to write a page explaining our sophisticated consent management platform, its 214 vendor partners, and the legitimate-interest toggle buried three screens down that is switched on by default. But we would have had to build it first, and it turns out you can simply not.
Does this need consent?
Storage that is strictly necessary to provide a service the user has explicitly requested does not require consent. Remembering that you asked for a larger text size, on your own device, with nothing transmitted anywhere, sits comfortably inside that. We take the view that asking for permission to remember a preference you just expressed would be theatre rather than protection. The demo's keys are the same case: each exists only because you asked the demo to count, keep or share an area, or to sign you in.
If you disagree, everything on the site works with local storage unavailable — the panel still changes the page, it simply forgets between visits. The demo still counts, but without local storage it cannot carry an area through a sign-in.