Your wardrobe and photos

Your wardrobe, personal reference photos, and try-on previews are private to your signed-in account. Public access to the website does not publish those records.

Account sign-in

When Google and email accounts are enabled, Auth0 verifies your sign-in and the configured email provider delivers one-time codes. iMatcher stores a private account mapping and a hashed session identifier. Matching email addresses never merge wardrobes. Original account transfers require proof from the original account. Sign-out ends the current app session; deleting your iMatcher account also removes its provider identities when that connection is configured.

Your style profile

Optional gender, clothing preference, styles, fit, dressing needs and favorite brands are saved privately. You can edit them in Profile. Styling uses your clothing choices, fit, styles, dressing needs and brands; it does not receive your gender answer.

Garment recognition and Prettify

If you turn on finding separate pieces, OpenAI analyzes the clothing photo and suggests visible garments and their details. Review each piece before adding it. Prettify is a separate action that sends the selected source photo to OpenAI to create a clean product image using one image credit. Original photos remain private and can be restored. AI can approximate hidden details, so review the result.

AI processing

New garment analysis, styling, avatar and outfit-preview AI requests use OpenAI. Styling sends your short request, relevant clothing preferences, structured weather and a small set of candidate garment descriptions. Routine text tasks do not include wardrobe photos, your gender answer or full conversation history. Local rules and cached results can still support recommendations. DeepSeek, Qwen and external segmentation are disabled for new requests. Previously submitted image jobs remain associated with their original provider so their status can be recovered without submitting a duplicate image. Background image responses are temporarily stored by the provider so generation can continue after you leave. We request deletion of OpenAI responses after results are saved; provider security and abuse-monitoring retention may still apply.

Inspiration and suggestions

Optional image inspiration and personal previews send the explicitly selected references to the image provider. In Discover, starting generation approves one image credit per batch of six looks while scrolling on that page. You can pause at any time. When saved face or body references are available, that mode uses them privately; otherwise it creates fictional models. Refresh resumes pending work without buying another batch. Results are saved privately. Product search uses reviewed garment descriptions and shopping preferences; personal photos are not sent to retailer search providers. Friends’ comments remain private to their author and the outfit owner. You may first request clothing alternatives without generating an image. Only the separate, confirmed preview action sends the necessary images and reviewed clothing change for visual regeneration. Posting a comment alone never starts image generation.

Stylist conversations and voice

Stylist messages and drafts are saved privately. Recommendations use a compact style profile, available clothing candidates and structured weather. Your full message history is not repeatedly sent to a model. Microphone recording starts only after your action and permission. When connected, audio goes to OpenAI for transcription; iMatcher does not save the recording. Review the transcript before sending. Provider retention rules still apply.

Customer Support

Support is separate from the Stylist. Cases and messages are private to their customer and authorized support staff. The current team-contact flow does not attach photos, wardrobe contents, or diagnostic logs automatically. Signed-out visitors receive a browser cookie for their case; it does not verify account ownership. Do not send passwords, payment details, or sensitive photographs. Messages are retained until account deletion or a support deletion request is fulfilled. Email and push notifications are not currently enabled.

Weather choices

Your weather location and units stay private. Manual choices take priority over automatic location. Automatic location uses an approximate city from the host when available. Otherwise your browser contacts BigDataCloud directly to estimate its own IP location, without requesting GPS. VPNs and Private Relay can affect this estimate. Our server sends coarse coordinates to MET Norway for weather forecasts when enabled. It does not forward your IP address or personal photos. Weather is cached until the provider’s refresh time; outdated data is labeled and excluded from styling advice. NWS is an optional U.S. weather source and Open-Meteo requires its configured commercial connection. These providers may retain their own server request logs. iMatcher does not store the raw IP from this lookup. A private cache stores the latest coarse estimate for each browser session for use for up to one hour; expired entries are removed on subsequent lookups. Manual and device choices stay until changed or deleted. Changing to either choice or turning weather off clears the automatic estimates. A random browser-session identifier separates devices and is cleared on account change or sign-out. City-name search still needs its commercial geocoding connection; device location does not.

Reviewed outfit shopping

