Cookies and browser storage
No visitor analytics or advertising trackers. A security session cookie protects forms and assessment PDFs.
Security cookie
Pages with forms or assessment PDF requests use a first-party session cookie whose name starts with .AspNetCore.Antiforgery. It works with a request token to protect against forged submissions and is not used for advertising or visitor analytics. It is HttpOnly and SameSite=Strict; production HTTPS also uses Secure. The cookie has no persistent expiry and is normally removed when the browser session ends, although browser session restoration may retain it. Blocking it prevents protected submissions and assessment PDF export.
Appearance and tool answers
The initial colour theme follows your device preference. Changing it affects only the current page and resets on navigation or reload. Application scripts do not read or write localStorage or sessionStorage. Tool answers remain in page memory unless you request a PDF or email delivery. Preferences saved by an earlier site version are no longer used; you can clear them in your browser's site-data settings. Your browser may cache public assets such as styles and fonts in the usual way.
No optional tracking
The website includes no visitor analytics or advertising trackers and has no optional-storage consent popup. There is no analytics script, collector endpoint or analytics setting to enable.
Form protection
When online forms are enabled, Cloudflare Turnstile is loaded to protect submissions. The public site is also designed to use Cloudflare for HTTPS and delivery. These services may process network and security information; their actual security-cookie behavior and processor terms must be checked for the final deployment. They are separate from the website's own antiforgery cookie.
Assess your starting point yourself, or work through it together.
Take the free assessment →