Cookie Policy
The short version: this website sets no cookies at all. Here is what it does store, and how to get rid of it.
- kenzed.in sets no cookies — not necessary ones, not analytics, not advertising.
- Two preferences live in local storage on your own device and never leave it.
- There is no consent banner because there is nothing to consent to.
This summary is written for speed of reading and is not itself the agreement. Where it and the numbered sections below differ, the sections govern.
1. We do not use cookies
This site writes no cookies of any kind. There is no analytics cookie, no advertising or retargeting cookie, no social-embed cookie, and no session cookie — a static site has no session to keep.
That is also why you will not see a consent banner here. A banner exists to collect consent for tracking; with nothing to track, one would be theatre.
2. What we do store on your device
Two values are written to your browser's local storage. Local storage is not a cookie: it is never attached to a network request, so it cannot travel to us or to anyone else. Both exist purely so the site behaves the way you last left it.
- Stored value
- Purpose and lifetime
- Theme choice
- Remembers light or dark so the page does not flash the wrong theme on your next visit. Persists until you clear site data.
- Assistant greeting flag
- Records that the chat assistant has already introduced itself, so it does not repeat the greeting on every page. Persists until you clear site data.
3. Third-party content
We embed no third-party scripts, fonts, maps, video players or social widgets. Typefaces are compiled into the site at build time and served from our own origin, so no request leaves for a font CDN.
Links that take you off the site — to WhatsApp, or to a published project — land you on someone else's property, where their own cookie policy applies.
4. Clearing what is stored
Clear site data for kenzed.in in your browser's settings, or use a private window. The only effect is that the site forgets your theme choice and the assistant introduces itself once more. Nothing else changes and nothing breaks.
If we ever add anything that does need a cookie, this page and the privacy policy change first, and a consent mechanism arrives with it.