Cookie Policy

Essential Browser Storage (Always Active, No Cookies)

We store nothing in a cookie of our own. What the site needs in order to work stays in your browser's own storage and is not transmitted automatically with each request the way a cookie is. It cannot be switched off, because without it you could not stay signed in or keep your choices.

• Sign-in state (Firebase Authentication): your session token, kept in IndexedDB and localStorage — not in a cookie. It is cleared when you sign out.
• Your cookie choice: stored in localStorage under the key al_cookie_consent_v1 (plus al_data_consent_v1 when the choice is made while creating an account). It has no expiry date.
• Interface preferences: your language and your light/dark theme choice, in localStorage.
• What you type into our tools: some simulators and forms keep your entries in localStorage so you can come back to a half-finished form. That data stays in your browser until you clear your browser storage for this site.
• Cross-site request protection: handled by a one-time value issued by our server for the request, not by a cookie.
• The only cookie our own code writes: a deletion. When you withdraw analytics consent, we expire Microsoft Clarity's _clck and _clsk cookies.

Analytics and Measurement (Optional, except where stated)

With your consent, these help us understand how the site is used — which pages are visited, where people get stuck, and which errors occur. This measurement is pseudonymous, not anonymous: when you are signed in, your AdminLanding account identifier is sent to Google Analytics as the user ID, so the data can be linked back to your account.

• Google Analytics 4 (G-KXNSNV0T70): Usage statistics. Cookies _ga and _ga_KXNSNV0T70, both set on our own domain (.adminlanding.com) and kept for up to about 13 months. The Google tags are not loaded at all until you accept.
• Microsoft Clarity (project yjsp6pi7pj): Heat maps and session recordings of the public website, to see where pages are confusing. This project loads only with this consent, and never on /share/ links. Cookies: _clck (12 months) and _clsk (short-lived, groups pages into one session). Signed-in app pages and the sign-in, sign-up, e-mail-verification and account-deletion screens are marked so their content is not uploaded — masking hides what is on the page, not the visit itself: page addresses, clicks and scrolling are still sent.
• Cloudflare Web Analytics: a page-load beacon (static.cloudflareinsights.com, posting to /cdn-cgi/rum) that measures loading times and page views. It sets no cookie, but it is not consent-gated: it runs on every visit, including before you have made any choice. We declare it here for that reason.
• Calculator step counts (AdminLanding): on the home-employment end-of-contract calculator, our own server counts how many visits reach each step (page seen, calculation shown, offer seen, a button pressed, payment page opened), per day and per advertising-campaign name. It sets no cookie and stores only those daily totals — no identifier — and it reads nothing from your browser beyond the campaign name already kept for checkout. It is not consent-gated either, which is why we declare it here.
• Performance Monitoring (Sentry): Performance tracing and text-masked session replay load ONLY with this consent. Without it we keep bare error capture — the error message and its stack trace — while navigation, click, console and network history and session tracking are switched off; legitimate interest in keeping the site working. Sentry sets no cookie.

Marketing Cookies (Optional)

These cookies are used to measure the effectiveness of our own advertising campaigns. Today this is limited to the Meta Pixel (Facebook / Instagram — cookies such as _fbp), which is set only if you accept marketing cookies.

• Conversion measurement (Meta Pixel): tells us which of our ads led to a sign-up. The pixel is loaded through our Google Tag Manager container and only once marketing consent is stored; refusing or withdrawing marketing consent keeps it from loading.

AI Assistance Choice (Optional — browser extension only)

The consent panel also carries an "AI assistance" switch. It sets no cookie and changes nothing on this website: it is passed to the AdminLanding browser extension when that extension is installed, and it is what turns the extension's page assistance on or off. While it is on, the assistance runs automatically on the supported government websites — you do not have to ask for it — and the visible text of the page you are on is sent to our AI provider so it can be explained. The same switch is available in the extension's own popup. The retention option next to it (zero, limited or full) is likewise passed to the extension and controls how long it keeps its local history.

On AdminLanding:

The consent banner appears on your first visit and stays until you make a choice. Your choice is stored in the browser you made it in, so it applies to that browser and that device only — not to your account. You can reopen the preferences panel at any time from the "Manage Cookie Preferences" link at the bottom of our home and pricing pages.

If you have an account, the Privacy card in your account settings saves the same choice — but it only offers analytics, AI assistance and data retention: every save there records marketing cookies as refused.

In Your Browser:

Most browsers let you control cookies and site data through their settings. Clearing the site data for adminlanding.com also removes the browser storage described above: you will be signed out, your consent choice is gone and the banner appears again.

• Chrome: Settings → Privacy and security → Cookies and other site data
• Firefox: Settings → Privacy & Security → Cookies and Site Data
• Safari: Preferences → Privacy → Manage Website Data
• Edge: Settings → Cookies and site permissions