Bring the try-on experience to your physical store with Antla Retail.

Blog
October 26, 2026

Customer Photo Handling in Virtual Try-On: Merchant Checklist

Customer photos in a Shopify virtual try-on need a map of upload, retention, and deletion. Use the vendor policy and Shopify privacy docs, not a guessed clock.

Aaron
Aaron
12 mins read

Customer photos in a virtual try-on app are personal data. Map the upload, where processing happens, and the document that states retention, then quote that document on the product page. For Antla, the privacy policy states: Images are deleted and not accessible within 72 hours. Do not invent a different clock for Antla or for any other vendor. Shopify’s privacy rules tell you which questions a policy must answer, and storefront copy has to match the policy you can link.

Person at a back-office desk holding a printed portrait beside a locked filing drawer, Antla marked on the wall

The photo is the data. The lock is the part most product pages skip. Editorial image in Classic Antla disposable-camera style.

Shoppers ask a blunt question: what happens to my picture? The useful merchant answer is also blunt, and it has to be true. A sentence like “deleted instantly” is a product claim. If your vendor’s privacy policy does not say that, you do not get to say it on the product page because it sounds reassuring.

This is a checklist for the photo itself. It is not a substitute for counsel. For Antla, quote the published image line rather than paraphrasing it into “deleted instantly” or “never stored.”

Map upload and processing

Draw the path before you write copy. On a typical Shopify product page the path is short, and each step is a different kind of data.

  1. The shopper chooses a file or takes a photo. That file is an image of a person. Treat it as personal data even when you never ask for a name.
  2. The browser sends it to the try-on app. Processing is not “on the theme.” The theme shows a button. Generation happens in the app’s systems.
  3. The app returns a preview. The preview is a new image derived from the shopper’s photo and your product photo. It is still about that person.
  4. Optional extras. An email field, a share action, or a saved avatar is a second collection. Do not bury it inside the sentence you wrote for the photo.

Antla documents the storefront moments you can listen for: antla_image_upload_success, antla_image_upload_error, antla_image_generated_success, and antla_image_generated_error, alongside modal open and close. The payloads and names are in the custom events docs. Use them to see that an upload happened. They are not a privacy policy, and they do not tell you how long a file is kept.

A returning browser can be a surprise. If the shopper uploaded a photo before and has not cleared cookies, Antla can reload that image in the background so they do not pick a file again. That is a convenience. It is also something to say out loud: this browser may remember the last photo until the cookie is cleared. Remembering a photo in the browser is not the same statement as a server retention period. Do not collapse the two into one sentence.

You may also ask for an email in exchange for more try-ons, with Klaviyo as the usual destination. That email is personal data collected for a marketing purpose. It needs its own line in the policy and its own consent, separate from the photo. How those events should and should not feed flows is covered in try-on data for Klaviyo and Postscript.

The product image is yours. The shopper image is not. Photography versus AI try-on is about the garment file. This checklist is about the person in the other file.

Review retention and deletion

Read the vendor’s privacy policy and quote it. Do not translate it into a number of hours unless the policy itself uses that number.

Antla’s privacy policy, the October 2026 text, has two retention sentences. Personal information “is retained as long as necessary to fulfill the purposes we collected it for, including for the purposes of satisfying any legal, accounting, or reporting requirements.” On images specifically, the same privacy policy states: Images are deleted and not accessible within 72 hours. Quote that image line when you mention photos. Do not rewrite it as “deleted instantly,” “never stored,” or a number of hours you prefer. The policy also says people can request access, correction, or deletion, and it gives a contact: aaron@antla.io.

A separate Antla FAQ says images “are processed securely and deleted automatically after use unless the shopper opts to save their avatar,” and that Antla complies with GDPR and Shopify’s data policies. That sentence is on the try-on FAQ. The numbered clock for photos is the privacy-policy line above, not the FAQ. If your counsel wants a different number in your own policy, ask Antla for it in writing. Until that reply exists, storefront copy should quote the published 72-hour sentence, not a made-up SLA.

Shopify’s side is more specific, and it is about apps, not about a marketing sentence you prefer.

Shopify requires App Store apps to subscribe to three mandatory compliance webhooks:

WebhookWhen Shopify sends itWhat it is for
customers/data_requestA customer asks the store to see their dataThe app must provide the data it has to the merchant
customers/redactA customer asks for deletionThe app must delete or redact, with Shopify’s timing rules
shop/redact48 hours after the merchant uninstalls the appThe app can erase data for that shop

Shopify tells apps to confirm the webhook and complete the action within 30 days, unless the law requires the data to be kept. On customers/redact, Shopify’s own send timing depends on orders: if the customer has not ordered in the past six months, Shopify sends the payload 10 days after the request. If they have ordered, Shopify withholds the webhook until six months have passed. Those intervals are Shopify’s instructions to apps. They are not an Antla promise about how long a try-on photo remains on a server. Cite them as platform mechanics. Do not paste “30 days” or “48 hours” into your product-page copy and attribute it to Antla.

When you uninstall, assume shop/redact is the deletion trigger the app is supposed to act on. Export any merchant-side reports you need before you uninstall. Do not export shopper photos into a shared drive “just in case.” That drive becomes a new retention problem you now own.

