Last updated: September 17, 2026
01
What we use
Docet sets only strictly necessary cookies. We run no advertising or analytics cookies, so we do not show a cookie-consent banner.
02
Cookies we set
__Secure-neon-auth.session_token- Authenticated session — Session / provider-managed
__Secure-neon-auth.local.session_data- Signed session cache — Session / provider-managed
__Secure-neon-auth.session_challenge- OAuth sign-in verification — Transient
__Secure-neon-auth.session_challange- Legacy OAuth verification retained by the auth SDK — Transient
docet-membership- Remembers which organization you last used — 365 days
03
Error monitoring
Docet uses Sentry for error and performance monitoring at a 10% trace sample rate. Session Replay is not used. Cookies, request and response headers, request bodies, URL query parameters, and stack-frame variables are excluded from what is sent to Sentry.
04
Third-party pages
Stripe Checkout, the Stripe Customer Portal, and Stripe hosted invoices are separate Stripe-operated pages. Those pages may set their own cookies under Stripe's policy. Docet does not embed Stripe.js.
05
Fonts and storage
Fonts are self-hosted at build time through next/font/google; your browser does not request fonts from Google. Docet uses nolocalStorage, sessionStorage, orindexedDB.
06
Managing cookies
You can manage or block cookies through your browser controls. Blocking the authentication cookies prevents you from signing in to Docet.
07
Contact
Questions about cookies can be sent to support@docet.org. Read our Privacy policy for more information.