privacy

Privacy at TryEz.

The short version: we don’t store your photos, and we don’t train on customer images without consent.

This page describes what data TryEz collects when you use the website (tryez.ai) or the embedded try-on widget on a partner store, and what we do with that data.

Last updated: 2026-04-26. We will note any material changes here and notify account holders by email.

Photos

We do not store the photos you (or your shoppers) upload. Person photos and garment photos are processed in memory on our servers and discarded the moment the rendered try-on is returned to your browser.

  • No copy of the input photos is written to any disk we control.
  • The rendered output image is returned to your browser and not retained on our servers.
  • Customer photos are never used to train any model without explicit, written, store-level consent.

Account data

If you create an account on tryez.ai we store:

  • Your email address (so you can sign back in).
  • A bcrypt hash of your password (irreversible). If you signed in with Google, no password is stored at all.
  • Your monthly usage counters (so we can enforce free-tier limits).
  • Timestamps of account creation and last sign-in.

We do not sell, rent, or share any of this data with third parties. We share account data with our infrastructure providers (the company that hosts our database) under their standard data-processing terms.

Try-on metadata

For each try-on we record a small row of metadata: a unique ID, the timestamp, the rendering quality score, and the requesting IP address (used for abuse prevention on anonymous demo traffic). We do not record anything about the photo content.

Cookies

We use one cookie for sign-in (an HttpOnly session cookie) and one short-lived cookie during the OAuth round-trip with Google. We do not use third-party tracking cookies.

Your rights

If you have an account with us, you can request deletion of your account and all associated metadata at any time by emailing hello@tryez.ai. We will action it within 30 days.

This document is written in plain English on purpose. If you’d like the formal privacy policy with regulator-friendly phrasing, we’re happy to send the long version on request.