7 withdrawals have not fully propagated
Two systems — the Scheme Beneficiary Warehouse and the AI Assistant Knowledge Base — are not acknowledging withdrawal notifications. Continuing to process after withdrawal is the single most visible failure to a Data Principal, and the most common source of grievances.
Withdrawals recorded
30
Fully propagated
23
Awaiting acknowledgement
7
Involving children
2
How withdrawal propagates
A withdrawal is recorded on the artefact, then pushed to every system the purpose declares as downstream. Discovery marks the affected elements as withdrawn, DLP starts blocking their transfer, the AI Guard denies retrieval, and the retention manager queues erasure where no other lawful ground applies. A system that does not acknowledge is treated as still processing.
30 withdrawals
1–25 of 30
1 / 2