Privacy, consent & data deletion
Consent categories, data minimization, subject erasure and retention.
Consent categories
- analytics — required for any event to be stored.
- personalization — required for experiments, experiences rolled out to a percentage, and most campaigns.
- marketing — required for campaigns configured with marketing consent.
Data minimization
Use pseudonymous user IDs only. PII-like property keys are stripped on ingest. Payment card data is never accepted. Only aggregates are used in AI prompts, and cloud AI providers are disabled unless the platform and your organization both opt in.
Erasure and retention
Admins can erase a data subject (DELETE /v1/projects/{id}/users/{user_id}) and purge events older than the project’s retention period. Both actions are audit-logged.
Children
Mark child-directed or mixed-audience projects in project settings. Personalized offers are then disabled or restricted, monetization changes always require human approval, and dark-pattern lint violations become hard errors.