Skip to content
Kilomeet

Cookies and storage

Version 0.2 · updated October 1, 2026

English translation provided for information only: the French version is binding.

Why there is no banner

Kilomeet only sets cookies that are strictly necessary for the service you ask for. Such cookies are exempt from consent (French Data Protection Act, art. 82), so there is nothing to accept or refuse.

A visit without signing in sets no cookie at all. We measure audience only with daily totals computed on our server, with no cookie, no IP address and no identifier. No advertising tracker, no social-media button, no third-party analytics.

The cookies we use

  • __Host-session

    Role
    Keeps you signed in (a session identifier, nothing else).
    Where
    Kilomeet website
    Set
    Only after you enter your sign-in code, or sign in with your passkey.
    Lifetime
    30 days rolling, 90 days at most; deleted when you sign out.

  • __Host-passkey

    Role
    Ties your device to the check of your passkey (a signed challenge identifier, nothing else).
    Where
    Kilomeet website
    Set
    Only when you tap “Continue with my passkey” or “Add a passkey”.
    Lifetime
    5 minutes, deleted as soon as the check is done.

  • __Host-km_console

    Role
    Session of the read-only admin console, used by the founder.
    Where
    Admin console, on a separate origin
    Set
    Only on the console’s own origin, reachable over the VPN; never on the public site.
    Lifetime
    12 h at most, and 30 minutes of inactivity; deleted when you sign out.

Storage on your device

Besides cookies, some features may store information on your device, only after an action of yours. They are listed here with the feature that creates them.

  • localStorage km.scan-dismissed.*

    Role
    Stops showing “Scan each other” on a run’s page once you closed it (nothing is sent anywhere).

  • localStorage km.announce.landmark

    Role
    Prefills “Where I start from” with the last public place you picked (a metro, a park gate), on this device only: Kilomeet keeps no history of your starts.

  • localStorage km.signedIn

    Role
    Remembers that this browser was signed in, so the home opens straight on your page instead of the presentation (no data about you, removed as soon as you are signed out).

  • Service worker /sw.js

    Role
    Shows the notifications you turned on and opens the run when you tap one. It caches nothing and stores no data about you.

  • Abonnement aux notifications (PushSubscription)

    Role
    Created by your browser only when you tap “Turn on notifications” and accept its prompt; deleted when you turn them off or sign out of this device.

Third-party content

Our pages embed no content loaded from another site. A link to Instagram, Strava or a map sends nothing until you click it. If a video or widget is ever embedded, it will load only after you click.

Managing cookies

You can delete or block cookies in your browser settings. Blocking the session cookie only stops you from staying signed in.