How should our preference center handle GDPR compliance for automated lead nurturing streams when a user requests partial data deletion versus a total opt-out?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How should our preference center handle GDPR compliance for automated lead nurturing streams when a user requests partial data deletion versus a total opt-out?
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.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
GDPR official text Articles 7 17 21 12 erasure objection direct marketing consent withdrawal Google ↗
EDPB guidelines right to erasure direct marketing objection GDPR Article 21 official Google ↗
- Respect people's preferences · ico.org.uk
- How should we obtain, record and manage consent? · ico.org.uk
- Regulation - 2016/679 - EN - gdpr · eur-lex.europa.eu
- Dealing with requests from individuals · commission.europa.eu
- One-Stop-Shop thematic case digest: Right to Object and Right to Erasure · edpb.europa.eu
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
GDPR official text Articles 7 17 21 12 erasure objection direct marketing consent withdrawal OBSERVED | Google ↗ AI Mode ↗ | — | Consequence | — | — | 1x of 1 | |
EDPB guidelines right to erasure direct marketing objection GDPR Article 21 official OBSERVED | Google ↗ AI Mode ↗ | — | Other / navigational | — | — | 1x of 1 |