Cookies · RetireSafe

What we use

RetireSafe uses a small number of mechanisms that either are technically cookies or behave like them (localStorage, sessionStorage). Most are strictly necessary, meaning the site cannot do its job without them, and those are listed first. Google Analytics is the one exception. It sets cookies, it is not necessary, and it runs only if you accept it.

Strictly necessary

Supabase session token (httpOnly cookie). Set when you sign in; identifies your session. Cleared on sign-out or when it expires.
retirement:input-flow (localStorage). The inputs you've entered into the calculator. Lives in your browser; not transmitted unless you save the scenario.
retirement:ui (localStorage). Your UI preferences (theme, etc.). Lives in your browser.
retirement:cookie-consent (localStorage). Records whether you accepted or rejected analytics cookies, and when, so we can honour that answer and stop asking. You can change it at any time from Cookie settings at the bottom of any page.

Analytics that needs no permission

We use Umami to count page views and which features get used. Umami does not use cookies and stores nothing on your device, so there is nothing here for you to accept or refuse. What it does record is set out in our privacy policy. See also their privacy policy.

Analytics that asks first

If you accept, we also use Google Analytics to measure which pages and features people use, and which of our adverts brought someone here. That second part is how we tell whether money spent on advertising is doing anything. It sets two cookies:

_ga (2 years). Tells one browser apart from another, so that a repeat visit is not counted as a new person.
_ga_Y5ZVFG0SK6 (2 years). Tracks a single visit to this site specifically.

Neither cookie is set unless you accept. Until you do, Google receives only an anonymous note that a page was viewed: nothing is stored on your device and no identifier is created, so Google cannot recognise you here or on any other site. As with any request to any server, it does see the internet address you are connecting from. If you reject, it stays that way permanently. Google's own account of what it collects is in its privacy policy.

Error reporting

Sentry may store an anonymous error-ID in your session storage so we can tie a single failure to a single user-reported bug. When an error occurs, Sentry may also capture a masked replay of that session, meaning a reconstruction of on-screen interactions with all text and form values blanked out. Error-free sessions are never recorded. If a simulation run fails, the inputs of that run are included in the crash report so we can reproduce it; see the privacy policy for detail.

How to change your mind

Cookie settings, at the bottom of any page, reopens the question and takes effect immediately. Rejecting stops Google Analytics and deletes nothing else about how the site works for you.

Browser storage can be cleared at any time via your browser's site settings. If you do so, the input flow will start fresh and we will ask about analytics again. Signing out removes the Supabase session cookie immediately.