Cookies
Version 1.0 · Last updated 25 July 2026
Whelpy uses only strictly-necessary cookies — the small ones a site needs to work and to keep you signed in securely. We do notuse advertising, marketing or third-party tracking cookies, and we don’t profile you or share your browsing with anyone.
The cookies we set
| Cookie | Purpose | Type |
|---|---|---|
| Session cookie (authjs.session-token) | Keeps you signed in as you move between pages. Without it you would have to log in on every page. | Strictly necessary |
| Security tokens (authjs.csrf-token, authjs.callback-url) | Protect the sign-in process against cross-site request forgery and return you to the right page after logging in. | Strictly necessary |
These are set by Whelpy itself (they are first-party) and, in production, they are secure, HTTP-only cookies. On the live HTTPS site your browser shows them with a security prefix on the cookie name: the sign-in and return-page cookies appear as __Secure-authjs.session-token and __Secure-authjs.callback-url, and the anti-forgery token uses the stricter __Host-authjs.csrf-token.
What we don’t use
We don’t set advertising, marketing or cross-site tracking cookies, and we don’t use third-party analytics that would drop a cookie. Your theme choice (light or dark) is remembered in your browser’s local storage on your own device — not in a cookie and not sent to us.
Do you need to consent?
Under the Privacy and Electronic Communications Regulations (PECR), consent is needed for cookies that are not strictly necessary. Because Whelpy uses only strictly-necessary cookies, no cookie-consent banner is required. If that ever changes — for example if we added optional analytics — we would ask for your consent first and update this page.
Managing cookies
You can delete or block cookies in your browser settings, but if you block Whelpy’s strictly-necessary cookies you won’t be able to stay signed in and the service won’t work properly. Signing out clears your session cookie.
← Back to Whelpy · Terms of Service · Privacy Policy · Data Processing Terms