Cookie Policy

Updated: September 7, 2026

The KidiPass website uses very few cookies. There are no advertising cookies that follow you across other sites, and the child's app has no cookies and no ads at all.

Exactly what is stored

Sign-in cookie (Firebase Authentication)
Keeps the parent signed in so a password is not needed on every screen. Essential — the parent dashboard cannot work without it.
How long: Until sign-out
Language preference
Remembers whether Hebrew or English was chosen so the site does not fall back to the default on every visit.
How long: Up to a year
Technical local storage
Keeps display preferences and unfinished form state on the device. Not sent to our servers.
How long: Until browser data is cleared
Usage measurement (Microsoft Clarity) — the _clck and _clsk cookies
A Microsoft tool that anonymously records in-page interactions — clicks, scroll depth, and places where people get stuck — to find screens that are unclear. It runs on the public marketing pages of the site only, when enabled in the site configuration; it is not loaded on signed-in dashboard screens and does not exist in the child's app. _clck identifies a returning browser, _clsk groups events into one visit.
How long: _clck up to a year, _clsk one day
Meta measurement pixel
Measures how many people who arrived from an ad actually signed up. Runs only on the campaign landing pages (/start and /early) — not on the regular site pages and not in the parent dashboard.
How long: Up to 90 days

What it is	What it is for	How long
Sign-in cookie (Firebase Authentication)	Keeps the parent signed in so a password is not needed on every screen. Essential — the parent dashboard cannot work without it.	Until sign-out
Language preference	Remembers whether Hebrew or English was chosen so the site does not fall back to the default on every visit.	Up to a year
Technical local storage	Keeps display preferences and unfinished form state on the device. Not sent to our servers.	Until browser data is cleared
Usage measurement (Microsoft Clarity) — the _clck and _clsk cookies	A Microsoft tool that anonymously records in-page interactions — clicks, scroll depth, and places where people get stuck — to find screens that are unclear. It runs on the public marketing pages of the site only, when enabled in the site configuration; it is not loaded on signed-in dashboard screens and does not exist in the child's app. _clck identifies a returning browser, _clsk groups events into one visit.	_clck up to a year, _clsk one day
Meta measurement pixel	Measures how many people who arrived from an ad actually signed up. Runs only on the campaign landing pages (/start and /early) — not on the regular site pages and not in the parent dashboard.	Up to 90 days

How to reduce them

You can control cookies in several ways:

Browser settings can block third-party cookies, delete existing ones, and delete _clck and _clsk specifically. Blocking the sign-in cookie will prevent use of the parent dashboard.
Private browsing clears all cookies when the window closes.
Per Microsoft's documentation, Clarity does not record browsing when the browser's "Do Not Track" setting is on. The Meta pixel can be blocked with common content blockers or through the ad settings of a Meta account.
You can ask us at any time to exclude your browsing from the measurement tools — just write to support.

Why there is no consent banner

The cookies the site sets are essential or a language preference, and the measurement tools run on marketing pages only and without personal identification. If we ever add a tool that requires prior consent, we will show a consent banner and update this page.

Questions about cookies

Write to support and we will explain exactly what runs and when.

[email protected]