Skip to content

Privacy: what your store receives

TryYourSize is built so that a store never needs the shopper’s body data to sell them the right size.

You receive You never receive
The recommended size, in your labels Tape measurements
The sizes that are wearable on this body The 3D body or any body data
Whether the full simulation confirmed the size The shopper’s email, name or TryYourSize account
Status values (ready, computing, unavailable…) Anything about the shopper’s other stores
In webhooks: the try-on ID, product SKU and recommended size A shopper identifier in webhooks

This holds for every surface: the browser and mobile SDKs, the server API (its handle is sealed and unreadable to you; raw measurements are never accepted or returned), webhooks and the Shopify app (the _tys_size line property holds a size only).

  • The shopper’s session lives in our origin’s storage, which your page cannot read. Our invisible status frame answers your page with sizes only, and only for origins registered for your key.
  • On mobile, the bridge between our window and your app only ever carries sizes, and both sides validate every message.
  • The server API’s recommendation handle is encrypted: neither your page nor your server can read it.

The shopper’s measurements and body belong to them. They can see which stores they are connected to, disconnect a store, download their data or delete their account in their TryYourSize account at any time. A disconnected store gets no more sizes for that shopper (handles are refused with handle_invalid), and you receive a profile.disconnected webhook.

Orders and returns you send carry no customer data: the API and CSV import refuse personal-data fields. The A/B visitor ID is a random first-party ID in your site’s storage, stored by us only as a store-scoped hash. List it in your cookie and storage notice as a functional analytics identifier. Results are aggregates only. See Orders and returns.

For orders, returns and analytics, TryYourSize processes data as your processor under the Data Processing Agreement you accept when you go live.

Was this page helpful?