MyCombine Privacy Policy

Effective date: November 2, 2026

Operator: Arda Özen

Contact: mycombineapp@gmail.com

Published policy URL: https://www.mycombine.app/privacy

This policy explains how MyCombine processes information when you create a digital wardrobe, request outfit or suitcase suggestions, use virtual try-on, manage a subscription, or interact with advertising features.

1. Information We Process

Information stored primarily on your device

You can use core wardrobe features with this information stored locally. Deleting the app may remove locally stored information unless it is also retained by an Apple device backup.

iCloud sync and backup

After onboarding, automatic iCloud sync is on by default when an iCloud account is available. It can upload your profile, wardrobe and shopping metadata and images, saved outfits, collections, calendar entries, and outfit feedback to your private Apple CloudKit database. It may also restore that data to your device. You can turn automatic sync off, make or restore a manual backup, and delete the MyCombine iCloud backup in Settings. Turning sync off does not itself delete an existing backup. This backup belongs to the iCloud account on the device, independently of MyCombine sign-in; it is not stored in Google Drive.

Friends and community

If you sign in and use Style Circle or friend-wardrobe features, our Firebase/Firestore backend stores your display name, optional profile photo, friend requests and connections, shared clothing thumbnails and item details, invitations, and outfit proposals. A friend-wardrobe invitation is accessible for up to seven days unless you revoke it sooner; expiration does not currently erase its server record automatically.

If you publish to the community, your creator name, bio, style tags, post text, and selected clothing thumbnails and details can be viewed by other signed-in users. Likes, blocks, and reports are also recorded for operation and moderation. Deleting a post removes it from the public feed, but currently marks the server record as deleted rather than immediately erasing it.

Information processed when you use online and AI features

Depending on the feature you choose, MyCombine may transmit the following through our backend to an AI service provider:

AI-generated responses and images may be returned to and saved on your device. Do not submit images or information you do not have permission to use.

Location and weather

If you grant location permission, MyCombine may use your approximate or precise location to request local weather. Location coordinates and destination names may be sent to a weather provider to retrieve a forecast. You may deny location access and enter a destination manually where supported.

Subscription and purchase information

Apple processes payments. MyCombine and RevenueCat receive subscription status, product, transaction, entitlement, and an app user identifier needed to provide Pro access and restore purchases. We do not receive your full payment-card details.

Account information

If you choose Sign in with Apple or Google, Firebase Authentication processes the provider identifier and may receive your name, email address, or Apple private-relay address according to the choices you make with that provider. MyCombine derives a pseudonymous MC- customer identifier from the Firebase user identifier and sends that customer identifier to RevenueCat to associate Pro access and customer support. Signing in is optional unless a feature clearly states otherwise.

Security and technical information

We may process an installation identifier, Firebase App Check/App Attest tokens, IP address, request time, endpoint, device/app information, and limited diagnostic events to prevent fraud, enforce request limits, secure AI services, and troubleshoot failures.

Analytics, crash reporting, and advertising

Firebase Analytics and Crashlytics are enabled in the current app configuration and can process app events, installation identifiers, device information, crash diagnostics, and IP addresses. The app includes Meta SDK code, but its App ID and client token are empty and automatic Meta events and advertiser-ID collection are disabled in the current configuration. We do not currently use Meta advertising attribution or display third-party ads in the app. If this configuration changes, we will update this policy and request any required tracking permission before enabling cross-app tracking.

2. Why We Process Information

We process information to:

3. Service Providers and Disclosures

Information may be processed by providers acting for or alongside us, including:

Providers process information under their own terms and privacy notices. We may also disclose information if required by law, to protect rights and safety, or as part of a merger, financing, acquisition, or sale of assets with appropriate safeguards.

4. Retention

Local wardrobe data remains until you delete the item or local data, or remove the app, subject to device backups. The separate iCloud backup remains until you delete it in the app or through your Apple account. AI request images are processed through our backend; we do not intentionally keep a permanent copy of the source photos there. For recovery after an interrupted virtual try-on, a compressed result image is stored in Firestore for up to 24 hours and an hourly cleanup job removes expired results.

Google states that Gemini API prompts, context (which can include submitted images), and outputs may be retained for 55 days for abuse and safety monitoring. Its terms distinguish paid and unpaid services for product-improvement use; see Gemini API terms and abuse-monitoring policy. Firebase states that Crashlytics data is retained for 90 days before removal begins, and that Firebase Authentication information is removed from live and backup systems within 180 days after user deletion is initiated; see Firebase privacy information. These are provider periods, not promises that we can erase provider-held copies immediately.

Credit and usage records, friend and community records, and moderation reports currently have no automatic deletion period in our Firestore backend. A revoked or expired invitation is no longer usable but its record may remain. A community post marked deleted is hidden from the feed but its record may remain for moderation. RevenueCat and Apple retain purchase and transaction records under their own policies; Firebase Analytics, Cloud Logging, and website hosting retain technical data according to their configured or provider retention periods. Contact us to request deletion of server-side data associated with your account, subject to legal or security obligations.

5. International Transfers

Service providers may process information in countries other than where you live, including the United States. Their applicable terms and transfer mechanisms govern this processing.

6. Your Choices and Rights

You may:

Some server-side information may not be directly identifiable without the installation or subscription identifier. We may ask for information needed to verify and fulfill a request.

7. Children

MyCombine is not directed to children under 13, or a higher minimum age where local law requires it. We do not knowingly collect personal information from children below the applicable age. Contact us if you believe a child has provided information.

8. Security

We use measures such as HTTPS, App Check/App Attest verification, rate limiting, restricted server credentials, and device-local storage. No system is completely secure, and AI image processing necessarily requires transmission when you request those features.

9. Changes

We may update this policy as features, providers, or laws change. We will update the effective date and provide additional notice where required.

10. Contact

Arda Özen

mycombineapp@gmail.com