Privacy Policy

Effective May 28, 2026 · Last updated July 14, 2026

Try On Haul processes the information needed to create outfit previews and manage your account.

Information we collect

• Account identifiers from Firebase Authentication.
• Body reference photos, clothing images, generated looks, and closet metadata you add in the app. Body reference photos and generated try-on images may include your face.
• Usage counters needed to apply free generation limits and protect the service from abuse.
• Apple purchase transaction identifiers, product identifiers, subscription status, and try-on credit balances needed to grant and restore purchases.

How we use information

We use this information to authenticate you, generate try-on previews, save your closet and looks, grant and restore Apple purchases, operate support, and keep the service reliable.

Face data

Try On Haul does not use facial recognition and does not create faceprints, facial landmarks, facial geometry, or any other biometric identifier or template. Your face appears only as part of the ordinary full-body photographs you choose to provide and the try-on images generated from them.

• Collection. Face data is collected only as part of the body reference photos (front, left, right, back) you add in the app and the try-on preview images generated from those photos. Nothing is collected from your camera or photo library without your action and consent.
• Use. These photos are used solely to render virtual try-on previews of clothing on your own body and to suggest an editable body profile (such as body type and estimated height) for clothing-fit recommendations. They are never used for identification, authentication, tracking, advertising, or training of our own models.
• Sharing. Photos are shared only with Google, our data processor: they are stored in Firebase (Google Cloud) and are submitted from our Cloud Functions to the Google Gemini API to generate try-on images. Under the Gemini API terms that apply to our billed project, Google does not use these prompts or outputs to train its models and retains them only for a limited period for abuse detection. We do not sell photos and do not share them with advertisers or any other third party.
• Storage. Photos are stored in Google Cloud Storage and Firestore (Firebase) in the us-central1 (United States) region. Access is restricted to your signed-in account by security rules; generated looks can be written only by our server code.
• Retention. Photos are retained only for as long as you keep them in your account, so you do not have to re-upload them for every try-on. There is no secondary retention: you can delete your body photos in the app at any time, and deleting your account in Settings permanently removes all photos, generated looks, closet data, profile data, and your authentication record from our systems.

Third-party processors

The app uses Firebase for authentication, storage, database, and cloud functions. Image generation and body analysis requests are processed through Google Gemini APIs from Cloud Functions. Apple processes App Store purchases and subscription billing under Apple's privacy policy; Try On Haul receives signed transaction information needed to provide access.

Data retention and deletion

Your photos, closet items, generated looks, profile data, usage counters, and app-side purchase records are retained while your account exists. Deleting your account from Settings permanently deletes this data, including every stored photo, and removes your Firebase Authentication record. Deletion is executed server-side and is not recoverable. Deleting the app account does not cancel an Apple subscription or remove transaction records retained by Apple; subscriptions can be managed separately in Apple ID settings.

Your choices

You can delete your body photos or your entire account and related app data from Settings. You can also contact support@tryonhaul.app for privacy requests.

Data protection

Access to user data is restricted by Firebase Authentication, Firestore rules, Storage rules, and server-side callable functions.