E-commerce
July 1, 2026
"The bot promises that you no longer keep any data." "The AI disables my cookies without me understanding why." "Chatbot gives invented GDPR legal advice." Three failures where a miscalibrated privacy bot creates legal risk and distrust.
An e-commerce privacy preferences AI chatbot does not replace PRIVPREF agents (#849). It reads PRIVPREF-MAP, quotes obligatory_copy, guides settings_link, and executes handoff toggle admin to humans without promising zero data or executing API consents.
This guide #850 covers intents bot_privpref_*, flow PRIVPREFbot, and KPI privpref_bot. Companion bot of the PRIVPREF playbook (#849). AI use case: tier 1 privacy education with clear consequences.
Summary
Why automate privacy education with a bot?
"Where are my settings", "cut marketing", "cookies or emails" arrive account widget and footer CMP. A calibrated bot reads PRIVPREF-MAP, quotes obligatory_copy, without NO-ZERO-DATA violation.
What the bot solves tier 1 privacy
Guide menu: settings_copy account path map
Explain channels: channel_diff_copy emails cookies push map
Quote mandatory: obligatory_copy unchanged orders map
Toggle consequences: personalization_off_copy analytics_off_copy map
Handoff customer service: #849 payload privpref_* toggle admin
PRIVPREFbot vs PRIVPREF #849, TXNPREFbot #834, Privacy #154 and anti-hallucination #123
Seven contents, seven distinct customer privacy journeys.
Quick matrix
#850 PRIVPREFbot: tier 1 bot explain toggles consequences handoff
#849 PRIVPREF: agents toggle Klaviyo CMP PV-5 document
TXNPREFbot #834: transactional emails distinct privacy center account
Privacy #154: cross-cutting support data usage distinct toggles
ACCTDELbot #824: account deletion erasure distinct preferences
PUSHNOTIFbot #836: push distinct privacy account
Anti-hallucination #123: policy map whitelist not LLM legal advice
Pipeline: #850 bot explain tier 1 → #849 agents execute PV-5 toggle policy.
Which bot_privpref_* intents should be configured?
Eight bot privacy intents mapped to privpref_* typologies #849.
Eight bot_privpref intents
bot_privpref_settings: settings_copy guide menu map
bot_privpref_channel_diff: channel_diff_copy separate channels map
bot_privpref_obligatory: obligatory_copy cite map
bot_privpref_marketing_off: marketing_off_copy guide toggle map
bot_privpref_personalization: personalization_off_copy consequences map
bot_privpref_analytics: analytics_off_copy cookies map
bot_privpref_sync_delay: sync_delay_copy persists map
bot_privpref_handoff: toggle execute → PRIVPREF849-HANDOFF-BOT
Execute toggle listes CMP → human handoff PV-5 only. Bot explain guide only.
How do I use PRIVPREF-MAP #849?
The bot reads PRIVPREF-MAP #849 : privpref_program_id, settings_copy, channel_diff_copy, obligatory_copy, marketing_off_copy, analytics_off_copy, personalization_off_copy, sync_delay_copy, gdpr_route_copy, toggle_matrix_copy.
Privacy-sensitive Guardrails
PRIVPREF-MAP-GROUNDED-BOT : privacy response from map only
OBLIGATORY-CITE-BOT : obligatory_copy cites map verbatim
PRIVPREF-NO-ZERO-DATA-BOT : never promise zero data if active command
NO-LEGAL-ADVICE-BOT : no personalized GDPR interpretation by LLM
NO-TOGGLE-EXECUTE-BOT : do not modify API bot consents
PRIVPREF849-HANDOFF-BOT : toggle execute → #849 agents PV-5
PRIVPREFBOT-SUP policy in six rules
Six rules for responsible bot privacy.
PRIVPREF-MAP-GROUNDED-BOT: toggle consequences from map only
OBLIGATORY-CITE-BOT: mandatory explanation before marketing off
PRIVPREF-NO-ZERO-DATA-BOT: no zero data promised
NO-LEGAL-ADVICE-BOT: verbatim map is not LLM legal advice
CHANNEL-DIFF-FIRST-BOT: channel_diff if cookies_confused
NO-TOGGLE-EXECUTE-BOT: human consent toggle #849 only
Flow PRIVPREFbot PVB-1 to PVB-8
Flow eight steps bot privacy embed account CMP footer.
PVB-1 Classify: bot_privpref_* detect keyword privacy cookies marketing data
PVB-2 Intent check: settings vs marketing off vs analytics personalization
PVB-3 PRIVPREF-MAP: settings channel_diff obligatory marketing handoff
PVB-4 Explain: TPL-PRIVPREFbot-OBLIGATORY grounded first if marketing off
PVB-5 Guardrail: MAP-GROUNDED OBLIGATORY-CITE NO-ZERO NO-LEGAL NO-TOGGLE-EXEC
PVB-6 Respond: TPL-PRIVPREFbot max 3 sentences grounded
PVB-7 Handoff or close: #849 payload or close self-service OK
PVB-8 Log: intent obligatory_cited zero_data_blocked handoff Y/N
Example TPL-PRIVPREFbot-OBLIGATORY
"[obligatory_copy map.] Marketing only can be deactivated: [marketing_off_copy map.] SETTINGS: [settings_copy map.] OBLIGATORY-CITE-BOT."
Templates TPL-PRIVPREFbot and touchpoints
Four short privacy embed templates.
TPL-PRIVPREFbot-SETTINGS
[settings_copy map.] [channel_diff_copy map.] PRIVPREF-MAP-GROUNDED-BOT.
TPL-PRIVPREFbot-OBLIGATORY
[obligatory_copy map.] [toggle_matrix_copy map.] OBLIGATORY-CITE-BOT.
TPL-PRIVPREFbot-PERSONALIZATION
[personalization_off_copy map.] Controls unchanged. NO-ZERO-DATA-BOT.
TPL-PRIVPREFbot-SYNC
[sync_delay_copy map.] If promo persists 48 h: handoff #849.
Touchpoints
Account Privacy Page: bot_privpref_settings instant
Keyword stop promos: bot_privpref_obligatory followed by marketing_off
CMP banner click: bot_privpref_channel_diff proactive
Personalization keyword: bot_privpref_personalization trigger
Edge cases and reroutes
Five cases outside tier 1 bot privacy standard.
Transactional emails only: TXNPREFbot #834 reroute
Push marketing: PUSHNOTIFbot #836 distinct
Account deletion: ACCTDELbot #824 distinct preferences
privpref_gdpr_combo: gdpr_route_copy handoff DPO #849
General data usage: Privacy #154 distinct toggles
Essential privpref_bot KPIs
Five sensitive PRIVPREFbot steering metrics.
privpref_bot_clarity_deflect: closed resolved without agent repeat 7d
privpref_bot_obligatory_cite_rate: OBLIGATORY-CITE / bot_privpref marketing_off
privpref_bot_zero_data_violations: zero data promise target audit 0
privpref_bot_channel_diff_rate: % cookies_confused with CHANNEL-DIFF
privpref_bot_handoff_rate: escalate #849 / total privacy bot
Target: privpref_bot_zero_data_violations 0 and privpref_bot_obligatory_cite_rate higher than 95%.
PRIVPREFbot anti-patterns
Five common errors on bot privacy accounts.
Promising zero data: NO-ZERO-DATA obligatory first
Executing toggle consent API: NO-TOGGLE-EXECUTE handoff #849
GDPR legal advice: NO-LEGAL-ADVICE map only
Skip obligatory on marketing off: OBLIGATORY-CITE obligatory
Confusing email and cookies: CHANNEL-DIFF-FIRST before guide
PRIVPREFbot with Qstomy
Qstomy on Shopify : detect bot_privpref intent CMP account, PRIVPREF-MAP RAG grounded, NO-ZERO-DATA guardrail, handoff enriched #849 tier 2.
Pipeline : #850 bot explain tier 1 → #849 agents execute toggle PV-5.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist PRIVPREFbot (8 steps)
Sync PRIVPREF-MAP #849: RAG bot privacy embed CMP account
Policy PRIVPREFBOT-SUP: 6 OBLIGATORY-CITE NO-ZERO NO-LEGAL NO-TOGGLE-EXEC rules
8 intents bot_privpref_*: flow PVB-1 to PVB-8
4 templates TPL-PRIVPREFbot-*: SETTINGS OBLIGATORY PERSONALIZATION SYNC
Block consent API write: bot read-only toggles no CMP write
Red team 15 prompts: zero data promise toggle execute legal advice
Proactive privacy page: bot_privpref_settings trigger embed
Dashboard KPI: privpref_bot_* section 9 zero_data_violations obligatory_cite
FAQ
Difference #849?
#849 = Klaviyo CMP PV-5 toggle agents. #850 = bot explain guide tier 1.
Does the bot modify consents?
No. NO-TOGGLE-EXECUTE-BOT. PRIVPREF849-HANDOFF human PV-5.
Client wants to turn everything off?
bot_privpref_obligatory TPL-PRIVPREFbot-OBLIGATORY then marketing_off guide.
Does personalization off block orders?
bot_privpref_personalization TPL-PRIVPREFbot-PERSONALIZATION. Orders unchanged.
Going further
This week: deploy PRIVPREF-MAP RAG account embed, red team zero_data_violations audit, sync bot_privpref_obligatory proactive scenario marketing off explain test.
Enzo
July 1, 2026
