Cookies
Cookie policy
This policy explains every cookie this site can set, what each one is for, and how to change or withdraw your consent. We have kept it short because there is genuinely little to declare.
Effective August 2026
GDPR & NDPR aligned
What cookies are
A cookie is a small text file a site stores in your browser so it can recognise the browser on a later visit. Related technologies — local storage and session storage — do the same job in a different place, and we treat them the same way in this policy. Where we mention a cookie below, the same rules apply to any equivalent storage.
Our position
We set no advertising cookies, no tracking pixels, and no third-party analytics on this website. The only cookie we currently store is the one that records your answer to the consent banner, and the only local storage we use remembers whether you chose the light or dark theme. If that ever changes we will update this page and ask for consent again before anything new is set.
Strictly necessary
These are required for the site to function and cannot be switched off. They record your consent choice so the banner does not reappear on every page, and they protect forms against cross-site request forgery. Under the ePrivacy rules this category does not require consent, because without it the service you asked for cannot be delivered.
Preferences
These remember choices you have made so the site behaves consistently. Today this covers one thing: whether you selected the light theme, the dark theme, or asked the site to follow your system setting. It is stored in your browser's local storage, it never leaves your device, and we cannot read it from our servers.
Analytics
Analytics would let us count visits, see which documentation pages are actually read, and find pages that error. We currently run none. If we introduce analytics we will choose a provider that does not build cross-site profiles, and it will load only after you allow this category — never before.
Marketing
Marketing cookies would let an advertising platform tell whether a click on an advert led to an enquiry. We currently set none. This category exists in the preferences dialog so that if we ever run advertising, the control is already there and switched off by default.
What is actually stored
karmat_consent — a first-party cookie holding your consent choice, the categories you allowed, and the date you chose. It expires after six months, after which we ask again. karmat-theme — local storage holding the value light, dark or system. It does not expire and is removed when you clear site data. Neither contains a name, an email address, or an identifier that points back to you.
How long they last
Your consent record expires six months after you make it. We deliberately do not set a longer period: consent that was given years ago and never revisited is not meaningful consent. When it expires the banner reappears and you can make a fresh choice. Clearing your browser's site data removes everything described here immediately.
Changing or withdrawing consent
Select Cookie settings in the footer of any page to reopen the preferences dialog and change your answer, including rejecting everything you previously allowed. Withdrawing is exactly as easy as consenting, which is a requirement rather than a courtesy. You can also block or delete cookies in your browser settings, though blocking the strictly necessary cookie means the consent banner will appear on every page, because we will have no record of your choice.
Changes to this policy
If we add a cookie in a category you have not allowed, your existing consent does not carry over — we will ask again before that cookie is set. Material changes reset the stored consent version, which means the banner reappears for everyone. Questions about this policy can go to [email protected].