Cookie policy

What we set

One cookie of our own, and nothing else until you agree to it.

That is the only cookie present before you answer. Everything else is set by a third party, only after you agree, and is listed in the next section.

What you are agreeing to

Two categories, one of which you control.

• Strictly necessary. The consent cookie above, plus the browser storage described below that keeps you signed in. These cannot be switched off, because the site cannot do what you asked without them, and the law does not require consent for them.
• Analytics. Counts visits and records how pages are used, so we can see which ones earn their place. Google Analytics and Microsoft Clarity. Off unless you turn it on, and nothing analytics-related is fetched before you do.

Advertising. Measures whether an advert brought you here, and lets us reach people like you. The Meta pixel. Off unless you turn it on.

What we store outside cookies

Your dashboard at dashboard.daidocs.com sets one cookie of its own to keep you signed in. It is strictly necessary: without it you could not stay signed in between pages, so no consent is required for it under PECR, and it is never used to track you or shared with anyone.

All four are strictly necessary: without them you would be signed out on every page load. None is used to track you, and none is shared with anybody.

Your choice, and changing it

The banner appears before anything optional has run, and blocks each category until you answer for it. Nothing non-essential is pre-selected: an unanswered category counts as a refusal, not as agreement.

Closing the banner without answering is not consent. Nothing optional runs until you actively say yes.

To change your mind at any time, use cookie preferences, which also sits in the footer of every page. Withdrawing is as easy as giving, and takes effect on the next page you load.

Third parties, and when they load

Every asset the site needs to work is served from our own domain: fonts, images, stylesheets and scripts. There are no embedded videos, no social widgets and no external iframes.

Beyond that, four companies are involved. One asks the question; the other three receive data only if you agree. All of them arrive through Google Tag Manager.

All of them are operated from the United States, so accepting either category means data about your visit leaving the UK. The privacy notice covers the safeguards that applies under.

Links to GitHub and other sites are ordinary links. Once you follow one you are on their site and their policy applies.

If this changes

Consent is managed by CookieYes, delivered through the same tag manager as everything else it gates. It records your answer, stores it in the cookie above, and blocks the categories you refused before they load. It is a third party, so it sees that a visit happened; the privacy notice lists it with the rest.

The third party tags are managed through a Google Tag Manager container, which means a tag can be added without changing this site. That is convenient and it is also the risk, so the rule we hold ourselves to is this: anything added to that container appears as a category in the banner and a row in the table above before it is allowed to fire, not after. Tags are gated on your recorded choice rather than on the container, so one added without that being done does not quietly start collecting.

Controlling it yourself

You do not need our permission. Every browser lets you clear site data and block storage per site, usually under Settings, Privacy. Clearing ours will sign you out and forget your preferences, and nothing else will break. Private browsing achieves the same thing automatically when the window closes.

Contact

Questions: privacy@kerneta.com.

Related: Privacy notice · Terms of service · Software licenceCookie preferences