Customer erasure in 5 days: what the WhatsApp log keeps

Shopify now processes customer erasure requests after 5 days instead of 10. What Beacon Messenger blanks, what it removes from the queue, and what stays.

On 11 November 2026 Shopify's developer changelog recorded a quiet change to how customer erasure requests are handled. As of 10 November, a request to erase a customer's personal data is no longer held in a pending state for ten days. It is processed five days after it was submitted, regardless of when the customer last placed an order. The one exception is a customer who is the recipient of a gift card scheduled to send: their request stays pending until the gift card has been delivered.

For a store that sends WhatsApp order messages, the interesting part is not the five days. It is what happens at the end of them, when Shopify tells every installed app that this person must be forgotten, and what a messaging app does with a log full of phone numbers. This post walks through the sequence for Beacon Messenger: the request, the webhook, what is blanked, what is removed from the send queue, and what stays so that your delivery counts and your audit trail still make sense.

The request, and who starts it

An erasure request begins in one of two places. A customer asks you, by email or through the privacy page in their account, to delete their data, and you open the customer in your Shopify admin and request the erasure from there. Or you decide to do it yourself for a customer who asked over the phone. Either way the request lands with Shopify, which owns the customer record, and Shopify decides when to act. Until this week that meant a ten-day hold, which gave open orders time to settle and gave you a window to cancel the request. The hold is now five days.

When the five days are up, Shopify erases what it holds and sends a customers/redact webhook to every app installed on the store, as described on its privacy law compliance page. The webhook carries the customer's identifier, the phone and email Shopify had on file, and the IDs of the orders to redact. Each app is expected to do its part of the erasure from that. There is also a companion webhook, customers/data_request, which arrives when a customer asks for a copy of their data, and a third, shop/redact, that arrives 48 hours after a store uninstalls the app. Beacon Messenger handles all three, and the access log post describes how each one is recorded.

What Beacon Messenger holds about a customer

Very little, by design, and all of it in one table. Every WhatsApp message the app sent, tried to send, or decided not to send is a row in the message log. The row holds the recipient phone number, the customer's name if an order or checkout carried one, the order number and ID or checkout token, the template name and the merge values that filled it, the delivery status, any reply the customer sent to a cash on delivery confirmation, and a snapshot of the context the message was built from, kept so a failed message can be retried later. There are no customer profiles, no address book, no copies of chat history. The security review post goes through the permissions behind that.

Two kinds of record are worth separating. Rows in the message log are history: messages that have already been sent, delivered, failed or skipped. Messages that are still waiting, such as an abandoned checkout reminder sitting out its delay or a cash on delivery confirmation on a timer, are not in the log yet. They live in the scheduler, each with the phone number and order it was built for, until the moment they send.

What the redact webhook does, row by row

When customers/redact arrives, Beacon Messenger looks for the person in both places. It matches on two things: the order IDs Shopify lists in the webhook, and the customer's phone number as digits, because a checkout reminder has no order ID and the phone is the only link. Then:

  • Anything waiting in the scheduler for that phone number or those orders is deleted. A queued message to a customer who asked to be forgotten is not sent, however much of its delay has already elapsed, and nothing is written to the log for it.
  • On every message row that matched, the phone number is blanked, the name is removed, the merge values that filled the template are emptied, any reply the customer sent is removed, and the stored context snapshot is cleared.
  • The row itself is kept: trigger, template name, order number, status, timestamps and error codes stay exactly as they were.

The last point is deliberate. Redaction removes the person from the record; it does not pretend the message never happened. Your dashboard's sent, delivered, failed and skipped counts for the month are unchanged, your Meta invoice still reconciles against the same number of rows, and a row that failed with a template error still shows the error. What you can no longer see is who it went to.

A message row before and after customers/redact
FieldBeforeAfter
RecipientPhone number in digitsEmpty
Customer nameFrom the order or checkoutRemoved
Merge valuesName, order total, tracking number and so onEmptied
Replyyes or no from a COD confirmationRemoved
Stored context for retryFull snapshotCleared; the row cannot be retried
Status, trigger, template, order number, timestampsAs recordedUnchanged

