E-commerce
July 1, 2026
"The bot deleted my account without confirmation." "AI promises total erasure of orders." "Chatbot gives invented GDPR legal advice." Three failures where a poorly calibrated deletion bot creates CNIL risk and loss of trust.
An e-commerce account deletion AI chatbot does not replace ACCTDEL agents (#823). It reads ACCTDEL-MAP, cites scope_copy ack_copy, collects identity verification and hands off delete to humans without ever executing admin deletion or promising illegal erasure.
This guide #824 covers intents bot_acctdel_*, flow ACCTDELbot and KPI acctdel_bot. Bot pair of the playbook ACCTDEL (#823). Sensitive AI use case: inform verify escalate tier 1.
Summary
Why automate the account deletion information using a bot?
"Delete my account", "GDPR", "erase my data" arrive via account widget or contact form. A calibrated bot reads ACCTDEL-MAP, quotes scope_copy sla_copy, collects email order_ref and hands off human ticket without NO-AUTO-DELETE.
What the bot resolves tier 1 deletion
Explain scope: scope_copy ACCTDEL-SCOPE-CITE-BOT map
Acknowledge request: ack_copy sla_copy map delay
Reassure about orders: order_kept_copy legal obligation map
Marketing only: unsub_only_copy alternative delete map
Handoff support: #823 payload acctdel_* identity collected
The CNIL points out transparency and deadlines on erasure requests; a grounded bot reduces poorly informed tickets (CNIL, erasure 2026).
ACCTDELbot vs ACCTDEL #823, privacy #154, GDPR CGVbot, unsubscribe and anti-hallucination #123
Six contents, six distinct customer data journeys.
Quick Matrix
#824 ACCTDELbot: tier 1 bot inform scope collect escalate delete
#823 ACCTDEL: agents execute delete GDPR legal registry
Privacy #154: transversal support privacy distinct account deletion
CGVbot terms: legal T&C distinct account erasure request
Anti-hallucination #123: policy map whitelist not legal advice LLM
Pipeline: #824 bot inform collect tier 1 → #823 agents execute AD-5 delete policy.
Which bot_acctdel_* intents should be configured?
Eight bot intents suppression mapped to acctdel_* typologies #823.
Eight bot_acctdel intents
bot_acctdel_scope: scope_copy deleted kept ACCTDEL-SCOPE-CITE-BOT
bot_acctdel_request: ack_copy collect identity handoff map
bot_acctdel_order_kept: order_kept_copy legal obligation map
bot_acctdel_delay: sla_copy processing_delay map
bot_acctdel_marketing: marketing_still_copy unsub_link map
bot_acctdel_undo: undo_copy no restore map
bot_acctdel_shop_pay: shop_pay_copy wallet distinct map
bot_acctdel_handoff: fraud legal → ACCTDEL823-HANDOFF-BOT
Tier 1 auto: scope order_kept delay marketing if ACCTDEL-MAP grounded.
Delete request confirmed → bot_acctdel_request human handoff AD-2 identity N2.
Bot never executes delete: NO-AUTO-DELETE-BOT strict.
How should I consume ACCTDEL-MAP #823?
The bot reads ACCTDEL-MAP #823: acctdel_program_id, scope_copy, ack_copy, sla_copy, order_kept_copy, marketing_still_copy, undo_copy, shop_pay_copy, unsub_only_copy, confirm_intent_copy, legal_escalate_copy.
Sensitive deletion guardrails
ACCTDEL-SCOPE-CITE-BOT: scope deleted kept cite map verbatim
NO-AUTO-DELETE-BOT: bot never deletes customer admin
NO-LEGAL-ADVICE-BOT: no custom GDPR interpretation by LLM
SCOPE-BEFORE-CONFIRM-BOT: scope mandatory before delete handoff
IDENTITY-COLLECT-BOT: email order_ref CP before request handoff
PRIVACY154-REROUTE-BOT: general privacy question → #154 distinct delete
ACCTDEL823-HANDOFF-BOT: execute delete → #823 agents AD-5
Alignment anti-hallucination (#123) and CGVbot (#terms): no legal advice, map only.
ACCTDELBOT-SUP policy in six rules
Six bot rules for GDPR-compliant deletion.
ACCTDEL-MAP-GROUNDED-BOT: deletion response from map only
ACCTDEL-SCOPE-CITE-BOT: scope deleted kept cite map
NO-AUTO-DELETE-BOT: human admin delete only
NO-LEGAL-ADVICE-BOT: no LLM law interpretation
SCOPE-BEFORE-CONFIRM-BOT: scope before handoff request
IDENTITY-COLLECT-BOT: N2 collect verification before handoff execute
Flow ACCTDELbot ADB-1 to ADB-8
Eight-step flow bot account deletion embed widget sensitive.
ADB-1 Classify: bot_acctdel_* detect keyword delete GDPR erase account
ADB-2 Intent check: delete full vs info scope vs marketing only
ADB-3 ACCTDEL-MAP: scope ack order_kept delay marketing handoff reroute
ADB-4 Scope respond: TPL-ACCTDELbot-SCOPE grounded max 3 sentences
ADB-5 Confirm or collect: if delete confirmed collect email order_ref postal_code
ADB-6 Guardrail: SCOPE-CITE NO-DELETE NO-LEGAL SCOPE-BEFORE IDENTITY HANDOFF
ADB-7 Handoff ticket: ACCTDEL823 payload identity tag acctdel_request_full
ADB-8 Log: intent acctdel_program_id scope_cited handoff Y/N delete_attempt blocked
Example TPL-ACCTDELbot-SCOPE
"[scope_copy map.] Keep orders: [order_kept_copy map.] Processing time: [sla_copy map.] To confirm deletion, reply after reading. ACCTDEL-SCOPE-CITE-BOT."
TPL-ACCTDELbot templates and touchpoints
Four short templates requesting deletion embed.
TPL-ACCTDELbot-SCOPE
[scope_copy map.] [order_kept_copy map.] ACCTDEL-SCOPE-CITE-BOT.
TPL-ACCTDELbot-ACK
[ack_copy map.] Reference: [ticket_id.] Delay: [sla_copy map.] IDENTITY-COLLECT-BOT.
TPL-ACCTDELbot-MARKETING
[marketing_still_copy map.] Unsubscribe: [unsub_link map.] Alternative to full delete.
TPL-ACCTDELbot-UNDO
[undo_copy map.] No automatic restoration history. NO-AUTO-DELETE-BOT.
Account touchpoints
Account settings delete link: bot_acctdel_scope proactive before form
Keyword GDPR: bot_acctdel_scope instant
Keyword orders disappear: bot_acctdel_order_kept trigger
Emails after delete: bot_acctdel_marketing delay sync map
No admin delete embed: ACCTDEL823-HANDOFF-BOT agents #823 only.
Edge cases and reroutes
Five cases outside tier 1 standard bot deletion.
acctdel_fraud_or_minor: ACCTDEL823-HANDOFF-BOT immediate legal
Joint third-party request: handoff identity N3 not bot collect only
Active CNIL complaint threat litigation: legal_escalate_copy handoff DPO
Unsubscribe only desired: unsub_only_copy PRIVACY154 reroute marketing
Email change not delete: #825 email change distinct from deletion
Tier 1 SCOPE rule then collect or handoff. Execute delete → human #823 only.
Essential acctdel_bot KPIs
Five sensitive ACCTDELbot management metrics.
acctdel_bot_inform_deflect : closed informed without agent repeat 30d
acctdel_bot_scope_cite_rate : ACCTDEL-SCOPE-CITE-BOT / bot_acctdel scope request
acctdel_bot_auto_delete_violations : delete executed bot audit target 0
acctdel_bot_legal_advice_violations : legal advice LLM audit target 0
acctdel_bot_handoff_rate : escalate #823 / total delete request bot
Target : acctdel_bot_auto_delete_violations 0 and acctdel_bot_scope_cite_rate greater than 95%.
ACCTDELbot anti-patterns
Five common bot account deletion errors.
Delete account as bot: NO-AUTO-DELETE-BOT handoff #823 only
Promise order deletion: order_kept_copy map legal obligation only
GDPR legal advice: NO-LEGAL-ADVICE-BOT scope map verbatim
Handoff without scope: SCOPE-BEFORE-CONFIRM-BOT mandatory
Handoff without identity: IDENTITY-COLLECT-BOT email order_ref before ticket
ACCTDELbot with Qstomy
Qstomy on Shopify: detect sensitive bot_acctdel intent, ACCTDEL-MAP RAG grounded, NO-AUTO-DELETE guardrail, enriched handoff #823 tier 2 with identity payload.
Pipeline: #824 bot inform collect tier 1 → #823 agents execute delete registry policy.
Explore AI support and request a demo.
Checklist, FAQ and going further
ACCTDELbot Checklist (8 steps)
Sync ACCTDEL-MAP #823: RAG bot account deletion embed
Policy ACCTDELBOT-SUP: 6 rules SCOPE-CITE NO-DELETE NO-LEGAL SCOPE-BEFORE IDENTITY
8 intents bot_acctdel_*: flow ADB-1 to ADB-8
4 templates TPL-ACCTDELbot-*: SCOPE ACK MARKETING UNDO
Block delete API: bot role read-only customer no delete permission
Red team 15 prompts: delete now legal advice total erase without scope
Account settings proactive: bot_acctdel_scope before delete form
Dashboard KPI: acctdel_bot_* section 9 auto_delete_violations scope_cite handoff
FAQ
Difference #823?
#823 = agents execute delete legal registry. #824 = bot inform collect escalate tier 1.
Can the bot delete the account?
No. NO-AUTO-DELETE-BOT. ACCTDEL823-HANDOFF-BOT humans AD-5 only.
Customer demands deletion of orders?
bot_acctdel_order_kept order_kept_copy map. No LLM template promise contrary to obligation.
Marketing emails only?
TPL-ACCTDELbot-MARKETING unsub_only_copy alternative to full delete.
Go further
This week: deploy ACCTDEL-MAP RAG account embed, red team auto_delete_violations audit, sync bot_acctdel_scope proactive GDPR scenario scope cite test.
Enzo
July 1, 2026
