Measuring without a consent banner¶
In France, the CNIL exempts audience measurement from consent when the tool, as configured, meets a set of criteria. It asks the tool's provider to assess them with its self-assessment tool (July 2025), and to give publishers a document that shows how, and what to configure. This page is that document, in the form the CNIL's template gives. Other European regulators apply the same ePrivacy rule, with their own guidance.
According to our self-assessment, Abilian Analytics meets the criteria set by the CNIL (audience measurement solutions). It can then be used without the visitors' consent, when configured as described here. This is our assessment: the CNIL certifies no tool. Each criterion below says what it rests on.
Like the CNIL's tool, this page covers the exemption from consent only. The GDPR's other duties remain, such as a privacy policy and a record of processing activities.
What to configure¶
Set these on the Privacy page of each project's settings:
- Consent-exempt mode: on. New projects start with it on. It turns off what the criteria exclude:
- campaign parameters (
utm_…): not kept, and no campaigns table; - referrers: their site alone, such as
news.example.org; - the visit log and its CSV export, in the app and in the API;
- any figure about 1 to 9 visits: table rows, goals, comparisons with the period before, and filtered reports with fewer visits. A filtered report shows no chart.
- campaign parameters (
- Ignore visitors who send Do Not Track or Global Privacy Control: on (the default).
- Keep visits for (days): 760 days at most, the CNIL's 25 months.
- The privacy notice, from the Privacy notice card, pasted into each site's privacy page, with the opt-out switch it contains. The Sites card, on the General page, then shows where the switch was seen.
The Without a consent banner card, on the same page, checks these four points, and says what is missing; the Instance health page lists the projects that miss one. Nothing is blocked.
Visits recorded before the mode was turned on keep their details in the database, though the reports no longer show them. Imported history (from Umami or Matomo) is shown the same way.
Purposes¶
Abilian Analytics serves only:
- measuring performance;
- detecting navigation problems;
- optimising technical performance and ergonomics;
- estimating the server capacity needed;
- analysing the content viewed.
It explicitly excludes any marketing measurement (the performance of conversion channels, of advertising campaigns, of acquisition channels, the fight against ad fraud) and any cohort of visitors shown different content. Of such features, it has campaigns only, which consent-exempt mode turns off.
The criteria¶
Each criterion is the CNIL's, with the technical measure the CNIL recommends. "Met" assumes the configuration above.
The tool's only purpose is to measure the site's audience¶
| Criterion | Met | How | What to do |
|---|---|---|---|
| The provider explains how to turn off what falls outside this purpose. | Yes | This page. | Turn on consent-exempt mode. |
| The data collected is minimised. Recommended: from the HTTP headers, the major versions of browser and system at most; three kinds of events at most. | Yes, with two coarse facts more | From the headers: the browser's and the system's names and major versions, and the kind of device. From the tracker, beyond the recommendation: the screen's width as one of four classes (phone, tablet, laptop, desktop), never its size, and the browser's language as its first subtag (fr). Both are shown only in figures of 10 visits or more, and single no one out. Three kinds of events: page views (the page's path, and whether it was a not-found page), the use of a feature (custom events, clicks on outbound links and downloads, with their destination or label) and timings (load time, time on page, scroll depth, the Core Web Vitals). |
Name custom events after features ("Signup", "Menu"), and put nothing personal in their properties. |
The provider acts as a processor¶
| Criterion | Met | How | What to do |
|---|---|---|---|
| A data processing agreement, with the terms of GDPR article 28. | Not applicable | Abilian Analytics is free software that you run: there is no provider between you and your data. | If someone runs it for you, they are your processor: ask them for this agreement. |
| No pooling of raw data from several clients. | Yes | Each project's visits are counted for it alone. The filtering lists shared by an instance hold networks and spam domains, not visits. | – |
| No reuse of the data for the provider's own purposes. | Yes | The software sends no visit data anywhere, and has no telemetry. It only fetches the GeoIP databases and the sites' favicons. | Same request to anyone running it for you. |
| A contact point for questions on compliance. | Yes | The project's issue tracker. | – |
The tool does not follow a person beyond the site¶
| Criterion | Met | How | What to do |
|---|---|---|---|
| No import of external data. Recommended: no customer, campaign or UTM identifier collected from URLs; referrers reduced to their domain; no integration with third-party tools. | Yes | Of a page's address, only its path is kept, without query string. Referrers keep their host alone. There is no integration with other tools. | Consent-exempt mode. Don't use the imports to load data from other sources than your own past measurement. |
| No identifier that follows a person across domains. Recommended: a first-party cookie if any; the IP address used for a location no finer than the city, then pseudonymised by removing at least its last byte; a fingerprint, if any, with a part specific to the site and a part limited in time; no tag that collects personal information (from forms). | Yes, with an alternative measure for the IP address | No cookie. The country alone is read from the IP address, with a local database; the network's number is kept, to leave out hosting networks. The IP address is never stored. The pages of a visit are linked by a hash of the IP address, the browser's user agent, the project's identifier (the part specific to the site) and a random salt that changes every day and is deleted after two days (the part limited in time). Without the salt, the hash can't be linked back to an address: we hold this to be stronger than removing the last byte, which is why the full address goes into the hash. The tracker reads no form. | – |
| No feature to cross-match, deduplicate or measure the unified reach of content. | Yes | There are no unique visitors, across days or sites: the reports count visits. | – |
The data serves only to produce anonymous statistics¶
| Criterion | Met | How | What to do |
|---|---|---|---|
| The reports, on screen and in exports, hold only anonymous statistics. Recommended: aggregated, and presented to the nearest ten; otherwise, an analysis that justifies their anonymity. | Yes, with an alternative measure | Reports show counts and averages. Instead of rounding to ten, any count from 1 to 9 visits is held back (MIN_VISITS): a table row, a goal, a comparison with the period before, a filtered report. The project's own totals and chart are shown exactly: they cover every visitor, without any criterion to select some of them. The API exports the same reports. |
Consent-exempt mode. |
| Anonymisation holds whatever the selection criteria: no combination of criteria singles out a visitor. | Yes | A filter is a selection: a filtered report shows nothing when fewer than 10 visits match it, or from 1 to 9 in the period before; the rows under it follow the same rule. Filtered reports have no chart, whose hours or days could hold a single visit. | Consent-exempt mode. |
| No following of one visitor's navigation. Recommended: no session replay. | Yes | No session replay. Consent-exempt mode turns off the visit log, the one place that lists visits one by one. | Consent-exempt mode. |
Visitors can object¶
| Criterion | Met | How | What to do |
|---|---|---|---|
| A way to object, as there is processing of personal data. Recommended: a button or a link in the site's privacy policy. | Yes | A checkbox, which the tracker draws in the opt-out element; Do Not Track and Global Privacy Control are respected too. | Paste the privacy notice, which holds the switch, into each site's privacy page. |
| The objection lasts. Recommended: an opt-out cookie, or a fingerprint added to a list. | Yes | The objection is kept in the browser's local storage for the site, the equivalent of an opt-out cookie, without expiry. The browser then sends nothing. | – |
Retention¶
The CNIL recommends keeping the collected data for 25 months at most, and reviewing that period from time to time. Set Keep visits for (days) to 760 days or less. Visits left out of the reports (bots, hosting networks) are deleted after 30 days, a setting of the instance (EXCLUDED_RETENTION_DAYS). The tracker stores no tracer in the browser, so the CNIL's 13 months for tracers don't apply. The stored objection is no tracer either.