Privacy

What the try-on does with a shopper's photo, what your page can and can't see, and what Labbesne keeps.

This page describes how the software behaves. It is not a contract, a data processing agreement or legal advice. What Labbesne commits to is in your agreement with us. For anything this page doesn't answer, write to hello@labbesne.com.

The shopper's photo

• The shopper agrees first. The try-on's first screen says what will happen, and no photo is taken or sent before they agree.
• The photo is taken inside the try-on's frame, which is served by Labbesne, not by your page.
• It is sent to Labbesne's server to make one picture. The server passes the photo and the product's picture to the image model that makes the result.
• Labbesne does not store the photo or the result. The server holds no file storage for them. The result is passed straight through to the shopper's browser.
• The shopper can save the result to their own device. Nothing else leaves the try-on.

The image model is run by a provider Labbesne uses. This page says nothing about that provider's own handling of what it is sent. Ask us which provider serves your account and under which terms, before you put try-on in front of your shoppers.

What your page can see

Your page and the try-on are separate: the try-on runs in a frame from another origin, and the browser keeps the two apart.

Your page gets	Your page never gets
That the try-on opened, closed, and which step it reached	The shopper's photo
That a result is on screen, and for which product	The result picture
A request to add the product to the bag, or to go to checkout	Anything that identifies the shopper

See Events for exactly what each one carries.

What your page sends to Labbesne

• Your store's key.
• The product: its name, picture address, and the other fields your page has, including the product page's address.
• Your site's address (not the page's), which the browser sends when it loads the frame.

The script does not read your cart, your customer's details or your shop's cookies.

What Labbesne keeps

For each try-on a shopper makes, one record:

• which store and key it was for,
• when it was made, whether it worked (with an error code if it didn't), and how long it took,
• which model made it, the credits it took and what it cost,
• which product it was: your product id, or the product page's address without its query string.

No photo, no product picture and no result is in that record, and nothing that says who the shopper was.

Like any web request, the try-on's requests carry the shopper's network address. Labbesne uses it to limit abuse. See Rate limits.

Cookies

The try-on's frame sets no cookies, and the script sets none on your site.

Counting

• Labbesne's own counts, on the dashboard's Usage page: how often the button was shown, and how many shoppers opened the try-on, added a photo, saw a result and added to bag. They are counted without a cookie and keep nothing about a shopper, so one shopper who looks at five products counts five times.
• Your own analytics. If your page has a dataLayer, the script pushes the same steps to it, with the product and nothing about the shopper. What your tags do with them is up to your setup and your consent rules. You can turn it off. See Analytics.

The question before the button

Before it adds a button, the script asks Labbesne whether try-on can start. That request carries your store's key and nothing else: no cookie, and no address of the page it came from.