Privacy policy
Last updated: 19 November 2026
Magpie (“the App”) is provided by Robert Mardall (sole trader), United Kingdom (“we”, “us”). You can contact us at rmardall@gmail.com. This policy explains what information the App collects when a Shopify merchant installs it, and when shoppers use the App on that merchant’s store, and how we use it.
1. Our role
- Merchant data (your store and product information): we act as a controller for the account and service data we need to run the App, and as a processor for your store data.
- Shopper data (style finder activity on your storefront): you, the merchant, are the controller, and we process it on your behalf, only to provide the App to you.
2. Information we collect
2.1 From Shopify, through its APIs, when you install the App
| Data | Why |
|---|---|
| Your shop’s myshopify domain, and an access token for the permissions you approve | To connect to your store and keep the App working |
| Product data: product ID, handle, title, SEO title, the first 300 or so characters of the description, product type, Shopify product category, vendor, tags, size option values, the “Target gender” and Google Shopping “gender” fields, collection IDs and titles, status, total inventory and main image URL | To build the style finder, show results, leave out sold-out or excluded products, and tell womenswear from menswear |
| Derived product data we create from your product photos: image embeddings (numeric style fingerprints), dominant colours, an assigned category and audience, and style words | To match shoppers’ picks to similar products and label their style |
| Your App settings and the plan you choose | To run the App the way you set it up and to apply your plan |
| Feature requests you send us from inside the App | To consider them for future versions of the App |
The App requests these permissions: read_products, read_inventory, read_metaobjects, write_online_store_pages, write_app_proxy, write_pixels and read_customer_events. Online store pages are used only to create the style finder page when you click “Create page”; inventory is used only to keep sold-out products out of results; metaobjects are read only to get the value of a product’s “Target gender” attribute (from Shopify’s product category), to tell womenswear from menswear, and are never changed. We don’t request access to your customers or orders, and we don’t read them. We don’t ask for staff names or emails. The App uses offline access tokens only.
2.2 From shoppers who use the style finder on your store
The App does not collect shoppers’ names, email addresses, postal addresses, phone numbers, payment details, Shopify customer IDs or order IDs.
It does collect:
| Data | When | Why |
|---|---|---|
| Style finder session: which products were shown and picked in each round, the categories and audience chosen, the results shown, the style headline, and an optional thumbs up or down on the results (not linked to the shopper). After a thumbs down, the shopper can also pick a reason (such as “Wrong colours”) and type an optional comment of up to 300 characters; these are stored with the anonymous style finder session. We don’t ask for personal details there, and the comment is only what the shopper chooses to type | Whenever a shopper uses the style finder | To create each round and the results |
| Style finder events: such as shown, started, round completed, result opened and added to cart. Each has a timestamp, the entry point (page, inline, or pop-up from a banner or card) and, where relevant, a product ID and value | When these happen | To show you style finder starts and the value added to cart |
| Visitor ID: a random identifier (UUID) created in the shopper’s browser | Only if the shopper has allowed analytics through your store’s cookie or consent banner (Shopify Customer Privacy API) | To count unique visitors and link a style finder start to a later purchase. It is pseudonymous: we can’t tell who the shopper is from it, but we treat it as personal data. |
| Purchase signal: when an order is completed, the order total, the currency, a one-way hash of Shopify’s checkout reference (we don’t keep the reference itself), the visitor ID (if present) and whether the visitor used the style finder. For items the style finder added to the cart: the product, variant, quantity, line price and style finder session ID. When a shopper adds one of their style finder results to the cart from a product page: that product, its price and the style finder session ID | Sent by the App’s web pixel, which Shopify runs only when the shopper has allowed analytics | To report the value purchased by style finder users and which style finder products were bought. Purchases are counted only for visitor IDs and style finder sessions we have already seen use the style finder. |
| IP address | Held in server memory only, for a short time. It is not written to our database. | To limit request rates and prevent abuse |
Data stored in the shopper’s browser (local storage):
styleQuiz.visitorId: the random visitor ID. Only stored with analytics consent.styleQuiz.tookQuiz: a “used the style finder” flag. Only stored with analytics consent.styleQuiz.lastResult: the shopper’s last results (style label and product titles and images), so they can see their picks again. Only stored with consent: preferences consent where the store’s cookie banner asks for it separately, otherwise analytics consent. If consent is withdrawn, it is deleted the next time the style finder loads. It stays on the shopper’s device and is not sent to us.
3. How we use information
We use it only to:
- provide the style finder, results and dashboard to you;
- keep the App secure and working, which includes fixing bugs;
- handle billing through Shopify;
- meet our legal obligations.
We don’t sell personal data, use it for advertising, build cross-store profiles of shoppers, or combine one merchant’s shopper data with another’s.
4. Who we share it with (sub-processors)
| Provider | What | Where |
|---|---|---|
| netcup GmbH | Hosts our servers and database (the App, the image-analysis worker and the Postgres database all run on our own server) | Germany (EU) |
| Shopify | Platform, billing (Shopify App Pricing), product image CDN | Per Shopify’s privacy policy |
| Let’s Encrypt | Issues our TLS certificate. It receives our domain name only, no merchant or shopper data. | USA |
We may also disclose information if the law requires it, or to a buyer of our business under the same protections.
5. International transfers
Our servers are in Germany (EU), which the UK recognises as adequate. Merchant and shopper data is not sent outside the EU by us.
6. How long we keep it
| Data | Kept |
|---|---|
| Product data and derived data | While the App is installed. Updated as your products change. Removed when you delete a product. |
| Style finder sessions (including any results feedback and comment), analytics events and purchase signals | 13 months from when they were recorded. Older records are deleted automatically every night. |
| Feature requests you send us | Until the App is uninstalled and your shop’s data is erased |
| Access tokens and login sessions | Deleted as soon as you uninstall the App |
| Everything above | Permanently deleted when Shopify sends the shop/redact request, about 48 hours after you uninstall |
| Server logs | Only as long as needed to run and troubleshoot the App. Logs contain shop domains and technical event details, not shopper identities. |
7. Shopify privacy requests (GDPR webhooks)
The App is subscribed to Shopify’s mandatory compliance webhooks. Each request is verified with Shopify’s signature, and invalid requests are rejected.
customers/data_request: we don’t hold data linked to a Shopify customer, email or order, so there is nothing to export. We log the request.customers/redact: for the same reason, there is no customer-linked data to delete. We log the request. Style finder data is held against a random visitor ID that can’t be matched to a Shopify customer.shop/redact: we delete all data held for the store: products, derived data, store categories, style finder sessions, events, settings, feature requests, jobs and sessions.
When you uninstall, we immediately delete access tokens and stop all processing for your store.
8. Security
All traffic uses HTTPS (TLS). Requests from Shopify are verified with signatures (HMAC or session tokens). The database is reachable only from our own server. Access tokens expire and are refreshed. Access to production systems is limited to Robert Mardall.
9. Your rights
Merchants can contact us to access, correct or delete their data. Shoppers should contact the store they shopped with, because the merchant controls their data; we will help the merchant respond. Under UK GDPR and EU GDPR you may also complain to the UK Information Commissioner’s Office (ico.org.uk) or your local supervisory authority.
10. Children
The App is not aimed at children, and we don’t knowingly collect children’s data.
11. Changes
We’ll update this page when the App’s data practices change, and tell merchants about significant changes by email or in the App.
12. Contact
Robert Mardall (sole trader), United Kingdom
Email: rmardall@gmail.com