How do I handle a sudden influx of right-to-be-forgotten requests in our CRM while keeping our audit logs intact for legal compliance?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do I handle a sudden influx of right-to-be-forgotten requests in our CRM while keeping our audit logs intact for legal compliance?
1 real search · 1 real-search pass
GDPR Article 17 right to erasure exceptions Article 12 response one month complex requests official text; ICO erasure requests keep records audit trail guidanceGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
GDPR Article 17 right to erasure exceptions Article 12 response one month complex requests official text; ICO erasure requests keep records audit trail guidance Google ↗
- Right to erasure · ico.org.uk
- The right to erasure and the right to restriction · ico.org.uk
- Dealing with requests from individuals · commission.europa.eu