Badge Runner (the "App") shows badges and labels on a Shopify merchant's products — for example "New", "Sale", "Low stock" or "Best seller" — based on rules the merchant sets and, on some plans, on the store's own sales and review data. This policy explains what data the App accesses, why, and how it is handled.
The App processes order line items — which products were bought, in what quantity, and when — to compute sales-based badges. Shopify treats order data as protected customer data, and the App accesses it under Shopify's protected customer data requirements. The App stores no customer-identifying data: it does not request or store names, email addresses, phone numbers, addresses or customer identifiers, and it does not use cookies or tracking identifiers on the storefront.
When a merchant installs the App, we access — through Shopify's APIs and only to the extent the merchant has approved — the following store data:
If the merchant switches on view-based badges, the App counts product page views as a daily total per product. A view is counted only when the shopper has consented to analytics under the store's privacy settings. No identifier of any kind — no IP address, customer id, session id, cookie or random id — is sent to or stored by the App.
We do not sell any data or use it for advertising.
We do not share store data with third parties except:
We honour Shopify's mandatory compliance webhooks:
customers/data_request — we respond that the App holds no
customer-identifying data: order line items are stored without any
reference to the customer, so nothing can be attributed to a person.
customers/redact — likewise, there is nothing attributable
to the customer to erase; the request is acknowledged and recorded.
shop/redact — 48 hours after a merchant uninstalls, we delete
all data stored for the store.
Order quantity data is kept only for the badge look-back window (at most 61 days) and view counts for 8 days; both are deleted automatically after that.
Access to the App's backend is authenticated (Shopify session tokens / signed requests). Data is transmitted over HTTPS.
We may update this policy; material changes will be reflected by a new effective date at the top of this page.
Questions about this policy or your data: edward@meginteractive.com.