Who looked at your customers' phone numbers? The access log behind a WhatsApp app
Every open, search and retry in Beacon Messenger's message log writes an audit row: which Shopify staff account, what filters, when. What is recorded, for how long, and why Shopify asks for it.
A WhatsApp notifications app is, underneath, a list of phone numbers with names and order details attached. The message log that lets you check whether a shipping update went out is also a page where any staff member with access to the app can read every customer's number, name and the contents of what was sent. Most apps treat that page as a utility and leave it at that. Beacon Messenger treats it as access to personal data, which means every visit to it leaves a record. This post explains what that record contains, who can see it, how long it lives, and what it does and does not protect you from.
What counts as access
The Messages page in the app lists one row per message: the recipient's phone number, the customer's name, the order it relates to, the template, the status, the merge-field values that were filled in, and any reply the customer sent. Those are the fields Shopify classifies as protected customer data, the name and phone number in particular, and Shopify's protected customer data requirements ask apps that handle them to limit who inside the app can reach them and to keep records of that access. Reading the page is access. So is narrowing it with a filter, searching for a specific customer, paging to older rows, and retrying a failed message, because a retry reads the stored phone number and order context again.
Each of those actions writes a row to a separate audit table. The row carries the store, the actor, the action, a small bag of details, and a timestamp. The actor is derived from the Shopify session token the embedded app receives on every request: the token's subject is the Shopify staff account that opened the admin, so the actor reads as user: followed by that staff id. If a request arrives without a usable subject, which should not happen in the embedded admin but is handled anyway, the actor is recorded as user:unknown rather than dropped.
| Action | Written when | Actor | Details stored |
|---|---|---|---|
| message_log.view | The Messages page is opened, filtered, searched or paged | Shopify staff account | Status filter, trigger filter, search term, page number, number of rows shown |
| message.retry | A failed message is resent from the log | Shopify staff account | The message id |
| customer.data_request | Shopify sends a customers/data_request webhook | shopify | Customer id, how many orders were named, how many log rows matched |
| customer.redact | Shopify sends a customers/redact webhook | shopify | Customer id and how many rows were scrubbed |
| shop.redact | Shopify sends a shop/redact webhook after uninstall | shopify | Store only |
Notice what is not in the details column. The audit row does not copy the phone numbers or names that were displayed. It records that someone searched the log for a term, which is enough to reconstruct what they saw when combined with the message rows themselves, without duplicating the personal data into a second table that would then need its own protection and its own deletion.
Why the compliance webhooks are in the same table
Shopify sends three mandatory webhooks to every app. When a customer asks a merchant for their data, customers/data_request arrives; when a customer asks to be forgotten, customers/redact arrives, five days after the request since 10 November 2026 (ten before that); when a store uninstalls, shop/redact arrives 48 hours later. Beacon Messenger handles each of them and logs the handling with the actor shopify, next to the staff access rows. The reason is practical: a data subject request from a customer is answered partly from this table. If a customer asks who has looked at their information, the message_log.view rows whose search term matched them, plus the redact row showing when their rows were scrubbed, are the answer.
Redaction itself is worth describing because it is less drastic than deletion. When customers/redact arrives, the app finds the message rows for that customer and blanks the recipient number, removes the name, empties the stored merge-field values and removes any reply, but keeps the row with its status and timestamp. The delivery counts you rely on to verify that notifications are going out stay accurate; the person is gone from them.
How long the trail lasts
Audit rows and message rows share one retention period: 365 days by default, configurable per deployment through an environment variable. A scheduled job runs every few hours and deletes both kinds of row older than that. Twelve months is the period stated in the app's privacy policy and on its security page, and it was chosen to be long enough that a complaint about a message sent last autumn can still be investigated, and short enough that the app is not sitting on years of phone numbers it no longer needs.
Two properties of the audit write matter more than the retention number. First, it is scoped by store at the database level, like everything else in the app: the Messages query filters by the authenticated shop, so a staff member of one store cannot read, or appear in the audit log of, another store, whatever they put in the URL. Second, the audit write is designed never to break the page that triggered it. If the database refuses the insert, the failure is logged on the server and the request proceeds. The alternative, refusing to show the log when the audit insert fails, sounds stricter but in practice means a transient database error turns into a merchant who cannot see why a message failed. The server-side error is the signal that something needs fixing; the merchant's page is not the place to surface it.
What the log is for, and what it is not
There is no page in the app that displays the audit table. That is deliberate for now. The log exists to answer questions after the fact: a customer asks why they received a message a second time, a merchant wants to know whether an ex-employee looked up a particular customer before leaving, Shopify asks during a review how access to protected data is controlled. In each case the answer is a query by store, time range and actor, and support can run it on request. Showing it to every staff member in the admin would itself be a disclosure of who did what, and a merchant who wants that should decide to ask for it.
What the log cannot do is stop access. It is a record, not a gate. Whether a staff member can open the app at all is decided in Shopify's staff permissions, under Settings > Users, where apps are granted per account. A store that gives every staff account access to every app has, in effect, decided that every staff account may read the message log, and the audit trail will faithfully record that they did. Pair the two: restrict who holds app access, so that the actors in the log are a short list of people you would recognise.
- In the Shopify admin, open Settings > Users and review which staff accounts can access Beacon Messenger. Remove it from accounts that do not handle customer messaging.
- Decide who owns data subject requests from customers. Shopify routes them to the store owner by email; the owner should know that the app's log is one of the places to check.
- If your privacy notice lists processors, add the retention period: message content and access records are kept for twelve months and then deleted.
- When a staff member leaves, remove their Shopify account. Their past rows in the audit log keep their staff id, so they remain attributable after the account is gone.
Why bother, for a notifications app
The honest reason is that the volume of personal data in a WhatsApp app is small per customer but complete per store. Every customer who ordered has a row. A leak of the message log is a leak of your entire active customer base's phone numbers, in a channel where an unsolicited message is an intrusion rather than an annoyance. Shopify's recent move to treat WhatsApp consent as a first-class field at checkout is a sign of how the platform views those numbers. An access log is cheap to write, costs the merchant nothing, and turns the question of who saw what from a shrug into a query. Beacon Messenger has kept one since its first release, and if you ever need to read it, the data is there, by store, by staff account, for a year.
Common questions
Can I see the audit log inside the app?
Not yet. The audit table is kept for investigations and compliance questions and is available on request through support, scoped to your store. A read-only view in the admin is a reasonable future addition and is on the list; if you need one, say so, because that is how features get ordered.
Which staff member is recorded when someone opens the message log?
The Shopify staff account that is signed in to the admin. The embedded app receives a session token from Shopify on every request, and its subject is the staff user id. The audit row stores it as user: followed by that id. It is Shopify's identifier, so it stays meaningful after the staff account is removed.
Does the audit log store the phone numbers that were viewed?
No. It stores what was asked for: the filters, the search term, the page, and how many rows came back. Combined with the message rows it is enough to reconstruct what was visible, without copying personal data into a second table.
What happens to a customer's messages when Shopify sends the redact webhook?
The app blanks the phone number, removes the name and the filled-in merge fields and deletes any stored reply, but keeps the row with its status and timestamp so delivery statistics remain correct. The redaction itself is recorded as an audit row with the number of rows affected.
More guides
- WhatsApp Business app drops order tools: move orders to Shopify
- A customer replied STOP to a WhatsApp order message. Now what?
- WhatsApp marketing templates leave the Cloud API in October 2027
- WABA to Messaging Account: what changes for Shopify WhatsApp
- Order paid later, refunded or edited: which WhatsApp messages send
- Edited your WhatsApp automation? What queued messages send
- How to add a WhatsApp chat button to your Shopify store (2026)
- How to send Shopify order confirmations and shipping updates over WhatsApp with the official Cloud API
- Cash on delivery on Shopify: confirm orders over WhatsApp before you ship
- Recovering abandoned checkouts on Shopify with WhatsApp, the compliant way
- Why WhatsApp apps get your number banned: linked device vs API
- How a "free" WhatsApp app for Shopify ends up charging you
- Por qué una app de WhatsApp "gratis" para Shopify te cobra
- Pushdaddy or SuperLemon alternative: WhatsApp apps compared
- How to verify Shopify WhatsApp notifications were delivered
- Chat button still on your store after uninstalling the app?
- WhatsApp API pricing changes on Oct 1, 2026: Shopify impact
- Setting up the WhatsApp Cloud API with Meta's MCP and an AI agent
- WhatsApp chat outside business hours: what shoppers should see
- WhatsApp product sharing on Shopify: tracking dark social
- WhatsApp template rejected? Fixing Shopify order templates
- One WhatsApp number or two? Shopify notifications & support
- Shopify Canvas and Beacon Messenger: what works today
- Shopify now collects WhatsApp marketing consent at checkout. Here is what it changes
- Split shipments on Shopify: how many WhatsApp updates to send
- WhatsApp's 250-a-day messaging limit and your Shopify store
- WhatsApp, SMS or email for Shopify order notifications?
- WhatsApp is down: what happens to your Shopify order notifications
- Shopify orders with no phone number: why WhatsApp messages get skipped
- Shopify rollout discounts and WhatsApp order messages
- Add a Track order button to WhatsApp order messages
- Which Shopify orders trigger a WhatsApp message?
- The abandoned checkout timer restarts every time the shopper comes back
- Blank names, twelve-item orders: what WhatsApp merge fields fall back to
- Send a WhatsApp test message before your first order: what the Connect and Test buttons check
- Disconnect, update credentials, app secret: what each does
- COD reply not tagged: how Beacon Messenger matches replies
- WhatsApp template language: why name alone is not enough
- Finding one WhatsApp message in the Beacon Messenger log
- WhatsApp automation is On but nothing sends: a checklist
- Mapping WhatsApp template variables to Shopify order fields
- Every WhatsApp chat button setting in the Shopify theme editor
- WhatsApp template examples for Shopify: order, shipping, COD, cart
- The Share on WhatsApp block, setting by setting
- WhatsApp order messages when customers speak several languages
- Reading the Beacon Messenger dashboard: sent, delivered, failed, skipped
- Shopify batch fulfilment: what happens to 250 WhatsApp shipping messages
- WhatsApp template status: approved, pending, paused, disabled, and what sends
- WhatsApp quality rating: the field on the Connected number card
- COD returns (RTO) on Shopify: confirm orders on WhatsApp first
- WhatsApp error codes on failed messages: a reference
- WhatsApp display name: what customers see on your order messages
- Shopify Messaging WhatsApp automations vs Beacon Messenger
- OXXO, bank transfer and pay-later orders: when the WhatsApp confirmation goes out
- How many WhatsApp messages will Black Friday send? Sizing your plan
- WhatsApp usernames and BSUIDs: what changes for Shopify order messages
- Reconciling your WhatsApp bill with the Beacon Messenger log
- Track with Shop vs WhatsApp shipping updates on Shopify
- Meta changed my WhatsApp template from utility to marketing
- Shopify's new app security review: what Beacon Messenger can access
- A shopper cancels their own Shopify order: what WhatsApp sends
- Customer erasure in 5 days: what the WhatsApp log keeps
- WhatsApp INR billing deadline: Indian Shopify stores
- WhatsApp template headers: text, image or document?
- Gift orders on WhatsApp: buyer's phone or the recipient's?
- WhatsApp order messages at night: when each one sends
- Downgrading a WhatsApp app plan after peak season: what changes
- Shopify subscription renewals and WhatsApp order messages