Why this matters
The advanced analytics level traced how data flows between tools so metrics stay consistent. The same flows carry people's choices, and whoever leads measurement answers for both. In this exercise's wine club, the sign-up form captured the member's permissions and the unsubscribe link worked; her choice was lost in the handovers between the tools that should have acted on it.
The tutorial on mapping consent across the stack lays out one row per purpose, from capture to every reader, with a test and an owner. The guide to data retention across marketing tools locates each copy of a person's data, ties each to a purpose and a period the data protection owner sets, and makes deletion reach all of them. This exercise, like both pages, gives no legal advice and chooses no Lawful BasisOne of the six grounds the GDPR accepts for processing personal data, such as consent, contract or legitimate interests, chosen for each purpose.: the map records the owner's decisions.
The wine club and the withdrawal that stopped
Blavoskin Wine Club is an invented online wine subscription club. Members receive a monthly case and are marketed to by email, text message and paid social. Its subscription platform holds member accounts, orders and the email and text permissions captured at sign-up, and its operations director owns data protection. A member who had paused her subscription complained that she still received texts and saw the club's ads after withdrawing.
Blavoskin Wine Club: the withdrawal, the tools and the owner's decisions
| Day | What happened | Where it was recorded |
|---|---|---|
| 1 | She clicks unsubscribe in the monthly email | Email platform, synced to the subscription platform overnight |
| 2 | She phones customer service and asks for no marketing of any kind | A helpdesk ticket |
| 6 | The weekly text file, exported with every member who has a mobile number, goes to the text tool | — |
| 9 | She receives a promotional text | Text tool |
| 14 | The freelancer uploads the lapsed-member list to Meta from an export that ignores the permission fields | Upload file saved to a shared drive |
| 17 | She sees the club's ads and complains again | Helpdesk |
| Tool | Member data it holds | How it learns consent | Retention today |
|---|---|---|---|
| Subscription platform | Accounts, orders, email and text permissions | Holds them | Everything since launch |
| Email platform | Subscribers, engagement logs | Sync; unsubscribes sync back | Platform default |
| Text tool | Numbers, message history | Its own STOP list | Platform default |
| Helpdesk | Tickets with contact details | Does not | Platform default |
| Meta | Lapsed-member audiences | Does not | 31 monthly audiences |
| Shared drive | Upload files; a win-back call spreadsheet | Does not | 31 files; 2,840 spreadsheet rows |
| Warehouse | Member table; analytics export keyed by member number | Does not | Since launch |
The operations director's decisions for this invented club, not recommendations: marketing to a lapsed member ends 24 months after the later of their last order and last email engagement; each upload replaces the previous audience and file; win-back calls end 6 months after a membership lapses; analytics export rows are kept for 25 months.
Purposes, copies and periods
Both guides start from purposes, not tools. One mobile number is held to send texts, to build an upload and to recognise someone who objected, and each purpose has its own basis, readers and period. Withdrawals and deletions travel the same routes, so the two maps are built together, and both rely on a record kept on purpose: the Suppression ListA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. that keeps an objection in force after the rest of a person's data has gone.
Task
- List each purpose the stack processes Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier. for, where its permission or other basis is captured, and the system that holds the record.
- List the tools that read each record and how, then trace the unsubscribe and the objection and mark where each stopped.
- Write the fix for each break, a test with a marked test record, and an owner for each row.
- Find every copy of member data, including those no integration explains.
- Turn the owner's decisions into a retention schedule: what starts each clock, what happens at the end, and what is kept on purpose.
- Design deletion that reaches every copy without a sync restoring it, and the record that shows it ran.
Worked answer
Where it stopped. The unsubscribe worked for email. Everything else failed: the text tool hears only its own STOP replies and the weekly file ignores the text permission; the objection sat in a ticket no tool reads; the upload was built from an export that ignores every permission field. Three breaks, one cause: copies updated independently instead of one record that every tool reads.
The consent map. The banner's choices live in the consent management platformSoftware that collects, stores and passes on visitors' consent choices for cookies and tracking.; marketing permissions and the global suppression list live in the subscription platform, where the most restrictive value wins.
| Purpose | Captured | Read by, and how | Test | Owner |
|---|---|---|---|---|
| Site analytics | Banner, analytics category | Tags, through consent mode | Reject in a clean browser | Analytics lead |
| Advertising tags | Banner, advertising category | Meta pixel, through its consent setting | Reject; the pixel holds back | Paid social lead |
| Sign-up opt-in, wording and date | Email platform, two-way sync | Test member excluded from the next send | CRM owner | |
| Texts | Separate opt-in at sign-up | Text tool, synced permission and suppression | Test member absent from the next text audience | CRM owner |
| Customer list uploads | The operations director's recorded basis | File built from the record, filtered at build | Test member absent from the file | Paid social lead |
| Win-back calls | The operations director's recorded basis | Call list built the same way | Test member absent from the list | Customer service lead |
Objections made by phone or by reply now follow the marketing opt-out request SOP, which runs each one along the map's routes to the suppression list in the subscription platform. The weekly text file and the spreadsheet are replaced by a sync and a list built from the record.
Copies. Beyond the tools, the search finds the copies no integration explains: old upload files, earlier Meta audiences, the spreadsheet, helpdesk tickets and export rows keyed by member number.
Retention schedule. Each purpose gets its clock, its end action (deletion, or reduction to a minimal record), its owner and the tools it runs in. Suppression entries keep the identifier, reason and date, and nothing else; consent records keep source, date and wording. Helpdesk tickets stay under the service team's own rules; the member's details held for marketing get their own period and are not kept longer because a ticket exists. The analytics retention setting becomes a recorded decision rather than a default.
Deletion. Delete in the subscription platform and let the deletion travel along syncs confirmed to carry it; where a route cannot, stop or filter it first, then delete downstream before upstream. Old files and audiences go, the spreadsheet is retired and the warehouse job drops rows past their period. Deletion cannot be undone, so the first run uses a small sample and checks that suppression entries and consent records survived. Each run is logged with rule, tool, date and count, without personal data; vendors' written confirmations go with the contracts.
Running it. The privacy and consent operations playbook makes this a routine: a monthly check that test members stay excluded, quarterly retention runs, and new tools reopening the map. The consent banner QA checklist is rerun whenever the banner changes, including its link to change choices from every page.
Blavoskin Wine Club: the first runs
The member's details turned up in 9 places. On the first monthly check the objected test member was still in the text audience, because the sync carried permissions but not suppression; on the second, it was absent from the send, the text audience, the upload file and the call list. The first retention run, on a sample of 40 records, cleared them from every tool but one: the text tool still held their message history, so a deletion step for it was added before the full run. The full run deleted 3,120 records and kept 412 suppression entries; 30 old upload files and 30 earlier audiences went, and 4 vendors confirmed deletion in writing.
Common mistakes
- Closing the complaint because the emails stopped. The unsubscribe only ever reached the email platform; the texts and the Meta upload were separate routes, and each needed its own fix.
- Adding this member to the text tool's STOP list by hand. It ends her texts and nothing else; the next objection taken by phone has the same gap until the text tool reads the subscription platform's suppression list.
- Leaving phone objections in helpdesk tickets. No tool reads a ticket, so the objection never reached the text tool or the freelancer's upload.
- Keeping the weekly text file running beside the new sync. Two routes then feed the text audience, and the file still ignores the text permission.
- Retiring the old Meta audiences but keeping their upload files. The files on the shared drive are copies of member data too, and the retention schedule has to reach them.
- Clearing lapsed members without exempting their suppression entries. If the complaining member's number came back in a win-back list, nothing would block it.
- Letting the freelancer decide how long upload files stay on the drive. The operations director has already ruled that each upload replaces the last; the schedule carries out that decision rather than making a new one.
The checkpoint on consent maps, retention and privacy operations puts these judgements to a garden design studio.