Deletion requests that arrive by email, not through Shopify’s customer privacy tools, still need a path. Publish who handles them (you, the vendor, or both) and the address. Antla’s policy points privacy requests to aaron@antla.io. Your policy should say how a shopper reaches you, and that you will pass a photo request to the app vendor rather than pretending the theme stores the file.

Consent copy fails when it describes a different product than the one you installed.

Write four sentences a person can read on a phone, next to the upload, not in a footer:

  1. What they are uploading. A photo of themselves, used to generate a preview of this garment.
  2. What the preview is. A simulation of appearance. It does not measure their body or decide a size. Say that here even though the longer version lives in your fit content.
  3. What you do with the file. Match the policy: processed to make the preview. For Antla, quote: Images are deleted and not accessible within 72 hours. For any other vendor, use their published sentence, not a number you typed because it sounded better.
  4. How to object or delete. The request address, and the fact that a cookie may reuse the last photo in this browser until they clear it.

Antla can require shoppers to accept terms before generation and can link those terms to your privacy policy. You choose whether processing waits for the click. The toggle does not draft the four sentences. You do.

Keep this separate from the cookie banner. Shopify’s customer privacy tools govern analytics and marketing cookies. A photo upload is an active submission of an image. Declining analytics does not, by itself, explain the photo, and accepting analytics does not, by itself, authorize a face upload. If your banner and your try-on step contradict each other, fix the try-on step. Shoppers do not read them as one agreement.

If you let people share a preview, say who can see it. Sharing a try-on is a growth mechanic. It is also a disclosure: a shared image leaves your page. The share control should not be the first time they learn the picture can travel.

Regions differ. Antla’s policy calls out access, correction, deletion, and portability, plus GDPR rights for EEA, UK, and Swiss users (including complaint to a supervisory authority) and CCPA rights for California users, including opt-out of sale. Your store may have its own duties on top. The copy on the button should not try to recite every statute. It should not hide the request path either.

Verify vendor terms

Shopify’s privacy requirements for apps are written for developers, and they are still the right checklist for a merchant buying an app. Shopify expects a public privacy policy on the App Store listing, and recommends that it answer, in plain terms:

  • What the app collects through Shopify’s APIs, from you, and directly from your customers (including cookies and logs).
  • How that information is used, and whether any use is unrelated to providing the app.
  • How long data is stored or retained.
  • Whether data is stored or processed outside Europe, if that matters to your shoppers.
  • How a merchant can ask a follow-up question. Some jurisdictions also expect a physical address.

If the policy you were handed skips retention, you do not “fill it in” with a guess. You ask the vendor, and you wait to launch the photo step until the answer is something you can link.

Protected customer data is Shopify’s program for customer fields such as name, email, address, and phone. The requirements emphasize minimum data, telling merchants what personal data is processed and why, and having a privacy policy or data protection agreement. A try-on photo may sit beside those fields or apart from them, depending on what the app requests. Read the App Store listing’s data-access section and the policy together. The listing is the scope. The policy is the promise. If they disagree, the disagreement is the work, not a footnote.

Use this pass on any vendor, including Antla:

QuestionWhere the answer must liveFail if
What file do you collect?Policy and the upload stepThe page says “photo” and the policy says nothing about images
Why?PolicyThe only purpose you can find is “improve our services,” with no preview purpose
How long?Policy, in the vendor’s wordsYou are about to type a number they did not publish
Training?Policy or a written replyYou cannot tell whether uploads train a model
Who else sees it?Policy’s sharing sectionSubprocessors are unnamed and support will not list them
Deletion?Policy plus Shopify webhook behaviorUninstall and customer requests have no owner
Contact?PolicyThe only address is a contact form that does not mention privacy

Antla’s policy says information is collected to let the service function, within Shopify’s restrictions, and is not used for other purposes without explicit consent. It also says information may be shared with service providers who assist delivery, for legal requests, and in a business change. That is the published scope. It is broader than “the photo never leaves the phone,” so do not claim on-device processing unless a current document says the processing is on-device. The honest line is: the photo is sent so a preview can be generated, under the policy you link.

I would not launch a photo upload on a policy you have not read in the last quarter. Policies change. Diff the October 2026 Antla text against whatever is live on the day you ship copy.

What this checklist will not settle

It will not tell you whether your store is the controller, the vendor is the processor, or you are both, in a given country. Shopify’s privacy pages say the same thing in their own caution: they are platform requirements, not legal advice to you. Take the four sentences and the policy link to counsel if you sell in the EEA, the UK, or US states with their own privacy laws.

It will not invent a retention SLA for a vendor that has not published one. If a stakeholder asks how many hours for Antla, the accurate answer is the privacy-policy sentence: Images are deleted and not accessible within 72 hours. Shopify’s webhook rules are about when apps must respond to platform requests. Those platform intervals are not a substitute for the vendor’s image line.

It will not make a shared screenshot private again. Say that before you turn sharing on.

What to do before the next upload

Open the live privacy policy, the App Store data-access list, and the four sentences on your product page. Highlight every number of hours or days in the product-page copy. If the policy does not contain that number, delete the number. Link the terms step to the policy. Put aaron@antla.io, or your own privacy inbox, where a deletion request can actually land. Then upload one photo yourself and read what you just agreed to, on a phone, with the cookie banner declined.