Antla uses shopper photos only to power virtual try-on and related features you enable (such as email, share, or Klaviyo more-looks). This article summarizes how photos are used, how long feed content is kept, and what to know for consent, GDPR, and uninstall—at a high level for merchants.
When a shopper uploads a photo:
The image is used to generate their try-on look for the product they selected.
Successful looks may appear in your Try-On Feed so you can review activity.
Photos are processed for generation; they are not used to invent unrelated profiles outside Antla’s try-on features.
Merchant Studio uploads follow the same idea for your own creative generations and appear in Studio Feed instead of the shopper feed.
Encourage clear photo guidance and transparent on-site copy so shoppers understand why they are uploading. Customize messaging in Customize On Site Design.
More looks consent is the shopper’s opt-in to let Antla reuse their try-on photo for additional personalized looks—especially for marketing paths such as Klaviyo recommend flows.
You can configure the consent text in On Site Design (for example, “Send me more looks that suit me!”).
When a logged-in or email-identified shopper opts in, Antla stores that consent so later recommendation emails can generate new outfits on the same base photo.
Without consent, do not expect more-looks / recommend marketing to reuse that photo.
Flows that only show the original try-on still depend on your broader email and Klaviyo setup; recommendation flows that generate new looks rely on consent plus matching audience rules.
Antla periodically cleans older try-on feed records so shops are not retaining endless photo history by default.
The Try-On Feed is cleaned on a recurring schedule (older entries are removed after a retention window measured in days).
Related operational cleanup (for example anonymous profiles without recent activity) also runs on a schedule.
Exact windows can change as product policy evolves; treat the feed as an operational gallery, not a permanent archive. Export or save any creative you need to keep outside Antla (for example from Studio) before you rely on long-term storage.
Emails collected through try-on create a Customer request and may sync toward Shopify / Klaviyo depending on your settings.
Discount codes tied to try-on follow your discount configuration and email timing.
Klaviyo profile properties may include marketing / image consent flags when those features are connected.
See Sharing looks & collecting emails, When customers receive emails, and Klaviyo flows (show try-on / recommend).
If you operate in regions covered by GDPR or similar laws:
Be transparent in your storefront privacy policy about virtual try-on and photo use.
Honor shopper requests that come through Shopify’s standard customer data workflows (access / erasure) as required for your app stack.
Antla participates in Shopify’s app privacy webhooks for customer and shop data requests; processing is handled as part of normal app compliance—not something you configure line-by-line in the UI.
For legal interpretation, rely on your counsel and Shopify’s merchant guidance; this Help article is operational, not legal advice.
If you uninstall Antla:
The storefront Try On button and Tapcart block stop working once the app / block is removed.
Theme app embed and related extensions should be disabled or cleaned up in the theme editor and Tapcart Studio.
Historical feed and account data are subject to Antla’s retention and deletion practices after uninstall; do not assume indefinite access to past try-ons.
Disconnect Klaviyo in Antla before or when removing the app if you want flows driven by Antla to stop cleanly.
Reinstalling later typically requires re-enabling the embed, confirming Funnels, and reconnecting integrations.
On Site Design consent and terms copy match your brand policy
Privacy policy mentions virtual try-on / photo upload
More-looks / Klaviyo recommend flows only run with consent as intended
Team knows the Try-On Feed is cleaned periodically
Uninstall plan includes theme embed, Tapcart block, and Klaviyo
