skip to content

cookies policy

last updated

This site sets no cookies. Not one, first or third party. No analytics cookie, no session cookie, no advertising or consent-management cookie. Nothing on this domain writes to document.cookie, and nothing sends a Set-Cookie header back to your browser.

That is also why there is no consent banner. A banner exists to collect permission for storage that is not strictly necessary, and there is nothing here to ask about.

what is stored instead

One thing, and only if you use the theme toggle: your choice of the light or dark theme, written to your browser’s local storage.

It holds no identifier and cannot be used to recognise you, on this site or any other. If you never touch the toggle, nothing is written and the site follows your system’s light or dark preference.

removing it

Clearing site data for this domain in your browser removes it: in Chrome, Edge, and Firefox it is under the padlock or site-information icon in the address bar, then site settings or cookies and site data; Safari keeps it under Settings, Privacy, Manage Website Data. Private or incognito windows discard it when you close them. Nothing on the site breaks afterwards; the theme simply follows your system again.

third parties

None are embedded, so none can set a cookie here. There are no ads, no embedded videos, no social widgets, no hosted fonts, and no tag managers. Every asset comes from this domain, and a content security policy declared in each page blocks off-origin loads outright. GitHub data shown on the home page is fetched when the site is built, not when you open it.

Links out to GitHub, LinkedIn, or X will of course set cookies once you are on those sites, under their policies rather than this one.

if this changes

Should the site ever need a cookie, this page will name it, say what it does and how long it lasts, before it is set, and anything beyond the strictly necessary will ask you first. Questions go to contact@gaya.anonaddy.com.

The request logs GitHub keeps as the host are separate from anything stored in your browser and are described in the privacy policy.

privacy policy