Storage and privacy
How long try-on images are kept, when a shopper's uploaded photo is stored, and how consent and retention keep you GDPR-aligned.
Last updated July 17, 2026
Try-on involves a photo of a person, so how it is stored matters. The defaults are privacy-first, and anything that stores a shopper's own photo is off until both you and the shopper opt in.
What is stored, and for how long
- Generated try-on images are kept for your retention window, then deleted automatically. You set the number of days.
- A shopper's uploaded photo is not stored by default. It is used to generate the image and then dropped.
- If you turn on saved photos and the shopper ticks the consent box, their photo is stored so they can reuse it - and it too is deleted on the retention window.
Returning shoppers
With try-on history on, a returning shopper sees their previous result for a product instead of regenerating it, which also saves a fitting. You can optionally drop the result into the product's image gallery so it is there on the page, not only in the popup.
Bring your own storage
From Starter up, images can go to a bucket you own instead of ours - Amazon S3, Cloudflare R2, DigitalOcean Spaces, Backblaze B2, or anything else speaking the S3 API. You give the endpoint, region, bucket, an access key pair, and the public address those files are served from.
Two things are worth knowing before you switch. Only images created from that point on go to your bucket: everything already stored stays with us and is deleted on your retention window, so no image already on a page ever breaks. And the bucket has to be publicly readable, because shoppers load these images directly - the Test connection button writes a file, reads it back over your public address and deletes it, so you find out before your customers do.
The app's privacy policy reflects all of this. If you enable saved photos, make sure your own store policy mentions it too.