OutfitSnap Privacy Policy

Privacy Policy for OutfitSnap

Effective Date: April 11, 2026
Last Updated: August 21, 2026

1. Introduction

OutfitSnap ("OutfitSnap," "we," "our," or "us") provides a mobile application and related website that help users upload clothing items, manage a digital wardrobe, and generate AI-based outfit visuals and related fashion content. This Privacy Policy explains what information we collect, how we use it, when we share it, how long we keep it, and what choices you have.

If you do not agree with this Privacy Policy, do not use the app or website.

2. Contact

• Email: outfitsnap.app@gmail.com
• Mailing location: Warsaw, Poland

3. Information We Collect

3.1 Information you provide directly

We may collect:

• Email address
• Name or display name
• Login credentials processed by Supabase Authentication; OutfitSnap does not store your password in your app profile
• Profile photo
• Body photo uploaded for reusable virtual try-on and outfit generation
• Clothing item photos and related wardrobe details
• Outfit names, favorites, notes, collections, and saved look selections
• Prompts or other text you submit for AI features
• Customer support communications and any attachments you choose to send

3.2 Information generated when you use the service

We may create or store:

• AI-generated outfit images and image history
• Clothing category, subcategory, and color suggestions derived from uploaded clothing images
• Saved outfit and generation records, including status and technical metadata needed to complete or recover a request
• Subscription status, entitlement status, purchase sync results, token balances, and token transaction history
• Usage counters such as generation counts, token usage, and free-generation limits

3.3 Technical and device-related data

We collect or receive limited technical data such as:

• App version and basic request, security, and service-operation metadata
• Authentication and session metadata
• An app-generated device identifier sent to our backend to enforce free-generation limits and prevent abuse
• Website page views, App Store link clicks, referrer, browser, device type, operating system, and approximate region collected through Vercel's privacy-focused website analytics

We do not use the app-generated device identifier for advertising. Vercel Web Analytics is configured without third-party advertising cookies and reports website activity in aggregate rather than associating it with an OutfitSnap account.

3.4 Purchases and payments

Apple processes in-app payments. We do not receive your full payment card details. We may receive or store:

• Product identifiers
• Subscription, entitlement, and renewal status
• Transaction and original transaction identifiers
• Purchase, expiration, refund, billing, and renewal event metadata

3.5 Information stored locally on your device

The app may store:

• Your remembered authentication session in the device's secure credential storage
• A non-sensitive session status marker and a local cached copy of basic profile data
• Language, theme, notification, onboarding, review-prompt, hint, and paywall preferences
• Cached subscription and token display state
• Bounded generation-recovery state, image-cache metadata, and sanitized local error records
• Locally scheduled reminder notifications

This local information supports app operation and continuity. It may remain until you log out, clear it, uninstall the app, or the app replaces or removes it. OutfitSnap does not currently collect a push token for remote marketing notifications.

4. Information We Do Not Intentionally Collect

We do not intentionally collect:

• Contact lists
• Precise location data
• SMS or call logs
• Advertising identifiers for ad targeting
• Biometric templates, facial geometry, or face-recognition identifiers

Photos you upload may incidentally include your face or body. OutfitSnap processes the image as content needed for the feature you request; it is not designed to identify you through biometric recognition.

5. How We Use Information

We use information to:

• Create and maintain user accounts and authenticate sessions
• Let you upload, store, organize, display, and delete wardrobe items and photos
• Analyze clothing images and generate requested virtual try-on or outfit results
• Save outfit history, collections, and favorites
• Complete, restore, and reconcile subscriptions and purchases
• Maintain token balances and enforce feature, subscription, and free-generation limits
• Recover generation requests safely and prevent duplicate charges or provider submissions
• Protect the service, prevent abuse and fraud, troubleshoot failures, and meet legal obligations
• Respond to support and privacy requests
• Measure aggregate website visits and App Store link engagement

We do not sell personal information or use it for cross-app advertising tracking.

6. Photos, Storage, and AI Processing

6.1 OutfitSnap storage

Body photos, profile photos, wardrobe photos, and generated images are stored in private, account-scoped Supabase Storage locations so the app can provide its features. New storage paths are organized by account ownership.

The app receives temporary signed links when it needs to display a private image. These display links expire and can be refreshed after an authenticated request; they are not permanent public links. When an AI provider needs an input image, OutfitSnap creates a separate, shorter-lived signed link shortly before the provider request.

6.2 Body, profile, and wardrobe photos

Your active body photo is stored so you can reuse it for future virtual try-on requests. Profile photos are stored for account display. Wardrobe photos and their details are stored so you can organize and use your clothing in outfit generation. Removing an active reference does not necessarily remove a separate image already used in saved or generated history; the related item or account deletion flow removes owned application storage within its scope.

6.3 FASHN virtual try-on

For the current virtual try-on flow, OutfitSnap may send FASHN short-lived signed links to your body photo and a prepared image containing selected clothing. FASHN's current documentation states that its request history records request metadata, submitted input URLs, and output references. Those signed input links expire independently and are intended to limit later access to the source images.

FASHN currently states that standard CDN outputs are scheduled for deletion after three days and that Customer Content is not used to train or fine-tune its AI models. Where data-protection law applies to this business processing, FASHN describes itself as a processor or sub-processor, as applicable, and may use its listed sub-processors. See FASHN's Data Retention & Privacy documentation, Privacy Policy, Terms of Service, and Data Processing Addendum.

