Cookie Policy
Short version: DocSpell only uses cookies it needs to work. No advertising cookies, no cross-site tracking, and no analytics cookies. Our page-view counts are done on the server without cookies (the Privacy Policy explains how).
What we set
| Name | Set by | What it's for | How long |
|---|---|---|---|
__session, __client_uat | Clerk (docspell.dev) | Keeps you signed in and checks whether you are. | Session, or until you sign out |
__client, __clerk_* | Clerk (clerk.docspell.dev) | Sign-in state and security for your account. | Up to 1 year |
__cf_bm | Cloudflare | Tells real visitors apart from bots. Only set if our bot protection kicks in. | 30 minutes |
docspell-theme | Your browser (local storage) | Remembers whether you picked light or dark mode. | Until you clear it |
docspell-cookie-notice | Your browser (local storage) | Remembers that you've seen the cookie notice. | Until you clear it |
Why there's no “accept all” button
Everything above is strictly necessary to sign in, keep your account secure, or remember a choice you made. The law doesn't require consent for those, and there's nothing optional to switch off, so we just tell you about them instead of asking you to click through a banner.
Payments
When you upgrade, you're sent to Stripe's checkout, which sets its own cookies on Stripe's domain to process the payment and prevent fraud. Those are covered by Stripe's privacy policy.
Docs published with DocSpell
Readers of docs published on DocSpell get the same treatment: no tracking cookies. If a doc space owner adds their own custom CSS or links, those can't add scripts, so they can't set cookies either.
Turning cookies off
You can block or delete cookies in your browser settings. Reading published docs works without them; signing in doesn't.
Questions
Email hello@docspell.dev.