When connected, SerpApi receives reviewed clothing search terms and your shopping region, size preferences and exclusions. We save normalized returned products and cache searches privately for one hour. Product names and direct retailer links come from returned sources; availability, size and delivery may remain unknown. Photo interpretation is a separate optional OpenAI step. Opening a retailer or saving a product does not mark it purchased or owned.

Finding your city

Use my location requests your current position from your browser only when you press the button and allow location access. Your browser sends the coordinates directly to BigDataCloud to look up your city and country. BigDataCloud receives your network address and says it uses anonymous coordinate and network signals to improve its location data; see its location data explanation. The precise device coordinates are not saved by iMatcher. A weather location stores coordinates rounded to a tenth of a degree. The returned city is saved automatically after you choose Use my location and permit access. You can cancel without changing your previous city. Only the resulting city and country are included in your private preferences when you start research.

City Trends

When you request City Trends, your chosen city, country, optional age range and gender, and clothing preference are sent to OpenAI for web research. Your wardrobe photos and garment records are not included. Your preferences and latest sourced report are saved privately in your account. You can clear both from City Trends, or remove them when deleting all wardrobe data or your account. Research requests count toward a daily allowance. We request that these research responses are not stored by the provider, although provider security and abuse-monitoring retention may still apply.

Storage and deletion

Wardrobe records and uploaded originals are retained in your account. Removing a wardrobe item removes its record; stored image files remain until you delete all wardrobe data in Settings, because saved outfits or explicitly shared looks may still reference them. Pending upload files are kept in this browser to recover interrupted uploads and are removed after successful upload. Deleting wardrobe data also clears Stylist conversations, weather preferences, and shopping requests. Support conversations remain available independently; complete account deletion also clears their messages and support roles. Deleting all account data removes the app’s records and stored photos. Provider retention and infrastructure backup expiration are governed by their respective services.

Outfit polls

Creating a poll makes only the selected outfit snapshots available to anyone with its unlisted link. Selected AI previews are included only after you confirm sharing them; your original personal reference photo is excluded. Friends can respond without signing in. A browser cookie recognizes repeat responses, and poll-specific hashes are stored with votes. Results show totals, not voter names or email addresses. Short-lived hashed network identifiers limit excessive voting. You can close voting or disable the link in Polls. Disabling a link stops future access but cannot remove copies people already saved. Deleting wardrobe data also removes your polls and their responses.

StyleSense community game

Playing does not publish your wardrobe. Community entry separately approves the exact three looks and a worldwide or city audience. Members can see those looks in the game; original reference photos and other wardrobe items are excluded. Community-only rounds have no friend link. Stop community exposure or disable the poll to block future access to its community photos; this cannot recall copies already saved. Friends and community results remain separate.

StyleSense stores a chosen nickname, optional home city, locked taste votes, predictions, and scoring history. Leaderboard visibility is opt-in and displays your nickname and score in worldwide, city, and any joined friends group. Anyone with a friends group code can join it. Browser hashes and signed-in accounts reduce duplicate voting; public friend polls remain casual browser-based polls. Prediction scores require at least 10 community votes and a closed round, with five scored predictions per day at midnight UTC. Deleting wardrobe data removes your StyleSense profile and ballots as well as rounds attached to your polls. Historical round totals already finalized may remain aggregated in other players’ results.

Recommendation memory and usage

We keep structured garment metadata, compact preferences and interaction signals privately so recommendations can reuse previous work. Photo analysis may be cached for up to 90 days, clothing descriptions for 30 days and recommendations for shorter periods. Only public city evidence is shared across accounts. Usage records contain provider/model, token counts, estimated cost, task, time and result status; they do not contain raw photos, keys or prompts. Wardrobe deletion clears recommendation memory and caches; cost totals remain to enforce current limits. Full account deletion removes those usage records too. Minimal deletion markers prevent late results from restoring cleared information. Infrastructure backups and provider retention may outlast app deletion.

Your controls

Export records and download photos in Settings. AI previews are optional. Reporting output quality records a private review request; it does not automatically generate another preview. A preview illustrates appearance and does not predict fit.