Privacy Policy

• Order and store data (Shopify Admin API). Order totals, dates, refunds, discount usage, and product line items, plus customer counts (new vs returning). These are read by a nightly job and aggregated into daily store-level metrics (orders, revenue, average order value, refund rate). Individual orders and customers are not displayed, exported, or shared.
• Storefront behaviour (web pixel). The app installs a Shopify web pixel that records page views, product views, add-to-cart, and checkout events. Payloads are stripped of customer identity fields (names, emails, addresses, IP addresses) before storage; only anonymous event counts are kept, and they are aggregated into daily funnel metrics.
• Theme change metadata (GitHub, optional). If the merchant’s development team connects a GitHub repository, the app stores commit and pull-request metadata (titles, dates, authors, changed file paths) to annotate the analytics timeline. No customer data is involved.
• Page speed data. Public performance measurements of the storefront (for example via Google PageSpeed Insights). No customer data is involved.

The app does not request access to customer names, email addresses, phone numbers, or physical addresses. It does not sell or share data with data brokers or advertisers, does not use store data for marketing or to train machine-learning models, and does not track merchants or their customers across other sites.

Your store’s data is used to provide the app’s features to you: daily performance metrics, funnel analysis, alerts about significant metric changes, and annotated timelines showing the impact of theme changes. Uncover Commerce staff can view your store’s metrics through an internal dashboard, for two purposes only — operating the app (checking that data is arriving correctly and diagnosing faults) and answering your support requests.

No merchant is ever shown another merchant’s data, and no merchant is ever identified to another. Your revenue, orders, conversion rate, sessions, and theme changes belong to your store, are visible only to you and to Uncover Commerce staff for the two purposes above, and are never disclosed to any other merchant, agency, advertiser, or data broker. Access is enforced technically as well as contractually: each store’s rows are isolated by database row-level security, and the dashboard you see is scoped to your store alone.

Uncover Commerce combines the daily store-level metrics from stores using Revenue Gap to calculate benchmark statistics — for example, the median conversion rate or typical add-to-cart rate across stores in a retail category. These statistics are used to improve the app (so a metric can be shown as strong or weak rather than only as a number), to provide comparative context back to merchants, and to inform Uncover Commerce’s own understanding of how stores in a category perform.

Only derived statistics leave your store’s boundary — a median, an average, a percentile position across a group. What is not shared, in any form: your store’s name or domain, your individual figures, your theme changes, your repository, and anything that would let another merchant identify you or reconstruct your numbers. A benchmark is only ever calculated across enough stores that no single store’s contribution can be isolated from it. No customer-level data of any kind is involved, because none is stored.

If you would prefer your store’s metrics were excluded from benchmark calculations entirely, email us and we will exclude them; the app continues to work unchanged.

Data is stored in a PostgreSQL database hosted by Supabase and processed on servers operated by Uncover Commerce. All data is encrypted in transit (TLS) and at rest. Shopify API access tokens expire roughly hourly and are refreshed automatically, so no long-lived credential to your store is held. Access is restricted by row-level security so each store’s data is isolated, and staff access requires authentication.

• Raw pixel events are deleted after 90 days, once aggregated. Raw GitHub webhook payloads are erased after 6 months, leaving only the timeline entry they produced. Daily metrics are kept for 2 years, or 6 months where broken down by segment.
• When the app is uninstalled, the store’s API access token is deleted immediately. Store data is retained for 30 days (so reinstalling restores history) and then permanently deleted by a scheduled job. The one exception is a store archived at the merchant’s own request, where data is kept read-only instead.
• The app subscribes to Shopify’s mandatory compliance webhooks (customers/data_request, customers/redact, shop/redact) and honours them: because no customer-identifying data is stored, redaction requests are satisfied by design, and shop redaction permanently removes all customer-derived raw data for that store.

• Supabase — database hosting and authentication.
• Our hosting provider for the application server.
• Cloudflare — DNS, TLS, and reverse proxy for the app. Every request to the app passes through it, so it handles connection metadata including visitor IP addresses. No store data is stored there.
• GitHub — the source of repository change metadata, and only where a merchant has connected a repository.
• Google PageSpeed Insights — public page performance. No personal data is sent.
• Slack and Resend — internal operational alerts only. No customer data is included.

Merchants can request export or deletion of their store’s data at any time. Customers should direct data requests to the merchant, who can action them through Shopify — the app responds to Shopify’s redaction webhooks automatically. Where UK/EU GDPR applies, you have the right of access, rectification, erasure, restriction, and portability over personal data we process.