Privacy Policy

Last updated: November 5, 2026

TryOnIA ("the App", "we", "us") is a Shopify app operated by DevCloud Software LLC that lets shoppers preview products on themselves using AI-generated virtual try-on. This policy describes what data we receive, how we use it, and how we protect it.

1. Data we receive from merchants

When a merchant installs TryOnIA, Shopify grants us an access token for the permissions the merchant approves (products, themes, orders and discounts) and sends us the webhook events we have subscribed to:

• Product events — products/create, products/update (we read the product image and title to feed the AI).
• App lifecycle — app/uninstalled, app_subscriptions/update, app/scopes_update.
• GDPR compliance — customers/redact, customers/data_request, shop/redact.

With the token we read the store's products, check the theme for the app embed, look up orders already attributed to a try-on (to report refunds), and create single-use discount codes when the merchant turns on Share-for-discount or the discount in the try-on email. We also keep the store's name, contact email and domain, and the plan the merchant chose. We do not subscribe to order, customer, inventory, or fulfillment events.

2. Data we receive from shoppers

When a shopper opens the try-on modal on a product page and uploads a photo, we receive:

• The selfie image file they chose to upload.
• The Shopify product they were viewing (product id, title and image URL).
• Their storefront locale (and country when the storefront provides it).
• A SHA-256 hash of their User-Agent string.
• An anonymous shopper identifier: a SHA-256 hash of a server-side secret, their IP address and User-Agent, used only to apply the merchant's per-shopper try-on limit. We do not store the IP address itself.
• Their Shopify customer id, when they are logged in to the store (used for the same limit and to show them their own past try-ons).

We do not ask for names, phone numbers, or other directly-identifying information. Three things are optional and only happen when the merchant turns them on and the shopper chooses to:

• Email — a shopper can enter their email to receive their try-on photo (and, if the merchant offers one, a single-use discount code). We store it with the try-on session, send that one email through SendGrid, and pass it to the merchant's Klaviyo list if the merchant connected Klaviyo. To stop the same address from receiving more than one code we keep a salted hash of it (not the address).
• Size recommendation — a shopper can enter their height and weight to get a suggested size; we store them with the session.
• Product-page carousel — after seeing their result a shopper can tick a box to show it on that product's page. It is shown blurred unless the merchant turned blurring off, the merchant can hide it, unticking removes it, and it disappears when the photos are deleted at the end of the retention window.

Sharing — the result screen has a Share button. Where the shopper's browser can, it shares the result image itself; otherwise it shares a link. Tapping Share creates that link, for that try-on only: a page that shows the AI result and the product's name, never the photo the shopper uploaded. Anyone with the link can open the page; it is not listed anywhere and asks search engines not to index it. It stops working 90 days after the try-on, or sooner when the result is deleted at the end of the retention window, and the merchant can turn share links off. The merchant can copy the same link from the admin gallery.

3. How shopper photos are processed

To generate the try-on result, the selfie and the product image are sent to Google's Gemini API (Google LLC), which returns the rendered result. We send them only for that request; Google's handling of data sent to the API is governed by the Gemini API terms of service.

Selfies and results are stored on a private storage volume of the server that runs TryOnIA, on DevCloud's own hosting platform. Every image link we hand out is signed and expires (10 minutes for a selfie, 24 hours for a result). A selfie is never public; the one public page is a share link (above), which shows the result only and signs its image afresh each time it is opened. The result image is stored alongside the selfie until the merchant's configured retention window elapses (default 7 days; minimum 1 day; maximum 30 days). After that window, an hourly job:

• Deletes the selfie file from our storage.
• Deletes the result image file (and its blurred carousel copy, if any).
• Keeps the session record with empty image links so the merchant's analytics totals remain accurate. The record (including the shopper's email, if they gave one) is deleted with the rest of the shop's data on shop/redact, and its personal fields are cleared on a customers/redact request.

The hosting platform's nightly backups of the storage volume and database are kept for 14 days, so a deleted photo can remain in a backup for up to 14 days.

4. Consent

Merchants can turn on an "I agree to upload my photo" checkbox that the shopper must tick before the upload starts (it is off by default; merchants who leave it off are responsible for covering the upload in their own privacy notice). When the checkbox is shown, it states how long the photo is kept. Opening the try-on is logged with a SHA-256 of the User-Agent for audit purposes.

5. Safety filtering

TryOnIA does not run its own automated content classifier on results. Generation is subject to the AI provider's own safety filters, which can refuse to produce an image. Merchants can review every result in the admin gallery and delete any of them, and hide any try-on from the product-page carousel.

6. Sub-processors

• Shopify — source of truth for installation and billing.
• Google (Gemini API) — generates the try-on image from the selfie and the product image.
• Hosting — TryOnIA, its database and its image storage run on DevCloud's own hosting platform.
• SendGrid — transactional email: to merchants, and to a shopper only when they ask for their try-on by email.
• Error tracking — DevCloud's own Sentry-compatible error tracker; shopper images are never sent to it.
• Google Analytics — usage analytics of the merchant admin pages only (not the storefront).

On the storefront, the try-on widget also reports its events (opened, completed, added to cart) to the merchant's own Google Analytics and Meta Pixel when the store has them installed; that data goes to the merchant's accounts, not ours.

7. GDPR & data deletion

TryOnIA honors Shopify's mandatory GDPR webhooks:

• customers/data_request — we look up the try-on sessions tied to that customer (Shopify customer id or email) so the request can be answered.
• customers/redact — we delete the selfies, results and carousel copies of that customer's sessions and blank their email, customer id and body measurements.
• shop/redact — 48 hours after uninstall, we delete every selfie and result file and every session, product config, daily-stat, feedback and webhook-log row for that shop, and the shop itself.

When a merchant uninstalls the app, we delete their Shopify access tokens at once; the rest of the shop's data is kept for the 48-hour reinstall window until shop/redact.

Shoppers who want their data deleted before the retention window expires can email support@devcloudsoftware.com with the store URL and the date of their try-on session.

8. Security

• All traffic encrypted in transit via TLS 1.2+.
• Shopify access and refresh tokens encrypted at rest (Fernet/AES).
• Webhook payloads HMAC-SHA256 verified before any processing.
• Storefront uploads HMAC-bound to a 30-minute session token to prevent replay.
• Per-shop rate limits on the storefront endpoints, and per-address and per-IP limits on try-on emails.
• Shopper images served only through signed, expiring links.

9. Children

TryOnIA is not directed at children under 13. Merchants are responsible for ensuring their storefront age-gates the try-on modal when serving merchandise to minors or in jurisdictions that require additional consent.

10. Changes

Material changes are communicated in-app at least 14 days before they take effect.

11. Contact

DevCloud Software LLC
Email: support@devcloudsoftware.com