Why Pulsar does not ask for consent

This is the question that comes up most, and it deserves a precise answer rather than a claim.

In short

Pulsar sets no cookie and keeps no identifier that could recognise a person from one day to the next. The ePrivacy Directive therefore does not require prior consent, and no banner is needed.

What the rule says

The ePrivacy Directive requires consent for any reading or writing of information in a visitor's device, cookie or not. So it is not the absence of a cookie that exempts you, it is the absence of storage.

Pulsar writes nothing in the browser. Each visit is attached to an identifier computed on the day itself, from data the browser sends anyway, and that identifier changes daily. No data remains on the visitor's side between two pages.

The limits of that exemption

The exemption covers strictly necessary audience measurement, not any use whatsoever. Three things make it fall, and they are worth knowing.

Cross-referencing with other processing. If you match statistics against a customer database to identify people, this is no longer audience measurement.
Following a visitor from one site to another. Pulsar does not allow it, each site being kept separate.
Adding other trackers. An advertising pixel placed next to Pulsar imposes its own banner. The exemption covers Pulsar, not your whole site.

That is exactly what compliance monitoring watches: it detects third-party trackers that have appeared on your pages, including those added by an extension or a supplier without telling you.

What you must still do

No consent does not mean no information. Your privacy policy must state that you measure your audience, with which tool, for what purpose and for how long.

You remain the data controller, Pulsar being the processor. A processing agreement is available in your account, signed and dated.