Privacy notice

What we store

The email address you sign in with, the photos you upload, the clothing descriptions and choices saved with each image, and records of your credit purchases. We also store outfit names, private notes, collections, shop links, favorites and any image feedback you give.

Your photos and looks

Uploads and generated images are held in private storage. Only your signed-in account can reach them, through authenticated requests and temporary signed links. Anyone you give a signed image link to can open that image until the link expires. We don’t publish your pictures in a public gallery.

Creating an image

When you create an image, Wearform sends your selected person photo, any clothing photo, and your description and choices to OpenAI to generate the result. Those requests are subject to OpenAI’s API data handling and retention policies. We don’t use your uploads to train our own model. We strip image metadata and resize uploads before storing them.

The photo check in the fitting room runs in your browser. Your photo isn’t uploaded for it, and its results aren’t stored.

Sharing a look and asking friends to vote

Sharing is optional. A public link lets anyone with it see and download the finished image for seven days, including on social networks you share it with. Outfit names, private notes, original uploads, clothing instructions, shop links and account details are never included. Turn off sharing or delete the look to disable the link sooner. Copies other people or networks saved may remain.

A vote link works the same way. It shows only the finished images you picked, for seven days, and you can turn it off at any time. Friends vote without an account. To count one vote per browser we set a random ID in a cookie on the voter’s browser and store a keyed hash of it with their choice. We don’t ask voters for a name or email address, and you see totals, not who voted.

Accounts, payments and analytics

Supabase provides sign-in, the database and image storage. Stripe processes payments; we never store full card numbers. Essential cookies keep you signed in. We don’t load advertising tags or trackers.

If you arrive through one of our ads or another tagged link, we keep the link’s campaign details (such as the campaign, keyword and Google’s ad click ID) in a cookie on your browser for up to 90 days. If you create an account in that time, we store them with it so we can see which ads and links bring customers. If you then buy credits, we may give Google Ads that click ID with the purchase time and amount, so it can count the ad’s result. We don’t send your email address, photos or other account details.

We use Plausible Analytics to understand visits, page views, referral sources, and broad device and location information. It also counts steps such as adding a photo, an image finishing or opening checkout, so we can see where people get stuck. Plausible doesn’t use cookies. We never send your photos, clothing descriptions, email address or account details to it. See Plausible’s data policy for more.

When something goes wrong in the fitting room, such as a failed upload or checkout, we record the error message you saw and when it happened, with your account if you’re signed in, so we can fix the problem. Your photos and clothing descriptions aren’t included.

Preventing abuse

We use keyed hashes of account or email identifiers and network addresses to limit repeated requests. These short-term records are cleared after their 24-hour limit window. Earlier free-image claims and generation attempt records may remain after account deletion to prevent repeated claims and refunded retries. Attempt records include account and request IDs, model, time, outcome and estimated cost, but never photos or prompts. We also record payment dispute status.

When you ask for the free preview, we set a random ID in a cookie on your browser. We keep keyed hashes of that ID, your email address and your network address with the claim, so each person, browser and network gets one free preview. We don’t store the raw ID, email or network address with the claim, and the claim record remains after account deletion so a replacement account can’t claim again.

Removing photos and data

Delete looks from your lookbook and unused photos from your saved photos in the fitting room. Delete looks that use a photo before removing that photo. Deleting a look also removes its name, notes, favorites, feedback, saved clothing description and choices, and removes it from any vote link. Payment and credit records are kept for accounting, refunds and fraud prevention. Service backups and provider retention may outlast deletion from the app.

Drafts on this device

The fitting room keeps one draft, including photos you’ve picked, in this browser’s storage so you can continue after signing in or paying. Drafts expire after 24 hours of inactivity, aren’t synced to other devices, and are cleared when you start a new look or sign out. Photos are saved to your private account when you create an image.

Examples and preview mode

Starter outfit images, pose examples and the examples on our pages are AI-created pictures of fictional adults. Choosing an example doesn’t create a custom image or spend credits. When accounts or image creation aren’t connected, the app labels preview mode clearly.

Support and privacy requests

To delete your account or ask about your data, use the support form. You can send an account-access, billing or privacy request without signing in.

Tickets store your message, the email address you give or sign in with, and our reply. Support operators can read them. A signed-out request doesn’t verify that you own the email address or account. Signed-out requests get a private ticket link; anyone with that link can read the ticket and our reply, so keep it private. We store only a hash of its access key. No ticket email is sent. Ask through the support form to remove a ticket once it’s resolved.