After receiving a provider output, OutfitSnap downloads it and saves its own copy in private Supabase Storage for your generated-outfit history. FASHN's temporary provider-side availability and OutfitSnap's account-side saved copy are separate.

6.4 Google Gemini / Google AI

OutfitSnap uses Google Gemini for clothing image analysis and related AI features and may use it as a configured fallback for image generation. The content sent depends on the feature and may include a clothing image, body photo, selected clothing images, prompt, or processing instructions. Google processes that content to return the requested analysis or result under its applicable terms and privacy commitments.

6.5 Generated images and AI limitations

Generated images may be stored in your account history until you delete the related content or your account. AI results can be inaccurate, unrealistic, or unexpected. OutfitSnap does not intentionally create biometric identifiers from submitted images.

6.6 Privacy-safe logging

OutfitSnap's image, storage, provider, and account-deletion logs are designed to use limited operational fields. They do not intentionally include image bytes, prompts, signed image links, local file paths, account identifiers, email addresses, tokens, request bodies, or raw provider payloads.

7. Legal Bases for Processing

If you are in the EEA, UK, or a similar jurisdiction, we generally rely on:

• Contract: to provide the app and features you request
• Legitimate interests: to secure, maintain, measure, and improve service reliability and prevent abuse
• Consent: where required, such as device permissions and optional notifications
• Legal obligation: where we must retain or disclose information by law

8. Sharing and Third-Party Services

We share information only as needed with providers that support the service:

• Supabase: authentication, database, and private file storage
• Apple: Sign in with Apple, App Store purchases, subscription management, cancellations, and refunds
• RevenueCat: purchase and subscription status, entitlement handling, purchase synchronization, and provider event processing
• FASHN: virtual try-on and outfit rendering
• Google Gemini / Google AI: clothing analysis, AI processing, and configured image-generation flows
• Vercel: website hosting and aggregate, privacy-focused website analytics

These providers may process information in other countries and may retain limited records under their own legal, security, billing, backup, and service obligations. We may also disclose information when required by law, to protect users or the service, to investigate fraud or abuse, to enforce our Terms, or as part of a business transfer subject to appropriate safeguards.

9. Data Retention

We retain information only for as long as reasonably necessary for the purposes described above, including:

• Account and active application data: while your account is active or until you delete the related content
• Wardrobe, body, profile, and generated images: while needed for the features you use, until you delete related content, or until account deletion removes owned active storage
• Generation records: while needed to provide history, recover requests, prevent duplicate processing, and support security and service integrity
• Subscription, entitlement, transaction, token, and delivery records: as needed for accounting, fraud prevention, dispute handling, purchase integrity, and legal compliance
• Device free-usage history: as needed to enforce free-generation limits and prevent repeated free-use abuse; account deletion removes the link to the deleted profile without resetting the device-level counter
• Website analytics: according to Vercel's aggregate analytics retention and privacy controls
• Local device information: until you log out, clear it, uninstall the app, or the app overwrites or removes it

Provider request history, temporary outputs, backups, security records, and legally required records may follow separate limited retention periods. We do not claim that deletion is instantaneous from every provider or backup.

10. Account Deletion and Your Choices

You can delete your account in the app. The deletion flow first removes active application data and owned storage covered by the account, including profile, wardrobe, body-photo, saved/generated-outfit, collection, generation, subscription, token, and related account state. It then deletes the Supabase Authentication account. If required cleanup fails, the flow stops before deleting the authentication account so it can be retried safely.

Limited transaction, billing-delivery, fraud-prevention, security, accounting, or legal records may remain when reasonably required. Device-level free-usage history may remain with the link to the deleted account removed. Third-party providers may retain limited information under their own legal, security, backup, billing, or service obligations.

Depending on your location, you may have the right to access, correct, delete, restrict, object to, or request a copy of certain personal information, and to withdraw consent where processing depends on consent. You can also delete individual content in the app, cancel subscriptions through Apple, disable local notifications, or contact outfitsnap.app@gmail.com for a privacy request.

11. International Transfers

Your information may be processed in countries other than your own, depending on where our providers operate. Where required, we rely on appropriate contractual or legal safeguards for cross-border transfers.

12. Children

OutfitSnap is intended for users aged 9 and older. We do not knowingly allow children under 9 to create or use an account. If you believe a child under 9 has provided personal information through the service, contact us and we will review the request and take appropriate action.

13. Security

We use reasonable technical and organizational measures intended to protect information, including authenticated access controls, private owner-scoped storage, expiring signed links, secure device credential storage for remembered sessions, privacy-limited logs, and encrypted transport where supported. No storage or transmission method is completely secure, and we cannot guarantee absolute security.

14. App Permissions

Depending on the features you use, OutfitSnap may request access to:

• Camera
• Photo library or media library
• Photo library add or save access
• Local notifications

These permissions support selecting or capturing photos, saving generated looks to your gallery, and scheduling local reminders. The app accesses only the photos you choose or the access scope you grant through the operating system.

15. Changes to This Policy

We may update this Privacy Policy from time to time. The updated version will show a new "Last Updated" date. Your continued use after an update means the revised policy applies to future use, to the extent permitted by law.

16. Contact Us

For privacy questions or requests, contact:

outfitsnap.app@gmail.com
Warsaw, Poland