Liveability

Cookie Policy

Last updated: October 31, 2026

Liveability sets one cookie, and only after you sign in. It keeps you logged in. We use no analytics, advertising, or tracking cookies. The only things kept in your browser besides it are the household you enter for the Monthly Budget and whether you dismissed the US waitlist banner, both in this tab's session storage. This policy sits alongside our Privacy Policy.

What we store

sb-<project>-auth-token

Type
Cookie, first-party (set on our own domain)
Set by
Supabase, our authentication provider, on our behalf
Purpose
Keeps you signed in between pages, and lets our server verify it is really you before returning your saved areas
When
Only once you sign in — browsing the public pages sets nothing
Lifetime
Lasts for your sign-in session and is refreshed while you stay active; cleared when you sign out
Consent
Strictly necessary, so no consent is required — the signed-in experience cannot work without it

If the value is large your browser may show it split across numbered parts (…auth-token.0, …auth-token.1). That is one cookie, chunked.

Local storage and session storage

Local storage is not used. Session storage holds at most two entries. liveability:household: the income, marital status and household size you enter for the Monthly Budget, so it survives switching tabs and reloading. liveability:us-live-dismissed: set only if you close the “Now live in the US” note (shown to visitors in the US), so it stays hidden; it holds no personal data. Your browser deletes both when you close the tab, neither is sent to our database, and each is strictly necessary for something you chose to do, so no consent is required. Everything else you do in a session — your metric weightings, comparison list, and AI Match results — is held in the page's memory only and is gone when you reload or close the tab.

Third-party content

Four third-party services load in your browser. We checked all four: none sets any cookie or writes to your browser's storage.

  • Google Maps JavaScript API — loaded only on the signed-in dashboard, and only to power address autocomplete in the search box. It is served from Google's cookieless API domains (maps.googleapis.com, maps.gstatic.com) and sets no cookies. See Google's cookie policy.
  • swisstopo map tiles — the map images on result pages, requested from wmts.geo.admin.ch, the Swiss Federal Office of Topography's public map service. Tile requests set no cookies. See the geo.admin.ch terms of use.
  • USGS map tiles — the map images for US addresses, requested from basemap.nationalmap.gov, the US Geological Survey's public National Map service. Tile requests set no cookies.
  • Cantonal hazard maps — when you open the Natural Hazards card, the canton's official hazard map is shown over the map, as images requested from geodienste.ch, the cantons' shared geodata platform. Those requests set no cookies.
  • PostHog (EU cloud) — product analytics and session replays, used to improve the product. It runs in cookieless mode: its identifiers live only in the page's memory and are gone when you reload or close the tab. It sends data to eu.i.posthog.com in the EU. If your browser sends Do Not Track, PostHog records nothing. See the Privacy Policy for what it records and what it never sees.

Maps are rendered with Leaflet using swisstopo tiles (USGS tiles for US addresses) — we do not embed a Google map, so your browser makes no requests to google.com.

What we do not use

Being specific rather than hiding behind boilerplate — none of these exist:

  • Analytics cookies, or products such as Google Analytics
  • Advertising, retargeting, or social media pixels
  • Cross-site tracking or device fingerprinting
  • Preference cookies

We do count page views with Vercel Web Analytics, served from our own domain. It sets no cookies and writes nothing to your browser's storage; see the Privacy Policy for what it records.

We also use PostHog, described above, without cookies or browser storage. Because we set no non-essential cookies and store nothing non-essential in your browser, there is no cookie banner. To opt out of PostHog, turn on Do Not Track in your browser.

How to check or clear cookies

You can inspect exactly what this site stores: open your browser's developer tools and look under Application → Cookies (Chrome, Edge) or Storage (Firefox, Safari).

To clear or block: use your browser's privacy settings, or clear site data for this domain. Signing out, or deleting your account from the Settings page, also clears the session. If you block the session cookie you can still read the public pages, but you will not be able to stay signed in or use saved areas.

Changes to this policy

If we ever add a cookie beyond the one above, we will update this page before doing so and, where consent is required, ask for it first.

Contact

Questions about cookies? Reach out at tino.rosenkrantz@gmail.com.