Compare Your Build
Cookies and browser storage
Optional journey analytics helps us understand which pages and calculator steps work well, and where visitors stop.
Your choice
Analytics is off until you choose Allow analytics. Declining does not stop you using the calculator or requesting help. Use Analytics settings at the bottom of any page to change your choice. There are no advertising pixels or screen recordings.
What optional analytics records
We record page categories, button actions, calculator steps, validation events, and successful saves, uploads and requests. A random browser-tab session reference connects these actions, with timestamps and a phone/tablet/desktop layout category. We do not attach your account, name, email, postcode, address, typed answers, filenames, IP address, query strings or document contents to these events. This random reference is pseudonymous, not a guarantee of anonymity.
The authorised team can view visit timelines and the last recorded action. This is not permission to contact a visitor. Blockers, connection failures and declined consent create gaps; we cannot determine why someone left.
Storage and expiry
The cyb_analytics preference cookie remembers accepted or declined for six months. After acceptance only, cyb_journey in session storage remembers a random visit reference and activity time. A new visit starts after 30 minutes without recorded activity. Closing the tab ends its session storage. Declining stops new events and clears this tab’s reference; previously collected events are not automatically withdrawn.
Journey events are stored in our site database for a 90-day rolling window. Older events are removed when the analytics endpoint is next used, including when the team opens its report. The report shows the latest 30 days. No external analytics company receives this activity.
Essential access and project storage
The hosting provider manages sign-in and access separately. Unsent assessment answers stay in memory while you navigate this tab and clear on refresh or closing. Choosing to save stores your project privately on the server. Aggregate operational counts of saved projects and submitted requests continue independently of optional browsing analytics.