Privacy and security

Faces stay on the shopper's device

Camera only with consent. Faces are processed on the shopper's device, never uploaded. Here is exactly what happens, and how we check it.

Data flow

Trialhood try-on data flow On the shopper's device: the camera feeds face tracking, which feeds the 3D renderer; none of this leaves the device. The device downloads the storefront script and 3D model from the Trialhood CDN, and sends the Trialhood API only the consent decision (decision, policy version, time, session token) and allowlisted usage events without face data. The merchant sees aggregated usage in the dashboard. Shopper's device (browser) Nothing in this box leaves the device Consent screen before any camera Camera after Start camera Face tracking on device (WASM) 3D renderer frames on your face Video frames and face landmarks: memory only Trialhood CDN Storefront script, 3D model (GLB), face-tracking model, self-hosted Trialhood API Consent log: decision, policy version, time, session token, coarse region. No face data, no IP. Usage events from an allowlist. No images. Your dashboard Aggregated usage and consent rate, CSV export download consent

What is and isn't processed

DataWhereKept
Camera videoShopper's browser onlyNever stored or sent
Face position (landmarks)Shopper's browser only, in memoryDiscarded when try-on stops
Consent decisionTrialhood APIDecision, policy version, time, session token, coarse region (no IP, no face data)
Usage eventsTrialhood APIAllowlisted events such as 3D opened or try-on ready; behavioural events only with the store's analytics consent
Your 3D modelsTrialhood storage and CDNUntil you delete them; downloadable any time

How we check it

Our end-to-end test runs a full try-on in a real browser with a simulated camera and records every network request the page makes. It fails if any request goes anywhere other than the store page, the Trialhood API and the asset CDN, or if a request carries image data. The face-tracking files are self-hosted, and the third-party library's usage telemetry is removed at build time.

What merchants control

  • The notice text and retention statement shoppers see, from editable templates.
  • Switching try-on off by US state or by country (the 3D view stays available).
  • A compliance kit: notice template, retention schedule template, data-flow diagram and subprocessor list.

Consent-first by design. Templates are a starting point; review them with your counsel. See our BIPA guide and the subprocessor list.

Privacy questions

Do you store shoppers' faces?

No. Face tracking runs in the shopper’s browser and no camera images are sent to us. We log only that consent was given or declined, with the policy version and time.

What about BIPA and other biometric laws?

Trialhood shows a consent screen before the camera opens, gives you editable notice and retention templates, and can switch try-on off by state or country. Templates are a starting point: review them with your counsel. This isn’t legal advice. Read our BIPA guide.

See it on your own products

Send us your store link. We turn 3 of your products into 3D and show them on your own product page, before you decide anything.

Get 3 products in 3D, free

Free · no card · just your store link