Retrics
Start free · 14 days

CRO · DATA & PRIVACY APPENDIX

What CRO
reads, and why.

The company policies below apply to everything Retrics runs. This page is the part that is specific to this product — the data it touches, and who else sees it.
All policies →About CRO →
BUILDING
CROBUILDING
RUNS ONcro.retrics.ai
CUSTOMER GRAPHOutside the shared graph
DATA FLOW DECLAREDYes

THIS PAGE IS THE URL THIS PRODUCT’S APP LISTING SUBMITS

WHERE IT STANDS

The work is real. The door is not open yet.

THE DATA FLOW

Five questions, answered plainly.

WHAT IT READS
  • Orders and refunds from Shopify, to settle an experiment on money rather than on clicks
  • Experiment-assignment events and a sampled embed heartbeat from the storefront, with Shopify's Web Pixel also relaying assignments plus checkout-started and checkout-completed events
WHAT IT STORES
  • Storefront event rows for experiment assignments, sampled embed heartbeats, checkout starts and checkout completions: event type and shop domain, browser-generated visitor id and Shopify client id where present, plus experiment and arm ids or checkout order id, total and currency where applicable
  • Order rows contain order id, total, refunded total, currency, creation and receipt times, note attributes and cart token; refund rows contain refund id, order id, amount, and creation and receipt times — no Shopify customer object is copied
  • Experiment definitions, their variants and assignments, and the verdict with its arithmetic
  • Daily aggregates per shop
HOW IT IS PROTECTED
  • CRO does not extract or persist Shopify's customer object or dedicated shopper name, email, phone or address fields. Order note attributes are stored as Shopify sends them, so their merchant-controlled contents are not claimed to be free of personal data
  • Shopify's permission screen describes access to IP address, browser and operating system, and browsing behavior. CRO's pixel does not access browser context or an IP field; its JSON event payload contains no IP value and the event schema has no dedicated IP column
  • The CRO visitor id is a random browser-generated string; Shopify's client id is kept only to join an experiment assignment to checkout activity
HOW LONG IT IS KEPT
  • Raw storefront events are deleted after 90 days, by dropping whole months at a time rather than ageing rows out one by one
  • The daily aggregates that outlive them carry no per-shopper data, which is what makes a 90-day limit on the raw events affordable
  • A shop redaction from Shopify deletes that store's events, assignments, orders, refunds and aggregates
WHO ELSE SEES IT

Nobody. Nothing this product reads or stores leaves Retrics.

Stated rather than left blank on purpose — an empty list reads as unfinished, and “nothing leaves” is a claim somebody has to make.

AND THE COMPANY POLICIES IT SITS UNDER

These apply to everything Retrics runs.

They are linked rather than repeated here. Twelve copies of the same policy is twelve things that drift apart.

Privacy →Subprocessors →Data processing addendum →Data rights →Data deletion →Security →Terms of service →

THIS APPENDIX IS MAINTAINED WITH THE PRODUCT · EDITING IT CHANGES NOTHING ELSE