The one cookie
| Name | What it does | How long |
|---|---|---|
| rf_session | Remembers that you signed in, so every page you open knows who you are and which organisation you belong to. | 30 days |
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.
Why there is no consent banner
Consent is required for cookies that are not needed to deliver the thing you asked for. Analytics, advertising and anything that follows you between sites all need it. A cookie that exists solely to keep you signed in does not, under the ePrivacy rules and their equivalents elsewhere.
We set nothing beyond that one cookie, so there is nothing to ask you about. Clicking accept on a banner that only ever had one honest answer wastes a second of everybody's day.
What we do not set
No analytics. No advertising or retargeting tags. No social media buttons that phone home. No session recording. No third-party script of any kind runs on these pages, which you are welcome to check with your browser's network inspector.
If that ever changes, this page changes first and a consent banner appears with it. The date at the top tells you which version you are reading.
Turning it off
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.
Asking about this
The privacy policy covers everything else we hold. For anything this page does not answer, write to privacy@dockcount.com.