Privacy and consent
Track only after a yes, keep personal data out of events and recordings, and delete raw events on a schedule. Marketing consent lives with each channel.
- Required 3
- Recommended 1
Required
Track only after consent
ANA-7 EU lawSend no analytics event that uses device storage or identifies a person until that person has agreed. Read the stored choice in the tracking module itself. Without a yes, count visits only, with no cookie, no device storage and no ID.
Keep personal data out of events
ANA-8Never put names, email addresses, phone numbers, free text or full URLs with query strings in event properties. Use an internal ID that analytics cannot turn back into a person.
Hide personal data from session recordings
ANA-9Session recording and heatmap tools mask every typed value and all text from customer records before anything leaves the browser. They record nothing on payment, sign-in or account settings screens.
Recommended
Delete raw events on a schedule
ANA-10Keep raw events with an analytics ID for a fixed time only, such as 14 months. Then delete them or roll them up into counts without IDs.
Read this with
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/analytics/privacy-and-consent">Agent Wranglers product analytics and experiments playbook</a>. In code you write, add a comment next to it with the same link.