← Back to heifamily.com
Legal · Cookie Policy

Cookie Policy

Last updated: 4 November 2026 · Applies to heifamily.com and to the heifamily web dashboard

1The short version

We do not use cookies. Not for advertising, not for analytics, not to build a profile of you. There is no tracking pixel on this site and no third-party advertising network.

We do keep a few small items in your own browser: on the homepage, the language you choose, and only once you choose it; on the sign-in pages and in the web dashboard, what they need to keep you signed in and to work. Sections 3 and 4 list every one of them, including what the software we load from other companies keeps.

Everything we keep is strictly necessary for the service you ask for: showing the site in the language you chose, keeping you signed in and making the dashboard work. Under the ePrivacy rules, storage of that kind does not need your consent, so this site does not show a cookie consent banner.

2Cookies

heifamily.com and the heifamily web dashboard do not set any cookies of their own. We do not read or write document.cookie anywhere in our code.

3What we store in your browser

The other public pages, including this one, keep nothing. The homepage keeps nothing either until you choose a language under Language & country; from then on it keeps two items in your browser's local storage:

  • hf.lang — the language you chose, saved only when you choose one under Language & country or in the dashboard's Settings, so that the sign-in page and the dashboard open in the same language. It stays until you clear your browser's data.
  • hf.lang.pick — the language you choose yourself under Language & country, saved only when you choose one. The next time you sign in to the dashboard, it becomes your account's language, which the app and our e-mails also use, and it is then removed from your browser.

The sign-in pages and the web dashboard also keep the following, and nothing else:

  • Your sign-in session. Handled by Firebase Authentication, which keeps your session in the browser's IndexedDB (falling back to local storage). Without it you would be signed out on every page you open. It is removed when you sign out.
  • What the Firebase software keeps (firebase-heartbeat-database, in IndexedDB). The Firebase software we load records, for up to 30 days, on which days it ran and which of its versions, and sends that summary to Google with its requests. While you confirm your identity through Google, it also keeps a temporary marker in the tab (firebase:…), removed when the tab closes at the latest.
  • A browser identifier (hf.web.id.v1). A random code for this browser, which we also save with your family's account. It keeps the dashboard open in one browser per parent at a time — signing in on another computer signs this one out — and lets us e-mail you when your account is opened in a browser we have not seen before. It stays until you clear your browser's data.
  • Items for the current tab (hf.lock.v1, hf.lock.reauth.v1, hf.web.claimed.v1, hf.delete.reauth.v1). Which account last unlocked the PIN lock and when, plus short-lived markers used while you sign in, confirm your identity or delete your account. Your browser removes them when you close the tab. The one-hour access token for the dashboard's maps (heifamily_mapbox_token, from Mapbox) is kept here too, only for your account, and also goes when you close the tab.
  • Your language (hf.lang), saved only when you choose one in Settings or on the homepage, so the dashboard appears in it before your settings have loaded.
  • Map appearance (card_map_style, premium_map_style). The map style you last chose from the map menu, so the maps open in it again. It stays until you clear your browser's data.
  • Cached icon addresses (appicon:…, hf_icon_…). The addresses of small app icons already fetched, so they are not requested again on every visit. They stay until you clear your browser's data.

We use none of these items for advertising or analytics. Only the Firebase summary and your sign-in session, which the Firebase software sends to Google to prove it is you, leave your browser for another company; what Mapbox keeps is described in section 4. Two items also reach your account: the browser identifier, and your language (saved when you create the account, and replaced by any language you pick later). Everything else stays in your browser.

4Services we load from other companies

The public pages load nothing from other companies. Some parts of the sign-in pages and of the dashboard are served by other companies: when your browser requests a file from them, it necessarily reveals your IP address to that company, and they may store their own data in your browser under their own policies. We load:

  • Mapbox — the maps in the dashboard, together with address lookup and road matching. Showing a map tells Mapbox which area is on screen. To draw your child's routes along real roads, the dashboard sends Mapbox the coordinates of your child's day, with their times and accuracy; to show an address, it sends the coordinates of that point. Mapbox's map software keeps an identifier in your browser (mapbox.eventData…) and reports each map load to Mapbox, which uses these reports to bill us; it may also keep map tiles in your browser's cache (mapbox-tiles). We have switched off its optional performance reports.
  • Google — the Firebase software that runs sign-in and data access: your family's data, including your child's, reaches your browser through it, and Google stores it for us, as our Privacy Policy explains. Also Google Maps place search on the Places screen, which receives what you type and a nearby point from your child's places, to rank the results. All our pages, including the sign-in pages and the dashboard, serve their fonts themselves, from this site.

Beyond what is described above, the dashboard sends these companies nothing about you or your children.

6Seeing and deleting what is stored

Signing out of the dashboard removes your session, and closing a tab removes the items kept for that tab. Everything else can be cleared at any time from your browser's settings, usually under a heading such as "Cookies and site data" or "Clear browsing data". Clearing it signs you out and is otherwise harmless: the dashboard rebuilds what it needs, and your next sign-in from this browser counts as a new browser, so you may receive an e-mail about it.

7Changes to this page

If we start using storage for a new purpose, we will update this page before we do, and change the date at the top.

8Contact

Questions about this page, or about anything privacy-related, go to privacy@heifamily.com. Our full Privacy Policy explains what we collect in the service itself, and the Terms of Service describe the agreement between us.