Privacy Policy
Last updated: July 30, 2026
1. Who we are
AI Fashion Suite (“the App”) is developed and operated by AXICOM S.R.L. (“we”, “us”).
Roles. For shopper data, the merchant whose store you are visiting is the data controller and we act as their processor: we handle that data to deliver the features the merchant switched on, under their instructions. For the merchant’s own account, billing and support data we are the controller.
2. What the App accesses on your store
The App requests these Shopify access scopes, and no others:
write_products - reads product titles, images, prices, variants and inventory so the storefront features can work; writes only when a merchant explicitly asks us to push an AI Studio image into a product’s media gallery.read_themes - checks whether the App’s block is actually enabled in the live theme, so the admin can tell a merchant when it is not.read_orders and read_all_orders - powers the order bonus (extra fittings for buyers), revenue attribution in Analytics, verified review badges, and Find My Size’s ability to learn from what sizes were kept. read_all_orders only lifts the 60-day window on the same data.write_customers - only used by the optional Shopify Segments destination and by review/back-in-stock tagging: a captured contact becomes a tagged customer in the merchant’s own store.
We do not request access to store administration, staff accounts, payments or anything else beyond the list above.
3. Shopper data, feature by feature
Every feature below is off unless the merchant turns it on. A store using only the fitting room never creates any of the other records.
3.1 The photo a shopper uploads (fitting room)
- The photo is sent to Google Cloud’s Vertex AI image model to generate the preview.
- By default we do not store the raw photo. Only a one-way cryptographic hash of it (combined with the product image) is kept, purely to recognise an identical repeat request and avoid generating it again.
- Optional photo saving. A merchant may enable a feature that lets a shopper save their photo for reuse. The photo is stored only if the shopper explicitly ticks the consent box next to the uploader. It is kept solely for that shopper’s own reuse, never used for anything else, and deleted on the merchant’s retention schedule. No merchant setting alone is enough, and no consent alone is enough - it takes both.
- The generated result image is stored so a repeat visit is instant, until deleted as described in Section 7.
3.2 Body measurements (Find My Size)
- Shoppers may enter measurements and fit preferences (for example height, weight, age range and body shape) to receive a size recommendation. The recommendation is computed from the merchant’s own size charts - no external AI is involved.
- Guests are never stored. A guest’s answers stay in their own browser. Only a signed-in shopper who chooses to be remembered has their answers saved, and the merchant can switch remembering off entirely.
- Anonymous, aggregated statistics (how a garment’s sizing runs across many shoppers) are derived from purchases and returns. These hold no identifier for any individual.
3.3 Reviews
- When a shopper submits a review we store the rating, title, text, the display name they typed, any photos they attached, and optionally their email address. The email is never published; it is used to match the review against an order for the “verified buyer” badge and to let the merchant reply.
- Optional fit questions (how the size ran, which size was bought) are stored with the review and feed the public “true to size” figure and Find My Size. A separate question rating our AI preview is internal quality telemetry and is never shown as a product review.
- Review requests. If the merchant enables post-purchase review requests, we record which order became eligible and when it was asked. The email itself is normally sent by the merchant’s own tools: we tag the customer in their store and their Klaviyo flow or Shopify Flow does the rest.
3.4 Back in Stock
- A shopper who asks to be told when a variant returns gives us their email address, which we store with the product and variant they asked about, and their Shopify customer id if signed in.
- That alert is transactional - they asked for it. Agreeing to marketing is a separate, unticked question, and only that separate consent feeds any marketing destination.
3.5 Wishlist
- We store the products saved, against a hashed shopper identifier. A wishlist never asks for an email address - saving something is not subscribing.
- Sharing is opt-in and revocable. A share link exists only once the shopper creates one, uses a random token rather than the list’s id, and can be withdrawn without destroying the list.
- Price-drop alerts are a separate opt-in and need an address we can reach. Nobody consents to email by tapping a heart.
3.6 Email capture (“save your look”)
- If the merchant enables it, a shopper may enter their email to have their try-on result sent to them. We store the address, the product they were viewing and where the contact came from.
- These contacts belong to the merchant and may be forwarded to the destinations they configured - see Section 6.
3.7 Technical & usage data
- A per-browser identifier for guests, or the Shopify customer id when signed in. Both are stored hashed, so the records can serve a returning shopper without us holding the raw id.
- Storefront events (widget shown, opened, fitting generated, added to cart) and per-generation timestamps, status and cost, used for the merchant’s analytics and for our quota enforcement and billing.
- Rate-limiting and abuse-prevention signals, including a coarse browser fingerprint and IP-derived counters for guest limits.
- Orders are matched to prior try-ons to produce revenue attribution. We read order totals and line items; we never receive payment details.
4. Merchant data
- Account. Store domain, plan, quota, settings, and the Shopify session token that authorises the App.
- AI Studio. A model photo the merchant uploads is sent to Vertex AI to produce an on-model product image. The upload itself is not retained; the generated image is stored like any other result.
- Support. Messages sent through the in-app chat, with the name and email from the pre-chat form and any screenshot attached, are stored so the conversation has a history.
- Third-party credentials. API keys a merchant enters for Klaviyo, Omnisend or their own storage bucket are stored to perform the sync they enabled, and are never shown back in full or used for anything else.
5. Email we send
Some features send email on the merchant’s behalf - back-in-stock alerts, price-drop alerts, a try-on result sent to the shopper who asked for it. These go out through Amazon SES from our own sending domain.
- Anything that is not strictly transactional carries a one-click unsubscribe header and an unsubscribe link.
- We keep a suppression list of addresses that bounced or marked a message as spam, and we never send to them again. This list is shared across all stores using the App, because sending reputation is shared too. It holds the address, why it was suppressed and when.
- We do not send marketing email of our own to shoppers, and we never use a shopper address collected in one store to reach them in another.
6. Where data goes
Our sub-processors
- Google Cloud Platform - AI image generation (Vertex AI), application hosting, image storage and encrypted backups.
- Neon - the application database.
- Amazon Web Services (SES) - email delivery.
- Shopify - authentication, billing, and the App Proxy that connects the storefront to the App.
Destinations the merchant chooses
These are off by default. When a merchant switches one on, they instruct us to forward contacts to a service they control and are responsible for:
- Shopify Segments - the contact becomes a tagged customer in the merchant’s own store.
- Klaviyo or Omnisend - added to a list in the merchant’s own account, using their API key.
- Outbound webhook - each new contact is POSTed to an HTTPS endpoint the merchant specifies, optionally signed.
- Own storage bucket - a merchant may point image storage at their own S3-compatible bucket, after which new images are written there rather than to ours.
We do not sell shopper or merchant data to anyone.
7. Retention
- Raw uploaded photos - not retained. Where the merchant enabled photo saving and the shopper consented, the saved photo is kept for that shopper’s reuse and deleted automatically on the merchant’s chosen schedule (1–90 days).
- Generated images, try-on history and match hashes - kept while the store has the App installed, subject to the same retention window, and deleted within 30 days of uninstallation.
- Find My Size profiles - kept for a signed-in shopper until they or the merchant remove them.
- Reviews - kept while published or until the merchant deletes them; they are the merchant’s store content.
- Back-in-stock requests - deleted once the alert has been sent and the request has run its course, or on request.
- Wishlists - kept while in use; inactive lists are pruned.
- Contacts and analytics events - kept while the App is installed, and deleted within 30 days of uninstallation.
- Suppression list - kept indefinitely. Deleting it would mean emailing addresses that already told us to stop.
- Shop and billing records - kept for the duration of the subscription plus the period required by applicable tax and accounting law.
- Backups - encrypted database backups are retained for a short rolling window (a configurable number of days) and then destroyed, so deleted data can persist in a backup briefly after deletion.
8. Shopify compliance requests
We implement Shopify’s mandatory privacy webhooks. When a shopper asks a merchant for their data, we return everything we hold for that shopper (customers/data_request). When a merchant asks us to erase a shopper, we delete their fittings, saved photos, size profile, wishlist, contacts and requests (customers/redact). When a store is closed we erase that store’s data (shop/redact).
9. Legal basis & purpose
We process this data to deliver the service the shopper actively requested, to perform our contract with the merchant, and for our legitimate interest in operating, securing and billing the App. Optional photo storage, marketing consent and price-drop alerts rest on the shopper’s explicit consent, which they can withdraw at any time.
We do not use shopper photos, reviews or measurements for advertising, profiling, or to train machine learning models, ours or anybody else’s.
10. Children
The App is not directed at children. Shoppers should not upload photos of minors, and merchants are responsible for the age policy of their own storefront.
11. International transfers
The application, the AI generation and image storage run on Google Cloud in the European Union (europe-west1); email is delivered by Amazon SES in Ireland (eu-west-1). Where a provider processes data outside your region, we rely on their standard contractual clauses and data processing terms. A merchant-chosen destination (Section 6) may be located anywhere; that transfer is the merchant’s to assess.
12. Your rights
Merchants and shoppers in the EU/EEA, UK and other regions with data protection laws have the right to access, correct, delete or export their data, and to object to its processing. Shoppers should normally contact the store they used; we will support that merchant in answering. You can also write to support@template-tuners.com directly, and we respond within 30 days.
13. Uninstalling the App
When a merchant uninstalls, we receive Shopify’s app/uninstalled webhook and schedule deletion of that store’s data as described in Section 7. Earlier deletion can be requested at any time.
14. Security
Data is encrypted in transit (HTTPS/TLS) and at rest. Access to production data is restricted to the personnel who operate the App. Storefront endpoints are authenticated through Shopify’s signed App Proxy, so a shopper’s identity cannot be forged by the caller. Backups are written to a private bucket that is never publicly readable.
15. Changes to this policy
We update this page whenever our data practices change, along with the “last updated” date above. Material changes are announced inside the App.
16. Contact
Questions? support@template-tuners.com
