Ereignisschema, Einwilligung vor dem Tracking, keine personenbezogenen Daten, Speicherung in der EU.
Spec — Analytics with consent
Status: draft · Created: 2026-11-10
1. Context and goal
The product team measures how features are used, while visitors decide whether they are tracked and no personal data leaves the EU or reaches the analytics store.
2. Functional requirements (EARS)
- FR-1: THE SYSTEM SHALL validate every event against a versioned schema of names and properties, and drop events that do not match, counting them per day.
- FR-2: WHILE a visitor has not given consent, THE SYSTEM SHALL send no analytics events and set no analytics cookies or storage entries.
- FR-3: WHEN a visitor arrives for the first time, THE SYSTEM SHALL show a consent banner where accepting and declining take one click each.
- FR-4: WHEN a visitor withdraws consent, THE SYSTEM SHALL stop sending events within 1 second and delete the analytics identifier from the device.
- FR-5: THE SYSTEM SHALL strip names, email addresses, IP addresses and free-text input from events before they are sent.
- FR-6: THE SYSTEM SHALL store analytics data only in EU data centers and delete raw events after 13 months.
- FR-7: THE SYSTEM SHALL record each consent decision with its time and the version of the consent text.
3. Out of scope
- Advertising and remarketing pixels.
- Session recordings.