Privacy Policy
Effective date: October 14, 2026
OutfitCue ("OutfitCue", "we", "us", or "our") is a mobile app that helps people make outfit decisions using their own wardrobe photos, optional reference photos, and AI-generated outfit previews.
This Privacy Policy explains what information we collect, how we use it, who we share it with, and the choices you have.
Contact
If you have questions or requests about this policy or your data, contact us at:
Information We Collect
We collect the information needed to provide and improve OutfitCue:
- Account information, such as your email address, user ID, authentication status, and account settings. If you sign in with a service such as Google or Apple, we also receive the profile information that service makes available, which may include your name and provider account identifier. A name can be stored with your account even if you did not enter it directly in OutfitCue.
- Wardrobe and source photos you upload or capture in the app.
- Garment information derived from your photos, such as garment category, color, labels, attributes, and crop boxes.
- Optional reference photos or appearance information you provide so the app can render outfits on a person or placeholder.
- Person and appearance information derived from uploaded photos, including face/body crop locations, groups of photos judged to show the same person, matching confidence, and your confirmations or corrections about which person is you. These records are associated with your account.
- Generated outfit images, outfit combinations, scenarios, style notes, and related generation metadata.
- Feedback you submit, including feedback text, app version, platform, and any screenshots or photos attached to feedback.
- Outfit searches and search context, including the occasion and text you enter into the outfit helper. Search text is processed by our search providers; outfit-helper context is also retained in account-linked service usage records.
- Product interactions, such as onboarding milestones, outfit likes or hides, and subscription purchase or restore events.
- Usage and diagnostic information, such as render-credit usage, AI request start/end times, media download and cache statistics, errors, and server logs. Crash reports may include your account ID, an app installation identifier, device and operating-system information, app version, stack traces, and recent technical events. Diagnostic records can be linked to your account or app installation; they are not necessarily anonymous.
- Subscription information, such as the store product, entitlement, purchase status, store, renewal or cancellation state, and access-expiry date. We use a pseudonymous account identifier (your Supabase user UUID) to connect this information to your OutfitCue account. We do not receive or store your full card number or app-store password.
When you use camera or photo-library features, the app only accesses photos you choose to capture or upload. OutfitCue does not scan your entire photo library.
How We Use Information
We use your information to:
- Create and manage your account.
- Store your wardrobe, reference photos, generated outfits, and preferences.
- Detect garments, extract clothing attributes, choose outfit combinations, and render outfit previews.
- Group appearances of the same person within your uploaded photos and use your confirmations to manage personal references and worn-garment imports.
- Find and personalize outfits using your wardrobe, search requests, reference choices, and interactions such as keeping or hiding outfits.
- Display your wardrobe and outfit history back to you in the app.
- Process feedback and provide support.
- Track usage limits, prevent unexpected generation costs, and diagnose service issues.
- Understand onboarding and subscription activity and improve the app.
- Protect the app, our infrastructure, and other users from abuse or unauthorized access.
- Comply with legal, platform, and security obligations.
AI Processing
OutfitCue uses AI services to provide its core features. Your uploaded photos, garment data, reference photos, prompts, and generated outputs may be processed by AI/model providers to:
- identify garments in photos;
- extract garment attributes;
- compare people in uploaded photos and group appearances judged to be the same person within your account;
- interpret outfit searches and rank matching outfits;
- select a relevant synthetic example persona from your current AI reference when you use your own photos for Try-ons;
- choose outfits from your wardrobe; and
- generate outfit preview images.
Our current architecture uses OpenRouter for text, vision, image generation, and embedding model calls. Google Gemini remains an image-generation option. Person matching compares visible identity in photo crops and stores grouping results and confidence; it is not used to authenticate your account. Provider data handling can depend on the specific provider, model, plan, region, and account settings. We do not sell your photos or intentionally use your photos to train our own AI models.
For example-persona matching, we process your current generated AI reference through our embedding provider and compare it with prepared synthetic personas. We cache the selected example persona and reference version; we do not store the personal embedding produced for this comparison. Choosing an avatar or turning off use of your own photos stops new personal-reference matching. The example selection does not change your Try-on person setting. Cached selections are deleted when their reference or your account is deleted.
New photo uploads can trigger AI processing automatically. Outfit searches and generation requests also use AI services. You can avoid initiating these actions and can delete your account and app-stored data from Settings. Turning off use of your own photos for outfit renders does not, by itself, disable photo-intake processing or person grouping.
Service Providers
We use service providers to operate the app. These providers may process data for us only as needed to provide their services, maintain security, debug issues, or comply with law.
Current or planned providers include:
- Supabase for authentication, database, and file storage.
- Railway or another backend host for running the API.
- Google Gemini for AI image generation.
- OpenRouter and underlying model providers for text, vision, person matching, and search-embedding model calls.
- Langfuse or similar observability tools if tracing is enabled.
- Sentry for crash and error reporting, including diagnostic context and account or installation identifiers used to investigate faults.
- Apple and Google services for app distribution, sign-in, and platform functionality.
- RevenueCat for subscription purchase processing, entitlement status, restoration, and subscription diagnostics.
We do not sell personal information. We do not use advertising SDKs in the current beta.
We configure crash reporting to avoid automatically attaching screenshots or view hierarchies and to filter credentials, request bodies, and selected sensitive fields. These safeguards reduce the information sent with errors; they do not make every diagnostic record anonymous.
How Long We Keep Information
We keep your account data, uploaded photos, appearance-grouping records, garment information, generated outfits, preferences, retained search context, usage records, and feedback for as long as your account is active or as long as needed to provide the app.
If you delete specific content in the app, we delete or stop displaying that content as implemented in the app. If you delete your account, we delete your account data and app-stored media from our systems, except where limited retention is required for security, legal compliance, backups, fraud prevention, or provider-side logs outside our direct control.
Purchase records may also be retained by Apple, Google, RevenueCat, payment processors, or tax/accounting systems under their own legal and operational requirements. Removing the RevenueCat customer record disconnects provider-side subscription data where supported, but it does not delete the store's purchase record or cancel billing.
Account Deletion
You can delete your account in the app from Settings. Account deletion is intended to remove:
- your account record;
- your wardrobe/source photos and garment records;
- your reference photos;
- generated outfit images;
- feedback and feedback attachments;
- usage and preference records associated with your user ID; and
- your authentication account.
Deleting an OutfitCue account does not cancel an Apple App Store or Google Play subscription. Manage or cancel billing through the store account used for the purchase before deleting your account if you do not want the subscription to renew. We ask users with active provider-backed access to acknowledge this before deletion.
If the in-app flow is unavailable, contact ask.sulaimanov@gmail.com and we will help with the request.
Your Choices
You can:
- choose which photos to upload;
- delete garments, reference photos, outfit images, and feedback attachments where the app provides deletion controls;
- turn off use of your own reference photos for outfit renders if that setting is available;
- delete your account; and
- contact us with privacy questions or deletion requests.
Security
We use reasonable technical and organizational safeguards designed to protect your information. These include authenticated API access, per-user database access controls, hosted storage controls, and service-role access limited to the backend.
No system is perfectly secure. Please do not upload photos or information that you are not comfortable processing through a cloud service.
Children
OutfitCue is not intended for children under 13. Do not use OutfitCue or upload photos of children unless you have the legal right and any necessary consent to do so. If we learn that we collected personal information from a child under 13 without appropriate consent, we will take steps to delete it.
International Processing
Your information may be processed in countries other than where you live. Those countries may have different privacy laws. Where required, we rely on appropriate legal mechanisms for international transfers through our service providers.
Changes To This Policy
We may update this Privacy Policy as the app, providers, or legal requirements change. If we make material changes, we will update the effective date and, when appropriate, provide additional notice in the app or by email.