Agencies get asked the same question: where does our customers' data go? The privacy pack answers it from the client's real setup, not a template. Generated, not written by hand, so it can't drift from what the system does.
The tables that exist for that client, what each holds, and which hold nothing identifying.
What is counted without consent, what is observed after a yes, and what is inferred and labelled.
Each ad platform switched on, what is sent, and the gate it passes first. Declined or modelled data is never sent.
On the client’s own subdomain, in databases located in the EU, under UK data law.
The retention for each kind of data, as configured.
The erasure route, from the button in the hub to every platform the person’s data reached.
Made-up client, made-up setup. The real pack is built from yours.
| Table | Identifying? |
|---|---|
| daily_metrics | No |
| consent_log | Pseudonymous |
| customers | Email encrypted |
| orders | Linked to a customer |
The pack is in build. It ships to founding clients first, generated from their own setup.
Apply for a founding slotThis explains the law in plain English. It isn't legal advice.