Our store chat used to tell shoppers that a data deletion "completes within 30 days." It sounded responsible. There was no tool behind it: the only thing that could erase a shopper was Shopify's own customer-redact webhook, which a shopper can't trigger from a chat.
We have one rule above the rest: no claim without a mechanism. So the promise got one:
The shopper asks. A pending request is written, nothing is deleted yet, and the reply says so.
Only an email this chat has proved (a 6-digit code, or a verified order) can ask. Otherwise anyone could make a store email a stranger.
A signed link, valid once and for 24 hours, opens a page with a button. Only the button deletes, so a corporate link scanner can't erase anyone.
The deletion runs the same function as Shopify's customer-redact webhook. One definition of "erased" in the whole app.
If it fails, it retries once a day, up to 7 times. If it still fails, the merchant is told, with the request ID, inside the 30 days.
What I took from it: read your system prompt as a list of promises, and name the function that keeps each one. If none exists, remove the promise or build the function.
The other walls behind our Shopify agent, with the code, in the X Article: https://x.com/con_golias/status/2121352219635159234
