Cookie Policy
A short document, because the honest answer is short: we set what the product needs to work and nothing that follows you.
The Short Version
A summary of what matters most, in ordinary language. It is a guide to the document below, not a replacement for it — where the two differ, the full text governs.
No advertising or tracking cookies
The public site sets none. There is no advertising pixel, no cross-site tracker and no third-party analytics tag.
Only what the product needs
Signed in, you carry a session cookie. Without one you would be signed out on every page. Your theme choice is remembered in local storage on your own device.
No consent banner, because none is needed
Strictly necessary cookies do not require consent under the ePrivacy rules. We would rather not set the others than ask you to dismiss a banner.
You can clear them
Clearing site data in your browser removes everything. Signing out ends the session immediately.
Pending legal review. This document describes how the product actually works, but it has not yet been reviewed by a qualified lawyer and the bracketed fields below still need completing. Do not rely on it as final terms.
What We Set, And Why
A cookie is a small file a site stores in your browser. Local storage is a similar mechanism that keeps data on your device without sending it with each request. Docket uses both, narrowly.
| What | Purpose | Lifetime |
|---|---|---|
| Authentication session | Keeps you signed in as you move between screens. Set only after you sign in, and removed when you sign out. | Until sign-out or expiry |
| Theme preference | Remembers light or dark so the app does not flash the wrong one on every load. Local storage, never sent to us. | Until you clear site data |
| Security tokens | Short-lived values that protect forms and the sign-in flow against cross-site request forgery. | Session |
All of these are strictly necessary to provide a service you have asked for, which is the category that does not require prior consent.
What We Do Not Set
Stated explicitly, because the absence is the point:
- No advertising or retargeting pixels.
- No third-party analytics tag on the public site.
- No social media tracking widgets. Links to our profiles are ordinary links.
- No cross-site identifiers, fingerprinting or data brokers.
If that changes, this page changes first and an appropriate consent mechanism ships at the same time. A tag arriving quietly ahead of its policy is exactly the practice this section exists to rule out.
Cookies Set By Others
Two flows hand you to a third party, and while you are with them their own policies apply rather than ours:
- Google sign-in and Google account connection. Google sets cookies on its own domains during consent. Docket receives tokens, never your Google password.
- Your own WordPress site. If you follow a link to a published article, your site's cookies apply.
Docket cannot read cookies set on another party's domain, and no third party can read the ones set here.
Managing Them
Every browser lets you view, block and delete cookies and site data, usually under privacy or site settings. Blocking cookies for this site will sign you out and keep you signed out, because the session cookie is how being signed in works.
Signing out from the account menu ends the session immediately without touching anything else on your device.
Questions
Write to support@docket.ltd. This policy is operated by Docket Ltd. and should be read alongside the privacy policy.
Questions about this document? support@docket.ltd