Skip to content
Fire Safety ServicesDigital LogbookYour workspace →

Clear information, kept together

Cookies and browser storage

The storage used for secure accounts, and what stays separate in the free demo.

Version 2026-10-18.1 · Updated 18 October 2026

Explore the free demo →

On this page

  1. 1. Essential account storage
  2. 2. Demo and optional tracking
  3. 3. Stripe and other external services
  4. 4. Managing cookies

1. Essential account storage

The app uses cookies to keep sign-in secure and finish verification or password-reset journeys. They are not advertising identifiers. Blocking essential cookies may stop sign-in, invitations or verification from working.

Neon Auth session cookies
Cookies in the __Secure-neon-auth family identify and protect your session, including session-token and short-lived signed session-data/challenge cookies where used. The local session-data cache is configured for 60 seconds; that is not the lifetime of your sign-in. Authentication-session expiry is controlled by the authentication service and the cookie expiry shown in your browser.
fss-pending-email
Remembers your registration email during verification. Restricted to the authentication path, unavailable to client-side scripts, and expires after 20 minutes or is cleared when verification succeeds.
fss-auth-return
Remembers a validated local return destination during sign-up or invitation acceptance. Also restricted to the authentication path, unavailable to client-side scripts, and expires after 20 minutes or is cleared on completed verification.

Hosting and security services may also use necessary request-routing or security mechanisms. This list describes the app’s configured account cookies, not cookies on providers’ own websites.

2. Demo and optional tracking

The interactive demo keeps fictional changes in the current page’s browser memory. Reloading or resetting the demo discards them. It does not save them as real premises records or consume the free entry.

We have not added advertising pixels, cross-site marketing trackers or a client-side analytics package to this app. We do not load optional tracking merely because you view this notice. If optional tracking is introduced, we will explain it and obtain permission where required before it runs.

3. Stripe and other external services

Following a link to Stripe Checkout or its billing portal takes you to Stripe, which uses its own cookies for payment functionality, fraud prevention and other purposes explained in Stripe’s cookie policy. The app does not embed a payment-card form or automatically load Stripe’s browser payment library on every page.

Other external links have their own privacy and cookie information. Read our privacy notice for the app’s providers and processing purposes.

4. Managing cookies

You can inspect, clear or block cookies using your browser settings and sign out using the app. Clearing a browser cookie does not delete your account or logbook. For deletion and privacy questions, use the contact details in our privacy notice.

Because the app currently uses account functionality rather than optional tracking, it does not display an “accept all” marketing-cookie banner.

TermsPrivacyCookies
Fire Safety Services Digital Logbook