Legal

Privacy Policy

Last updated: November 7, 2026

This policy describes the current Ai-clothes-change application behavior. Storage of generated results depends on whether private Cloudflare R2 storage is configured in the deployed API and whether copying each output succeeds.

The service is for adults aged 18 or older. We do not sell personal information.

1. Information we handle

• Google sign-in information: Google account subject identifier, email address, and name when supplied.
• Try-on history: uploaded filenames, your styling prompt, submission time, processing status and duration, provider job identifier, error details, and a reference to the generated result.
• Billing records, if checkout is enabled: plan, price and currency, Waffo order or subscription identifiers, status, billing-period dates, and the timestamp when a monthly auto-renewal confirmation was recorded. Payment card details are entered with Waffo checkout and are not collected by this application.
• Basic technical information needed to operate and secure the service, such as request and error information.

2. How uploaded images are handled

The API accepts JPG, PNG, and WebP images up to 10 MB each. It processes the uploaded image files in server memory and sends the person photo, clothing image, and optional prompt to FASHN Try-On Max to generate the preview. This application does not write the original uploaded image files to its database or its own image bucket.

FASHN processes submitted content to provide the generation. According to FASHN's published Data Retention & Privacy documentation, temporary input-image copies are removed when processing finishes, with a one-day cleanup backstop. FASHN says its request records are not automatically deleted and do not include copies of base64 input images; default output URLs are scheduled for deletion after three days. FASHN also says customer content is not used for model training unless a customer separately opts in. We cannot delete FASHN's provider-side request records from this application.

3. Generated-result storage and retention

If private Cloudflare R2 storage is configured and the copy succeeds, the application stores the generated image in that private bucket. No automatic expiration is configured for those copies. You can delete a completed or failed try-on from Usage History; this removes its application history row and, when present, its R2 result file.

If R2 is not configured or a copy fails, the application keeps the FASHN result URL in the try-on history instead of making its own image copy. FASHN schedules its default output URL for deletion after three days. Deleting the history entry removes our database reference, but cannot accelerate FASHN's provider-side deletion schedule or delete its request record.

Try-on history rows in our database have no automatic expiry configured. Deleting an individual entry removes that row. Google account details and billing or subscription records do not currently have a self-service account deletion control or an automatic deletion schedule in this application.

4. Why we use information

We use information to sign you in, submit and track try-on requests, display usage history and results, apply credits and subscription entitlements, synchronize verified payment events, prevent duplicate requests, and maintain service security and reliability.

5. Service providers

• Google provides sign-in.
• FASHN provides the AI try-on generation model and processes the submitted images and prompts.
• Neon PostgreSQL stores account, history, and billing metadata.
• Render hosts the Node.js API; Cloudflare hosts the web application and may store generated results in R2 when configured.
• Waffo handles checkout and subscription processing only when payment checkout is enabled. Payment processing is currently disabled in the production configuration available to this project.

6. Your choices and deletion

You can review and delete individual completed or failed try-on entries from Usage History. This removes the app's record and any R2 copy the app controls. Provider-side FASHN request records are outside this deletion control. We do not currently provide an in-product account-wide deletion feature. The account-deletion and privacy-request contact address has not yet been supplied; it must be added before public launch.

7. Contact