Shopify's new app security review: what Beacon Messenger can access
Shopify admin now shows each app's permissions, sensitive data use and token type under Settings > Apps. What you will see for Beacon Messenger, and why.
On 5 November 2026 Shopify's changelog announced that the Apps page under Settings in the admin now shows security information for every installed app: what it has permission to do, whether it handles sensitive data, whether it uses expiring access tokens, and whether it restricts the servers that can talk to your store. Until now most of that lived in the install screen you clicked through once and in the developer's privacy policy. It is now a page you can open any time.
That is a good change, and it will prompt questions. A WhatsApp notification app necessarily reads orders and customer phone numbers, which is exactly the kind of access the new page flags. This post goes through what the page shows for Beacon Messenger, line by line, and what each entry means in practice, so the review takes five minutes rather than an afternoon.
Where to look
In the Shopify admin, open Settings, then Apps and sales channels, and click Beacon Messenger. Shopify's help pages on apps describe the page. Alongside the usual About and Support details there is now a section describing permissions and security, and an activity view showing what the app has been doing. The exact labels may change as Shopify iterates; the categories below are the ones announced.
Permissions: two scopes
Beacon Messenger asks Shopify for two access scopes, and the permissions list is the place to confirm them: write_orders and read_fulfillments. Nothing else. No customers scope, no products, no content, no themes, no discounts.
| Scope | Why it is needed | What it is not used for |
|---|---|---|
| write_orders | Receiving order and abandoned checkout webhooks, reading the order fields that go into a message, and adding a tag to an order when a customer confirms a cash on delivery order by reply | Editing line items, prices, addresses or fulfilment status. The only write is the tag on COD confirmation |
| read_fulfillments | Receiving fulfilment webhooks so a shipping update goes out when a tracking number is added | Creating or changing fulfilments |
The write in write_orders deserves the explanation, because a read-only app would look tidier. Shopify's order webhooks and abandoned checkout webhooks are granted through the orders scope, and the cash on delivery flow, where a customer replies to confirm and the app tags the order so your team can see it, needs to write that tag. The COD confirmation post describes the flow. If you do not use COD confirmation, the app still holds the scope but never writes anything; every change it makes to an order is a tag, and every tag it adds is in its audit log.
Sensitive data: yes, and here is which
Shopify labels apps that access protected customer data, and Beacon Messenger is one. To send an order confirmation to a customer on WhatsApp the app needs the customer's phone number, and to address them it uses their name. Both are protected customer data under Shopify's rules, which means the developer had to request that access in Shopify's developer tools and explain the use, and it means Shopify records the app's access to it, which the access log post explains how to read.
- Name: used in the message greeting and in the merge fields you map into templates.
- Phone number: used as the WhatsApp destination. If the order has none, the message is skipped and logged as skipped, as the no phone number post describes.
- Order contents and totals: order number, items, total, tracking link, used only to fill the template you chose.
- Not used: email address, full shipping address, payment details, browsing history. The app does not read customer records directly; it reads what arrives on the order and checkout webhooks.
What the app stores, and for how long, is on its security page and in the privacy policy. The short version: the message log keeps the phone number, the template used and the delivery status for each message for 365 days by default so you can investigate a complaint, then deletes it. Shopify's GDPR webhooks for customer data requests and erasure are handled, so a deletion request made through Shopify removes the customer's rows early.
Expiring access tokens
The new page says whether an app uses expiring access tokens. Beacon Messenger does. The token Shopify issues to the app for your store expires and is renewed automatically, rather than being a permanent credential that would work forever if it leaked. Shopify has been moving apps towards this model, and it is one of the items worth checking on every app you have installed: a permanent token that never expires is a bigger prize for an attacker.
This is separate from the WhatsApp side. The Meta system user token you paste into Beacon Messenger to connect your WhatsApp Business account is stored encrypted and is used only to call Meta's API on your behalf. The credentials post covers rotating it. Shopify's page does not know about it, because it is not a Shopify credential.
IP restrictions
The page also shows whether the app has told Shopify which server addresses it will call from, so that a request from anywhere else is refused. Shopify's developer changelog set deadlines in November 2026 for public apps to configure this. Beacon Messenger runs on a fixed set of servers, so the allowlist is a short list. If the page shows it as not configured on the day you read this, check back; it is a setting on the developer side, not something you can or need to change.
App activity
The activity view is new and, for a messaging app, mostly reassuring to read. It shows the app's recent interactions with your store. For Beacon Messenger expect to see order, checkout and fulfilment webhooks being delivered, the occasional order tag, and little else. There is no polling: the app does not fetch your orders on a schedule, it waits for Shopify to tell it one was created. A quiet day in your store is a quiet day in the activity view.
If you see something that does not fit, such as customer or product reads, that is worth a support message, with the timestamp. The app's own audit log in its admin records every setting change, every connection change and every tag it adds, so the two can be compared.
A five minute review
- Open Settings, Apps and sales channels, Beacon Messenger. Confirm the permissions list shows orders and fulfilments only.
- Read the sensitive data entry and decide whether the reason is one you accept: it needs the phone number to send a WhatsApp message. If you have stopped using the app, uninstall it rather than leaving the access in place.
- Check that expiring access tokens show as in use.
- Open the app's security page and privacy policy and note the retention period. If 365 days is longer than your own policy allows, ask support about the shorter setting.
- Do the same for every other app in the list. The one that reads customers and products and has no obvious reason to is the one to ask about.
Shopify has made the question of what an app can see something you can answer from the admin rather than from a privacy policy. For Beacon Messenger the answer is short: orders and fulfilments, the customer's name and phone number from each order, one tag on confirmed COD orders, a log kept for a year and then deleted. If a WhatsApp app asks for much more than that, ask what for.
Questions
Why does Beacon Messenger need write access to orders instead of read-only?
Order and abandoned checkout webhooks are granted through the orders scope, and the cash on delivery confirmation flow adds a tag to the order when the customer confirms by reply. That tag is the only write the app performs. If you do not use COD confirmation the app never changes an order.
Does Beacon Messenger read my customer list?
No. It has no customers scope. The name and phone number it uses come from each order or checkout as Shopify sends it, and they are used to address that one message. Shopify's protected customer data rules apply to those fields, which is why the app is labelled as handling sensitive data.
What does the sensitive data label on an app mean in Shopify?
It means the app accesses protected customer data such as names, phone numbers, email or addresses, and had to request that access from Shopify with a stated reason. For a WhatsApp notification app the phone number is the reason; a message cannot be sent without one. The label is a prompt to check that the reason makes sense.
Can I shorten how long Beacon Messenger keeps message logs?
The default retention is 365 days for message and audit rows, after which they are deleted automatically. Customer erasure requests received through Shopify remove a customer's rows sooner. Contact support if your own data policy needs a shorter period for your store.
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
- Who looked at your customers' phone numbers? The access log behind a WhatsApp app
- 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
- 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