How do I set up a right to be forgotten workflow in our CRM to satisfy strict GDPR deletion requests?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do I set up a right to be forgotten workflow in our CRM to satisfy strict GDPR deletion requests?
2 real searches · 1 real-search pass
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 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
European Commission GDPR Article 17 right to erasure Article 12 response one month Article 19 recipients official text Google ↗
ICO right to erasure guidance exceptions backups processors third parties GDPR Google ↗
- Regulation - 2016/679 - EN - gdpr · eur-lex.europa.eu
- Dealing with requests from individuals · commission.europa.eu
- The right to erasure (Articles 17 & 19 of the GDPR) · dataprotection.ie
- Right to erasure · ico.org.uk
- Right to erasure · ico.org.uk
- Right to erasure · ico.org.uk
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
European Commission GDPR Article 17 right to erasure Article 12 response one month Article 19 recipients official text OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
ICO right to erasure guidance exceptions backups processors third parties GDPR OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |