Cookie policy

It holds a signed token carrying your user id and your organisation id. Nothing else. Scripts running in your browser cannot read it, and outside local development it only travels over an encrypted connection.

The cookie that keeps you signed in needs no permission: it delivers the thing you asked for. Analytics cookies do, where the law says so. If you are visiting from the European Economic Area, the United Kingdom or Switzerland, nothing described in the next section loads until you press Accept on the banner, and pressing No thanks keeps it off every page after that. Everywhere else it loads by default, and this page is the notice.

We use Google Tag Manager, which loads Google Analytics and Microsoft Clarity so we can see which pages people actually read, which buttons they press, and where the site loses them. Google Analytics sets _ga and _ga_ followed by an id, kept for up to two years. Clarity sets _clck for a year and _clsk for a day, and Microsoft may set MUID on its own domains. What Google and Microsoft keep, and for how long, is set out in their own privacy statements.

Where the banner applies and you say no, no Google or Microsoft script is placed on the page. Not loaded and blocked: never requested. Everything on this site works either way, and nothing about the product changes based on your answer.

Your answer is remembered in your own browser, under the name dc_consent. Clearing site data forgets it and you will be asked again.

Every browser can block cookies, and yours will explain how in its settings. Blocking this one means the sign-in page will accept your password and then send you straight back to it, because nothing remembers that you got in. The public pages work fine without it.

Signing out deletes it immediately. So does clearing site data for DockCount.

The privacy policy covers everything else we hold. For anything this page does not answer, write to privacy@dockcount.com.