Body-image data is sensitive. We treat it that way.
A virtual try-on works with a shopper's photo and body proportions - some of the most personal data a retailer will ever touch. This page states plainly what we collect, why, how long we keep it, and how it is protected.
Photos deleted after the session
A try-on needs the image only for as long as the render takes. Shopper photos are deleted after the session rather than kept on file - body-image data is too sensitive to hold onto without reason.
Encrypted in transit and at rest
Data moving between the shopper, the storefront and the engine is encrypted in transit, and anything held during processing is encrypted at rest.
Scoped, least-privilege access
Access to shopper data is limited to what a given function needs to do its job. Body and photo data is not a general-purpose dataset inside MAAYLZY.
What is collected, why, and how long it stays.
| Data | Why it is used | How long it is kept |
|---|---|---|
| Shopper photo or camera frame | To render the garment onto the shopper | Deleted after the try-on session |
| Body proportions / measurements | To recommend a size and flag fit mismatches | Retained only as needed for the recommendation, then minimised |
| Try-on interactions | To power retailer analytics on demand and drop-off | Aggregated for reporting, not tied to an identifiable shopper |
| Retailer catalog data | To render items and build complete-the-look | Kept in sync with the retailer's inventory |
How the data is kept safe.
- Encryption in transit for data moving between shopper, storefront and engine
- Encryption at rest for anything held during processing
- Shopper photos deleted after the try-on session
- Access scoped to the function that needs it, on a least-privilege basis
- Analytics reported in aggregate, not against an identifiable shopper
Our compliance posture, honestly
We describe only where we actually stand today. As a growing company, we are building our data-protection practices deliberately around the sensitivity of body-image data, and we will not claim certifications we do not hold. If you have a specific compliance requirement for your market, raise it with us and we will tell you plainly what we can and cannot meet right now.
A shopper's likeness is theirs. We hold it only as long as a render needs it.
Have a data question before you start?
Tell us your market and your requirements, and we will answer plainly on storage, retention and access.
A live render, settled at rest