Consent & k-anonymity guarantees
The privacy guarantees behind every segment — consent gating, k-anonymity, and no PII.
Every segment you license carries the same guarantees, enforced in the data path rather than promised in a contract. This is what you can tell your own compliance team.
Consent-gated at ingestion
Data enters the pipeline only where consent allows, decided at the edge before anything is stored:
- In the EU/EEA and UK, events are dropped when a visitor hasn’t consented.
- Elsewhere, data may be collected but is gated from sale unless consent permits it.
When someone withdraws consent, a suppression list removes them from future processing — the withdrawal propagates rather than sitting stale.
k-anonymity floor
No segment or signal is served below a minimum cohort size (a floor of 50), enforced at multiple layers of the pipeline. Anything that would fall below the floor is never listed and never delivered — individuals can’t be singled out.
No raw events, no PII
- Identifiers are hashed at ingestion; raw personal data never reaches the analytics warehouse.
- The Data Platform API serves only aggregated, pseudonymous data, through allowlist serializers that make exporting raw events or PII structurally impossible.
Access is contracted
Partner access uses dual credentials and is gated behind a signed data agreement (DPA). Provisioning is handled by the AskThis team — see What the data platform is.