Handling Shopify Customer Data and Erasure Requests for Your Chat App
When a customer asks for their data or for it to be erased, Shopify passes the request to the apps on your store. Here's what Milly Chat does with each kind: where the request shows up, what the data report contains, what erasure deletes, and what neither covers.
A customer emails you asking what you hold on them, or asking you to delete it. You handle that in Shopify, and Shopify passes the request on to the apps installed on your store. A chat app is one of the places that customer may have left something: an email for a discount code, a phone number for a call back, a conversation about their order.
This post walks through what Milly Chat does with each kind of request, where you see it, and what it does not cover. The Privacy Requests page shipped on October 29, 2026. This post describes the product. It isn't legal advice: what you owe a customer, and whether a request has been fully handled, are yours to confirm with your own privacy policy and advisers.
What Shopify sends
Shopify sends apps two kinds of customer privacy request, as described in its privacy compliance documentation:
- A data request, when a customer asks for the data you hold on them.
- An erasure request, when a customer's data is to be deleted on their behalf.
Each one names the customer by their email, their phone number and their Shopify customer record, and can list orders. Milly Chat records each request it receives for your store and processes it automatically.
The Privacy Requests page
Privacy Requests sits in your dashboard's sidebar, next to Leads. The requests Shopify forwards for your store are listed there with:
- when it was received;
- whether it's a data request or an erasure;
- a masked reference to the customer, enough to recognise them without putting their full address on screen;
- Shopify's 30-day response date;
- its status: processing, the number of records found for a data request, or what was erased.
If processing fails, for example because a service was briefly unavailable, the status says so and Milly Chat retries the request. You don't need to resubmit anything.
Data requests: download the report
For a data request, click Download report. The report is built from our database at the moment you click, and we don't keep a copy of it. It downloads as a JSON file and contains:
- the request itself: when it arrived and Shopify's 30-day response date;
- the leads the customer left in the chat, including any phone number and the disclosure that was configured when it was taken;
- the chat conversations in our database matched to them, in full, each marked with how it was matched;
- notes on what the report doesn't cover, and what was left out and why.
You then provide the report to the customer. Because it is rebuilt from the customer details the request carried, it can be downloaded until 45 days after the request arrived. After that, those details are deleted from the request, and the page tells you the report can't be built.
Erasure requests
Erasure requests are processed automatically. Milly Chat deletes, from our database:
- the customer's matching lead captures;
- the chat conversations matched to them, and the records our database links to those conversations, including any correction you wrote against one of their replies.
Once the erasure is processed, the customer's details are cleared from the request record as well, and the status shows how many conversations and how many leads were erased. The database deletion runs as a single transaction: if it fails part-way, it is rolled back and the request is retried.
One thing to expect: if a corrected reply belonged to an erased conversation, that correction goes too. A correction stores a copy of the shopper's question and the assistant's answer, so keeping it would keep part of the conversation.
Erasure covers our database only. The next two sections say how records are matched and what is outside it.
How a customer's records are found
Lead captures are found by email, and by phone number when the shopper left a number and no email. Phone numbers are compared in a normalized form, so "(555) 010-0142" and "+1 555 010 0142" are treated as the same number.
Conversations don't carry an email of their own, so they're found three ways:
- Through a lead. The conversation a matched lead came from.
- Through an order. When Shopify names orders, the conversations from the browser that placed them, using the same link between orders and chats that revenue attribution uses.
- Through their email in the chat. Conversations where the shopper typed their own email address. Only the shopper's messages are read for this, not the assistant's, because the assistant often quotes your support address.
Two rules are there to keep one customer's request from reaching someone else's data. A browser can be shared, so a conversation reached only through an order, in which the shopper typed a different email, is left out. And a lead that matches by phone but carries someone else's email, a shared landline or a mistyped number, is left out too. Either way it is neither handed over nor deleted, and the report counts how many were skipped.
What erasure and the report don't cover
Both reach what Milly Chat holds in our database. They don't reach:
- Copies already sent to your connected tools. A lead sent to Klaviyo, to your CRM or help desk, or to your lead webhook, and any CSV you exported, is a copy held outside Milly Chat. Erasure doesn't touch it and the report doesn't include it. Handling the request in those tools is yours to do.
- Archived copies of expired conversations. On plans with a conversation retention period, conversations past it are moved out of the live database into a private archive. They are not in the report, and the deletion described above does not reach them.
- Phone numbers typed inside a chat message. These are not searched. Shoppers write numbers in many formats, and a search loose enough to catch them would also match order numbers, prices and SKUs. A phone number finds a conversation only through a lead that recorded it.
Each report ends with notes on the archive and on phone numbers in message text, so whoever reads it can see where it stops. Whether that is enough for a particular customer is yours to confirm.
If you want help with a specific request, email [email protected].
Frequently Asked Questions
What happens in Milly Chat when Shopify sends a customer erasure request?
It's processed automatically. Milly Chat deletes the customer's matching lead captures and the chat conversations matched to them in our database, along with the records our database links to those conversations. Copies already sent to your connected tools, and archived copies of expired conversations, are not covered. The Privacy Requests page shows how many conversations and leads were erased.
How do I answer a customer data request for Milly Chat?
Open Privacy Requests in your dashboard and download the report for that request. It's built from our database at the moment you download it, and no copy is kept. You then provide it to the customer. The page shows Shopify's 30-day response date for each request.
Does the report include all of a customer's conversations?
It includes the conversations in our database that can be tied to the customer: through a lead they left, through the orders Shopify names in the request, or through their email typed in the chat. It does not include archived copies of expired conversations, which are held in a private archive, and phone numbers typed inside a message are not searched. The report lists both of these limits itself.