Shopify is tightening app security. What SafeSale can touch
Shopify asked every app to move to expiring tokens by 1 January 2027. What that means for merchants, and exactly which permissions and data SafeSale holds.
By Beacon Wave Studio · · 8 min read
On 20 October 2026 Shopify published a post for app developers with an unusual tone. The title was Securing your app, together, and the first line asked every developer to act within the week. A week later a follow-up set dates: public apps that still use the old kind of access token will be delisted from the App Store on 1 January 2027, merchants will see a warning in the admin from 15 January, and from 1 April 2027 those apps will simply get a 403 from the Admin API. If you run a store, none of this was addressed to you, and yet all of it is about apps you have installed. This post explains what Shopify is changing, what you can check on your side, and then gets specific about SafeSale: every permission it asks for, every webhook it receives, every piece of data it keeps, and how long.
What Shopify asked developers to do
The 20 October post lists eight steps. Three of them are visible to merchants in some form, so they are worth knowing about.
Expiring access tokens. When you install an app, Shopify hands it a token that lets it call your store on your behalf. Older apps hold a token that never expires; if it leaks, it works until somebody notices. Expiring tokens last a short time and are refreshed by the app, so a leaked token is worth very little. Shopify is making them mandatory for every public app that uses the Admin API, with the dates above. Custom apps you built yourself are not affected.
A security scan. Shopify added a security check to its developer toolkit that looks for the mistakes that cause real incidents in apps: routes that do not check who is calling, one shop reading another shop's data, webhooks accepted without verifying they came from Shopify. Shopify said that in early access most partners found something they did not know about.
Two-step authentication everywhere. Not just on the Partner account, but on the hosting, the code repository, the e-mail and anything else that can touch the app. The 27 October update added tools on top: a way for apps to restrict API calls to their own server IP addresses, a declaration of which outside servers an app talks to, and identity verification for developers.
What you can check as a merchant
You cannot run the scan on somebody else's app, but three things are in your hands.
- Open Settings, then Apps and sales channels, and read the list. Every app there holds a token for your store, including the ones you stopped using in 2024. Uninstall what you do not use. That is the single most effective step in this whole post.
- For each app you keep, click through to its permissions. Shopify shows what the app can read and write. The question to ask is whether the permission matches the job. A sale app that wants to read customers deserves a question; a sale app that wants to write products does not, because that is how prices change.
- Turn on two-step authentication for every staff account in your store, not only the owner. Shopify asked developers to do this for their accounts, and the logic applies equally to yours.
SafeSale and expiring tokens
SafeSale runs on Shopify's current app framework with expiring offline tokens switched on. In practice: the token SafeSale holds for your store is short-lived and is refreshed automatically each time the app needs to talk to Shopify, including when a scheduled sale starts at 3 a.m. with nobody logged in. There is no migration for you to wait for and no warning will appear beside SafeSale in January. If a token were ever copied out of our database, it would stop working on its own within hours.
The five permissions, and what each one is for
Shopify calls permissions scopes. SafeSale asks for five. Here is the list exactly as the app declares it, with the one job each scope does.
| Scope | Why SafeSale needs it | When it is used |
|---|---|---|
write_products | Reads variant prices to build the snapshot and preview, and writes price and compare-at price in price rewrite mode. | Every sale, at start and at end. Reading also happens when you preview a draft. |
write_discounts | Creates, updates and deletes the automatic discount that an automatic discount mode sale uses at checkout. | Sales that use the discount mechanism. |
read_rollouts | Lets the sale page show when a Shopify rollout includes the sale's discount, so you are not surprised by a schedule set elsewhere. | Opening a sale page. |
write_pixels | Installs the web pixel that records which A/B variant a visitor saw. | Only when you start an A/B experiment. |
read_customer_events | Lets that pixel subscribe to the page view and checkout completed events it counts. | Only while an experiment is running. |
Two things are missing from that table on purpose. There is no read_customers and no read_orders. SafeSale has no screen that would show you a customer, and it does not need orders to run a sale. Shopify treats customer and order data as protected and asks apps to justify requesting it; a sale app has no justification, so we never asked.
If we ever add a scope, Shopify will ask you to approve the new permission before the app can use it. SafeSale subscribes to the app/scopes_update webhook so its record of what you granted stays in step with what Shopify says you granted. Until you approve, the app keeps working with the old set.
The webhooks SafeSale receives
A webhook is Shopify telling the app that something happened. These are the ones SafeSale listens to, which is also a list of the events it can see.
- app/uninstalled. You removed the app. The token is deleted on receipt.
- app/scopes_update. You approved or declined a permission change.
- app_subscriptions/update. Your SafeSale plan changed, so the cached plan is refreshed.
- products/update. A product changed. SafeSale uses this to notice when somebody edits a price by hand during an active sale, as the price edited mid-sale post describes. It reads the product payload, which contains prices and titles and no customer data.
- The three privacy topics Shopify requires of every app: customers/data_request, customers/redact and shop/redact. The first two have nothing to return, since no customer records exist; the third triggers deletion of the store's data.
Every webhook is verified against Shopify's signature before it is processed. A request that does not carry a valid signature is rejected, which is the unverified webhook problem the security scan looks for.
What is stored, and for how long
The data SafeSale keeps is the minimum that lets it restore your prices exactly: your store's myshopify domain and the access token; the sales you configure, meaning targets, rules and schedule; a snapshot of each affected variant's product ID, variant ID, price and compare-at price taken before any change; the audit log of what the app did and when; and your plan. Sale details are also written to a metafield that belongs to the app so the optional theme blocks can read them without a script. The audit log post shows what that log looks like.
During an A/B experiment the pixel adds one more category: a first-party cookie naming the variant a visitor was assigned, a count of visits per variant, and the order ID and amount of orders placed, deduplicated by order ID. No name, no address, no e-mail. The pixel post lists each field.
On uninstall the token goes immediately. Snapshots, sales and the audit log stay for 90 days, because the most common support request after an uninstall is a reinstall followed by please put my prices back, and the snapshot is what makes that possible. After 90 days they are deleted automatically. You can ask for earlier deletion from the store owner's e-mail address.
What this does not cover
Honesty about limits is part of the point. SafeSale cannot protect you from a different app that has broad permissions and weak security; the list in Settings is yours to prune. It cannot stop a staff member with the right role from changing prices by hand, although it will notice and show you. And a security posture is a snapshot: what is true today is what is described here, and the privacy page on this site is where changes get recorded first. If you want to verify any of it, the permission list Shopify shows you at install time is the same five scopes in the table above.
Frequently asked questions
Do I need to do anything in my store because of the expiring token change?
Not for SafeSale, which already uses expiring offline tokens. For other apps, watch for the warning Shopify says it will show in the admin from 15 January 2027 next to apps that have not migrated, and ask those developers about their plans. An app that is still on old tokens on 1 April 2027 stops being able to call the Admin API.
Why does a sale app need permission to write products?
Because the price rewrite mechanism changes the price and compare-at price of each variant directly, and that is a product write in the Admin API. The discount mechanism uses a separate permission, write_discounts, to create an automatic discount. SafeSale asks for both so you can choose either mechanism per sale.
Can SafeSale see my customers or orders?
It holds no customer records, addresses, e-mail addresses or payment details. The only order-related data it stores is the order ID and amount recorded by the A/B test pixel while an experiment is running, which is used to count orders per variant and nothing else.
What happens to the access token when I uninstall?
Shopify revokes it the moment you uninstall and sends the app an uninstall webhook. SafeSale deletes the token when that webhook arrives. Price snapshots and the audit log are kept for 90 days so a reinstall can still restore original prices, then deleted.