📊 scrumia-web-audience

What it is responsible for

Nine refusal rules and a checklist: events come from a closed catalogue; one module owns the tracker and pages declare events by attribute; the address sent is the path template; the module sends a closed body straight to the tool's collection on the site's own domain; the proxy opens that one route and writes the client address; the page is never touched by a failure; nothing is measured outside production or against a browser signal; the opt-out is a marker the tool respects, in the privacy policy; the tool has its own database. No cookie is not no tracker, and the policy says so. The checklist turns the exemption conditions into fifteen closed questions. Umami is the example. Ships a web-audience-audit skill with ten questions and a detector that lists files outside the module that touch the tracker queue — a text search, so an aliased call is not found.

What it refuses

An event the specification does not list. A page that calls the tracker itself. A query string, a fragment or a code in a path sent to the measurement. A measurement outside production. An opt-out shorter-lived than the measurement, or ignored when it cannot be read. A proxy that relays more than the collection. A tool sharing the application's database. A policy that says no tracker for a computed identifier. Campaign attribution presented as exempt.

The assumption it makes

Assumes the measurement is exempt as a whole or not at all, so every addition is checked against the conditions before it ships. The checklist paraphrases the French authority and says its current text prevails; a project under another authority keeps the structure and swaps the checklist. Costs a specification change per new event, and pays back in a privacy policy that stays true.

Its skills

• web-audience-audit

Tags

• scrumia
• analytics
• privacy
• consent
• web

What it plugs into

Install it

Read the source on GitHub