Your data
Privacy Policy
Last updated: 2 November 2026
Lookvert is a Shopify app that generates virtual try-on images for fashion stores. This policy explains what data the app processes, who it is shared with, and how long it is kept.
Lookvert acts as a data processor for the merchant who installs it. The merchant is the data controller for their shoppers' data and remains responsible for their own privacy notice.
What we process
Merchant data
| Data | Why |
|---|---|
| Store domain, app session tokens | Authenticating the app with Shopify. Session tokens are encrypted at rest. |
| Product titles, descriptions, images, product type, vendor, metafields | Deciding what the garment is, so the generated image keeps its colour, pattern and cut. |
| Usage and billing counters | Metering generations against the merchant's plan. |
Shopper data
| Data | When |
|---|---|
| Shopify customer ID | Only when the shopper is logged in. Guests are not identified by name or account (see the device identifier below). |
| An anonymous browser identifier | A random identifier stored in the shopper's browser, so their saved looks and try-on images stay available across tabs in that browser. Clearing the browser's data removes it. When a shopper logs in, the looks saved in that browser are linked to their Shopify customer account so they can see them on other devices. |
| A device identifier | Only for a guest who agrees and uses "try it on me": a one-way hash of browser and device characteristics (such as time zone, language, screen and graphics characteristics), used only to apply the merchant's daily limit on free photo try-ons. It cannot be turned back into those characteristics, is different for each store, and is not used for advertising or to follow the shopper across sites. |
| A photo the shopper uploads of themselves | Only if the shopper chooses "try it on me" and uploads one. This is optional — the app works without it. The photo is checked automatically before it is processed (see Children); a photo that fails the check is discarded. A photo that passes is used only while the try-on image is being generated and is deleted as soon as generation ends, whether it succeeds or fails. |
| Images generated from that photo | The result shown back to that shopper. |
| A record of the shopper's consent | When the shopper agrees before their first photo try-on: the anonymous browser identifier, the store, the Shopify customer ID if logged in, the policy version shown, and the time. This is our evidence that consent was given. |
| Widget interaction events | Counting opens and generations so merchants can see whether the feature is used. |
We do not read the merchant's orders, and the app does not
request the read_orders permission.
Visitors to this website
Our hosting provider, Vercel, processes technical request information to deliver and secure this website. The website does not include a marketing analytics or advertising tracking script.
Support requests
When you email us, we receive your name and email address, your message, and anything you attach or include. We use this information to respond to you, keep a record of your request, and improve our support and help content. We are the controller of this information.
Please do not send passwords, API tokens, payment card details, or shopper photos by email. If a request includes shopper information, we use it only to handle that request.
| Provider | What it does |
|---|---|
| Cloudflare (Email Routing) | Receives email sent to our Lookvert addresses and forwards it to our inbox. |
| Google (Gmail) | Stores support email and lets us read and reply to it. |
| Resend | Delivers our replies. |
| GitLab | Stores our internal records of support requests, in a private project. |
We keep support email and internal support records for up to 2 years after a request closes, unless we need them longer for a legal claim or legal obligation. To ask us to delete them, email privacy@lookvert.com.
Third parties
Generating an image requires sending the product photo — and, when the shopper uploads one, their photo — to an AI provider. The providers process the image to produce the result and do not receive the shopper's identity.
| Provider | What it receives |
|---|---|
| Google (Gemini API) | Product photo, shopper photo when one is uploaded (first to check it, then to generate the image), and the text prompt describing the garment. |
| OpenAI | Product photos, for the "Shop the Look" composite image. |
| Cloudflare (R2) | Temporarily holds uploaded photos during processing and stores generated images. Remaining uploads are scheduled for expiration after 1 day; lifecycle deletion runs in the background. |
| Vercel | Runs the app. |
| Neon | Hosts the database. |
| Resend | Sends summary emails to the merchant. Shopper data is not included. Support replies are described above. |
How long we keep it
| Data | Retention |
|---|---|
| Shopper-uploaded photos | Deleted as soon as generation ends. As a safeguard, the storage bucket is configured to expire remaining uploaded photos after 1 day. Lifecycle deletion runs in the background and can complete after the expiration time. |
| Images generated from a shopper's photo | Scheduled for automatic expiration after 7 days, or immediately when the shopper deletes them in the try-on widget. They are held in a private bucket, not served publicly. |
| Try-on images generated from the merchant's product photo | Kept until the merchant removes the product from the app or uninstalls. These show a synthetic model generated for the garment — they are not photographs of a real shopper. |
| Saved looks (My Looks) | Deleted 7 days after they are saved, or when the shopper's data is erased. |
| Try-on records and storefront usage events | The anonymous shopper identifier is removed after 13 months. The remaining records (which product, when) no longer identify anyone and are kept for the merchant's statistics. |
| Sharing | Sharing sends the image file directly from the shopper's device (or downloads it). Lookvert does not create a public copy or link. |
| Consent records | Kept for 5 years as evidence that consent was given. They are not removed by erasure requests (GDPR Art. 17(3)(e)). |
| Device identifiers | Stored with the shopper's try-on allowance and deleted with the store's usage records. |
| Merchant-generated product images and rotation files | Kept for one year from generation, including files in use on the storefront, or 90 days after subscription cancellation without resubscribing, whichever comes first. Resubscribing does not restart the original one-year period. Expired files are removed; generation and billing records follow their separate retention rules. |
| Merchant configuration and usage records | Deleted when we process Shopify’s store erasure request, which Shopify sends approximately 48 hours after uninstall. Billing and consent records have the separate retention periods described here. |
| Billing records | Retained after uninstall to meet accounting and tax obligations (GDPR Art. 17(3)(b)). |
Shopper rights
Shoppers can delete their try-on images at any time from the try-on widget, without making a request.
Formal requests are made through the merchant's store, and Shopify forwards them to us automatically. We respond to all three mandatory requests:
| Request | What happens |
|---|---|
| Access to data | We return the list of try-ons that shopper made, their remaining try-on allowance, and how many generated images are on file. We do not return the image files — they sit in a private bucket and expire within 7 days; returning them would widen exposure rather than reduce it. A merchant who needs the files can ask us. |
| Erasure | We delete that shopper's try-on records, saved looks, try-on allowance and generated images, and remove their identifier from any order linked to a try-on. |
| Store erasure | We delete that store's data. Other merchants are unaffected. |
One limit, stated plainly: uploaded photos are not kept, so there is nothing to erase. Images generated for a shopper who was not logged in cannot be linked to any person, by us or by Shopify, so no erasure request can reach them; the shopper can delete them in the widget, and they are otherwise removed after 7 days.
Biometric data
We do not use facial recognition. We do not create faceprints, face templates, face embeddings, or scans of face geometry, and we do not collect biometric identifiers or biometric information as defined by laws such as the Illinois Biometric Information Privacy Act (BIPA). The automated check on an uploaded photo only produces a few results — such as how many people it shows and whether they appear to be an adult.
Children
The try-on feature is for adults. Every photo a shopper uploads is checked automatically before it is processed, and it is rejected — and not stored — if it appears to show a person under 18, shows no person or more than one person, or contains inappropriate content. If the check itself cannot run, the photo is rejected rather than let through.
The check is automated and can be wrong. If you believe an image of a child was generated, contact us at the address below and we will delete it.
Security
- Generated images of shoppers are stored in a private bucket, not served publicly; uploaded photos are deleted once generation ends.
- App session tokens are encrypted at rest.
- Requests from the storefront are signed and verified; webhooks from Shopify are verified by HMAC.
- Public image addresses are randomised so they cannot be guessed or enumerated.
Who we are
Lookvert is operated by an independent developer. We do not have a postal address for correspondence; please contact us by email.
Contact
Questions about this policy, or a data request a merchant needs us to action directly: privacy@lookvert.com. We reply to data requests within 30 days.