Skip to content

Postmetry

Cookie Policy

This site sets one cookie, and it only serves to protect your forms. A second one appears when you open an audit request or the customer area. Here is which, why, and everything that is not there.

Updated on

2. What this site sets

2.1 The form-protection cookie

Name: csrftoken. It is set when you open a page that contains a form — the contact page, submitting an email for analysis, checking a suspicious email, the diagnostic. It ensures that a submitted form really comes from the page you are looking at, and not from a third-party site making you act without your knowledge. It contains only a random value, does not identify you, and is read by no one other than this site. Duration: one year.

2.2 The confirmation message

Name: messages. After a form is submitted, it carries the confirmation or the error from one page to the next, then it is deleted as soon as it has been read.

2.3 The session cookie

A session cookie (sessionid) appears in two situations. When you open an audit request, it keeps that request's token, so your report finds you again in the same browser: it contains nothing else, and it expires after two weeks. When you sign in to the customer area, it keeps you signed in; it is renewed at each sign-in and removed on sign-out or after two weeks. A third cookie (django_language) would remember the language you choose, if the site served more than one. It serves only one, French, so this cookie is not set for you.

2.4 Local storage

Two preferences are kept in your browser's local storage, never sent to the server: the light or dark theme you choose in the customer area, and the families you collapse in the sending platform comparison. They stay on your device; clearing them simply restores the default settings.

3. What is not there

On this site:

  • no advertising or targeting cookie;
  • no third-party tracker, no social network button;
  • no font or image loaded from a third-party domain;
  • no audience-measurement cookie.

The only script that does not come from this site is the audience-measurement one, Plausible Analytics, which sets no cookie and uses no persistent identifier: it counts page views, where they come from, device type, and country, without keeping the IP address. That is what lets us measure it without asking your agreement — and a product that measures other people's pixels was not about to set one of its own.

4. How to control them

Your browser lets you refuse or delete cookies, site by site. Blocking the form-protection one prevents you from submitting a form on this site; blocking the session one prevents you from staying signed in to the customer area. Nothing else changes.

5. Changes

If what the site sets changes, this page changes with it, and so does its date. We will not add a tracker subject to consent without asking you first.