Clearing the stored context matters for one button. The Messages log has Retry on failed and skipped rows, and Retry works from that snapshot. After redaction there is no snapshot, so Retry on one of those rows does nothing, by design. A message to a redacted customer must not be reconstructable from the app's own records. The log search post describes Retry on ordinary rows.

Five days and a seven-day delay

The shorter hold interacts with one Beacon Messenger setting in a way worth thinking through. The abandoned checkout reminder can be delayed anything from ten minutes to seven days after the last change to the checkout, as the delay post explains. Under the old ten-day hold, a reminder on any delay would have fired before Shopify processed an erasure requested the same day. Under the five-day hold, a reminder set to six or seven days is still in the queue when the redact webhook arrives, and the behaviour above is what removes it. If you run long reminder delays, the practical effect of Shopify's change is that a shopper who abandons a cart and immediately asks to be forgotten will now not receive the reminder, where before they would have. That is the right outcome and it needs no setting.

Order messages are not affected in the same way. An order confirmation goes out within seconds of the order, a shipping update within seconds of the fulfilment, and both are long sent by the time any erasure is processed. Those rows are redacted as history: the message was delivered, the record of it stays, the phone number does not.

What the data request webhook does

customers/data_request is the other half, and it is less dramatic. Shopify expects the merchant to give the customer their data; the app's job is to make that possible. When the webhook arrives, Beacon Messenger counts the message rows that match the orders and phone number in it and writes an audit entry with the count. It does not send anything to the customer and does not export anything on its own. If a customer asks you for everything you hold, the Messages log filtered by their phone number or order number is the answer for this app, and the audit entry proves when the request was received and how many rows were in scope at the time.

What stays with Meta

One thing no Shopify app can erase is the message as delivered. A WhatsApp message that reached the customer's phone is on their phone, and Meta holds whatever its own retention rules say about messages sent through the Cloud API. Beacon Messenger never held the rendered message text in the first place, only the template name and the values, and after redaction it holds the template name alone. If a customer's request extends to WhatsApp itself, that conversation is between them and Meta, and the message on their handset is theirs to delete.

Checking that it happened

Every compliance webhook writes a row to the app's audit log with the actor shopify, the number of message rows redacted and the number of queued messages removed. If a customer, or a regulator, asks whether their erasure request reached your messaging app, that row with its timestamp is the evidence, and the redacted message rows, with empty recipients and the original send times, are the corroboration. The audit log is kept for the same 365 days as the message log and is available on request from support.

The change Shopify made this week is a small one for merchants and invisible to customers. Where it shows is in the gap between a request and its effect, now five days, and in what every connected app does when the webhook lands. For WhatsApp notifications the answer should be: nothing queued goes out, nothing identifying stays, and nothing about your counts changes. That is what Beacon Messenger does. See plans.

Questions

How long after a customer asks to be forgotten does Shopify tell apps to delete their data?

Five days after the request was submitted, as of 10 November 2026. Before that date Shopify held requests for ten days. The exception is a customer due to receive a scheduled gift card, whose request stays pending until the gift card has been delivered. When the hold ends, Shopify sends the customers/redact webhook to every installed app.

Does Beacon Messenger delete the whole message history for a redacted customer?

No. It blanks the phone number, name, merge values, any reply and the stored retry context, and it removes anything still queued for that person, but it keeps the row with its trigger, template, order number, status and timestamps. Delivery counts and the Meta invoice reconciliation stay accurate; the person is no longer identifiable from them.

Will a queued abandoned checkout reminder still send after an erasure?

No. When the redact webhook arrives, any scheduled message for that customer's phone number or orders is deleted before it can send, and the audit entry records how many were removed. With the new five-day hold this can happen while a six or seven day reminder is still waiting, which is exactly the case the removal is for.

Can I retry a failed message after the customer was redacted?

No. Retry rebuilds the message from the context snapshot stored with the row, and redaction clears that snapshot. The Retry button on a redacted row does nothing. This is intentional: a message to someone who asked to be forgotten should not be reconstructable from the app's records.

More guides