Virtual try-on privacy: body photos, camera, and what to ask

Trying clothes with AI means the system needs some view of a body. That can be a photo you upload or a live camera stream. Neither should be a black box.

This page is not legal advice. It is a checklist of questions worth asking any try-on product — including us.

Photo path

• Who receives the image (your browser only, our API, a third model host)?
• How long is it kept for history / support?
• Can you delete history after sign-in?
• Is the garment image stored with the person image?

In TryOnAnytime, photo try-on runs through the product flow in studio; signed-in history is for your reuse. Prefer photos without bystanders.

Live camera path

• Permission is requested by the browser; denying it blocks live mode (photo may still work).
• Treat the session like a video call you control: close the tab when finished.
• Unstable networks interrupt live segments more than photo jobs — see where try-on struggles.

Merchant embed angle

If you paste an embed on a storefront, publishable keys should be scoped to your domains (embed guide). Do not paste secret server keys into theme liquid.

Practical hygiene for shoppers

1. Use a recent photo you are willing to store in account history.
2. Avoid IDs, faces of kids, or workplace badges in frame.
3. Read the site privacy policy before bulk uploads.
4. Uninstall browser extensions you no longer use (any-store notes).

Soft CTA: try a single garment after you are comfortable with the permissions dialog — studio.