GDPR: Delete a Chatbot Conversation After a Customer Request

A customer asks you to delete a chatbot conversation about a missing parcel. The thread is in your inbox, but an agent received an email notification, pasted a quote into a support note and viewed the customer’s order beside the chat. Deleting the thread alone would leave work unfinished; deleting the order without assessing why it is kept could create a different problem. Use a record-by-record inventory to decide what to erase, what needs review and what remains for a documented reason.

Start with the request, not the delete button

Record the customer’s wording and the date it arrived. Acknowledge the request without promising that every record connected to the order will disappear. If your team has a privacy-request owner, assign the case to them so the search and response are tracked in one place.

Before disclosing a transcript or changing records, check whether you have reasonable grounds to doubt the requester’s identity. A familiar email address can help locate a chat, but it is not proof by itself: a forwarded message or compromised mailbox can complicate matters. If there is a mismatch, use a proportionate check through a channel already associated with the customer; do not ask for an identity document by default. If someone claims to act for another person, refer the case to your privacy-request owner to check their authority. Log the check without collecting more identity material than needed.

Erasure is a different task from telling shoppers they are speaking to AI. See our guide to EU AI Act chatbot disclosure for that separate question. A disclosure notice does not locate or erase a conversation.

Map where the conversation and its copies went

Start with the approximate date, contact details and a distinctive phrase such as “missing parcel.” Search the inbox, then follow where the information went. Inspect agent notes and tags, emailed notifications or forwarded transcripts, connected support records, downloads and exports, and material written from the chat. If you need a fuller search method, use finding chat data for a GDPR access request as a companion workflow.

In askVela, the agent inbox includes tags and internal notes, and email notifications are available. Resolved chats can also be turned into help articles. Those are prompts to inspect the relevant records, not evidence that an inbox deletion reaches every destination. Likewise, order and customer context beside the chat does not make the underlying shop order part of the transcript. Identify which system holds each record before acting.

Do not mark an unfound chat as deleted. Write down the identifiers used, the systems searched and who can broaden the search. If an agent forwarded a notification to a shared mailbox, give that mailbox its own row rather than recording only “email checked.”

Choose deletion, redaction, restriction or justified retention

Decide separately for the transcript, each copy, each extract and the order record. Ask why the record is still held and whether the shop can establish a reason to keep it. A routine schedule can guide your search, but it does not settle an individual request; see setting a live-chat transcript retention period. Refer uncertain legal or retention decisions to whoever handles privacy decisions for your shop.

Record and condition	Action to assess	Record in the case file
Transcript and notes: no established reason to keep them	Erase from active systems; trace copies separately.	Record reference, owner, locations and completion evidence.
Help draft: useful general answer mixed with a name, order number or chat quote	Remove the identifying extract. Keep general guidance only if it is needed and cannot reasonably identify the customer, including by combining it with other available information.	What changed, why the remainder is kept and where it appears.
Retention claim or identity is unresolved	Limit access while the responsible person reviews it; make the final decision and follow through. Restriction is not completed erasure.	Reason for the interim step, access limit, reviewer and next action.
Separate order or invoice with an applicable reason to retain it	Keep only the record justified by that reason; assess chat copies of its details separately.	Reason, applicable retention rule, system and access limits.
Notification, export or pasted transcript with no separate reason to keep it	Erase the copy; do not rely on deletion of the original.	Each destination, owner and outcome.

Redaction is not a shortcut where the remaining text still identifies the shopper through an order number, unusual circumstances or a link to another record. Nor does erasing a chat automatically require erasing an invoice. If the reason for keeping any item is unclear, leave the decision open for review rather than calling the item exempt.

Carry out deletion across active systems

Assign one person to perform and verify each inventory action. Give them a record reference and destination, not an instruction to “clean up customer data.” When reviewing access and settings, askVela’s security and privacy controls may be relevant; do not treat those controls as an automated erasure workflow.

A delete control in one system is not proof that mailboxes, exported files or connected records changed. If the assigned owner cannot inspect a destination, keep its row open until someone with access reports back. Save action references and results rather than pasting the sensitive transcript into your audit log.

Handle backups and retained order data honestly

For every affected provider, ask what its backups contain, whether an individual record can be removed, who can access a backup and what happens on restoration. If an existing backup cannot be edited, record that limit and the procedure for addressing the conversation if it is restored. Confirm whether backup copies are isolated from ordinary support use before saying so to the customer; do not claim they have been cleared without evidence.

Keep an order or invoice under the shop’s order-record process if you establish an applicable reason to retain it. Record that reason, the rule used to determine when the record is removed and who can access it. An agent’s copied order number inside a support note is a different record and needs a separate decision. Before you respond, sort the inventory into completed actions, documented retained records, restricted records awaiting a decision and outstanding provider actions.

Reply to the customer and close the audit trail

Use only statements you have verified. If work remains open, describe the outstanding action rather than saying the request is complete. Remove any bracketed paragraph that does not apply.

Close the internal case with the request, identity-check outcome, search terms and locations, decisions for each record, owners, completion evidence and open follow-ups. That audit trail should show what happened without keeping a duplicate of the chat just to prove it was deleted.