Skip to content

Legal framework Reference politique-des-temoins

Cookie policy Dated, versioned, public.

The cookies and other storage the website and the app use, what they are for, how long they last and how to manage your choice.

Version1.3Effective dateNovember 12, 2026

The PDF of this version will be offered here when it is published; previous versions, from the next one onwards.

Section 01

In short

  • The public website itself sets no cookies; it only measures its audience if you accept it, and always without cookies.
  • The app uses the cookies needed for your sign-in and the security of your account, and the one for measuring the app's usage.
  • Usage measurement is a condition of use of the app, set out in the terms and conditions: it is on from the opening of your account and at each sign-in. The pages before you sign in are not covered.
  • We use no advertising cookies and do not track you from one site to another.

Section 02

What a cookie is

A cookie is a small file that a website saves in your browser and reads again on your next visits. This policy also covers similar techniques: your browser's local storage and session storage, and the cache of a web application.

  • A necessary cookie is one without which the service you ask for cannot work, for example to keep you signed in. It does not require your consent.
  • A non-essential cookie is used for something else, such as audience measurement. It is only set with your prior consent.

Section 03

On the public website

  • The arnoldkom.org website itself sets no cookies and writes nothing to your browser's storage.
  • Only with your consent, it measures its audience with PostHog: pages viewed, the site you came from and a link's campaign, without cookies, without recording your visit and without a profile. A banner offers it to you; "Refuse", or not answering, loads nothing.
  • Your choice, like that of a light or dark theme, moves from page to page in the address of the links, without keeping anything on your device; the measurement choice is asked again on your next visit.
  • The website is delivered by Cloudflare (section 6). As of the review of 29 October 2026, no Cloudflare cookie is set on arnoldkom.org.

Section 04

In the app: necessary cookies

These cookies belong to the address app.arnoldkom.org only: no other site or subdomain can read or write them. They only travel over encrypted connections, and the pages' scripts cannot read them.

  • __Host-bff-session (your session): it only contains an opaque identifier; your sign-in tokens stay on our servers. It is erased when you close your browser. On our servers, the session ends after 30 minutes of inactivity and, at the latest, 8 hours after sign-in. Your browser does not send it when you arrive from another site.
  • __Host-bff-appareil (trusted device): it is only set if you tick "Trust this device". It spares you the second factor on that device for 30 days, never the password. Signing out of all your sessions erases it.
  • __Host-bff-souvenir (remember me): it is only set if you tick "Remember me" when you sign in. It only contains an opaque identifier: your email address and name stay encrypted on our servers, and the sign-in screen suggests them for 30 days. It never signs you in by itself. "Not you?", a sign-in without the box and signing out of all your sessions erase it.
  • __Host-bff-federation (sign-in with Google): it links your return from Google to the request that left your browser. It lasts 10 minutes and is erased on your return.
  • __Host-aplomb-deces (reporting a death): it gives the person who reports a death and uploads documents access to their file. It lasts 2 hours at most. It is only used once the public page for reporting a death is open; until then, it is never set.

Protection against forged requests is tied to your session: it does not set a separate cookie.

Section 05

In the app: usage measurement, a condition of use

  • Service: PostHog.
  • What is measured: pages viewed, clicks, including those that have no effect, certain steps of your journey identified by a code, and recording of your sessions, to understand how the app is used and improve it.
  • What is masked: your inputs, your amounts and your identifiers in the recordings; the text of the pages in the events; identifiers in page addresses. We send PostHog neither your name, nor your email, nor your account identifier.
  • Pseudonymous identifier: to count you as the same person from one device to another, we send PostHog an identifier computed from your account with a key that only our servers hold; without that key, it cannot be traced back to you.
  • Surveys: after certain steps, a short multiple-choice question may be asked (your satisfaction after activating a bot, the reason for leaving your journey); answering is optional, and no free text is asked of you.
  • When: as soon as you are signed in, under the terms and conditions you accept when opening your account; measurement stops when you sign out. The public website is not covered (section 3), nor are the pages before you sign in.
  • What is stored: a PostHog cookie belonging to app.arnoldkom.org only, whose name starts with ph_ and ends with _posthog, valid for one year and limited to encrypted connections. PostHog also uses your browser's session storage, to tell your tabs apart, and its local storage, to remember that measurement stopped after you sign out and which surveys were already offered.
  • It applies to your account, on every device where you are signed in, and cannot be turned off while your account is open: it ends when the account is closed.
  • Signing out stops the measurement and erases PostHog's state on the device, except the record of that stop; any PostHog cookie left there is not used until your next sign-in and ends when it expires.
  • Retention at PostHog: events for at most one year, session recordings for at most 30 days.
  • IP address: like any online service that receives a request from your browser, PostHog receives your device's IP address with each transfer. Aplomb's PostHog project does not keep that address.

Section 06

Our providers' cookies during certain steps

  • Cloudflare protects the app against malicious robots and attacks. It may set security cookies needed for this protection, for example after a human verification (Turnstile); their names and durations are set by Cloudflare, such as __cf_bm or cf_clearance. As of the review of 29 October 2026, no Cloudflare cookie was set on app.arnoldkom.org, including when the human verification loads, which runs in a challenges.cloudflare.com frame; auth.arnoldkom.org sets no cookie in your browser.
  • If you choose to sign in with Google, you go through Google's pages, which use their own cookies under Google's policy. We have no access to them.

Section 07

Other storage in your browser

  • The app writes nothing to your browser's local storage or session storage, except what usage measurement uses (section 5). The public website writes nothing there, even if you accept its audience measurement.
  • To show you a message if your Internet connection drops, the app saves an "offline" page and its style sheet in your browser's cache. This cache contains no personal information.

Section 08

What we do not use

  • No advertising cookies, no social network pixels, no tracking from one site to another, and no sale of browsing data.
  • Device identifier: the app can set a cookie, __Host-aplomb-appareil, valid for one year, used to spot a device used by several accounts. This feature is turned off: this cookie is not set. We will update this policy before turning it on.

Section 09

Managing your choices

  • On the public website, the audience measurement banner offers "Accept" or "Refuse"; your choice applies to the visit and you are asked again on the next one.
  • In the app, under "My personal data", the "Cookies" page shows the cookies in use. Usage measurement is not a choice there: it is set out in the terms and conditions, and not accepting them prevents you from using the app.
  • Your other choices are made on the "My consents" page, and each one is dated.
  • Your browser also lets you delete or block cookies. If you block the necessary cookies, you will not be able to sign in to the app.

Section 10

Changes to this policy

Each version of this policy has a number and an effective date, and comes with a summary of what changes. Previous versions remain public on this page. We update it before using any new non-essential cookie or any new measurement provider.

Versions

Version 1.3

Effective date: November 12, 2026

Version 1.3: the public website may measure its audience with your consent, given in a banner, without any cookie; in the app, usage measurement counts you as the same person through a pseudonymous identifier, records clicks with no effect, and two short multiple-choice questions may be asked.

Each new version will be dated and summarized here, and earlier versions will stay public on this page.

All legal documents