How the scan works
On this page
What the app never does
- It never places an order. The walk opens checkout and stops at the payment step. Nothing is submitted.
- It never types card data. The payment fields are Shopify’s own. The app only notes which host they load from.
- It never changes your store. Its access is read-only, except for the one test customer it creates for the walk. It does not edit your theme, products, orders, apps or settings, and it does not remove anything it finds.
- It never reads your real customers. It works only with its own test customer.
Two kinds of checks
Admin checks (read-only access to your store)
- Theme: the files of your live theme. The app lists scripts loaded from other sites and looks for code patterns used by card skimmers, such as code that listens to card-like input fields or sends data to sites that are not part of your store.
- App embeds and app blocks: which apps add code to your theme, where, and with which settings. See App embeds and web pixels.
- Store data (Pro): metafields, metaobjects, files in Content > Files, URL redirects and menu links. See Metafields and files.
The shopper walk
A browser on the app’s server visits your store like a shopper: the home page, a collection, a product, search and the cart. With Pro it also signs in as the test customer, opens the account pages, adds one product to the cart and opens checkout up to the payment step.
On every page it records each script that loads, a fingerprint of its content, the sites it talks to, frames, forms that send to another site, the sites your web pixels call, and where checkout ends up. If the same script address starts serving different content, the fingerprint changes and the app reports it.
The walk is also recorded: a screenshot of each step (and, on the former Growth plan, a video of the visit), so you can see what the scan saw. See Walk evidence.
The walk needs one product that is available to buy, because Shopify does not open checkout for an empty cart. If checkout cannot be reached (no available product, or Shopify shows a challenge), the scan says “checkout not reached” with the reason, and checkout is then covered only by the theme and app embed checks.
How often
- Free: a theme and app embed scan every day, and a rescan when your theme is changed or a new theme is published. You can also start manual scans (Scan now), up to 10 a month and one a day; only manual scans count.
- Pro: a scan with the shopper walk every day, the same theme rescan, and a manual scan as often as every 10 minutes.
- The first scan starts as soon as you install the app.
The walk runs one browser at a time on the app’s servers, so a daily walk adds about one visitor’s worth of traffic. It can still show up in your analytics as a visit that reached checkout.
New, changed, removed
The first scan is your baseline. Each later scan compares with it and reports what is new, what changed and what was removed, plus anything that matches a risky pattern. See Reading findings.
What a finding means
A finding is a fact about your store, such as “new script from <site> since <date>”. It is not a verdict that an
app or a person is malicious. Most changes are expected: you edited the theme, installed an app, or an app shipped
an update. The app tells you what changed so you can check. It cannot promise to find every kind of malicious
code; see What the scan cannot see.