Privacy policy

Who operates Dresseeni

Mahmoud Yassine Chiboub operates Dresseeni and is responsible for the personal information described here. For privacy questions or requests, email privacy@dresseeni.com.

Wardrobe, photos, and outfit suggestions

Dresseeni stores your wardrobe, selected photos, outfit history, and style preferences on your device. It uses that information to suggest outfits. You can browse your saved wardrobe and use local features without a cloud account.

When you confirm an online photo feature, Dresseeni sends the approved photo or a re-encoded copy to our Google Cloud backend. A copy of a whole photo can still show people and the background. Google Cloud Gemini processes the images to find clothes, check a garment, create a Studio photo, or make an outfit preview. A personal outfit preview can include the person and garment photos you approve. The backend keeps uploaded copies, intermediate files, and results so it can complete and recover work and let you review or reuse results.

Optional photo recognition creates recognition signatures on your iPhone to help find photos of you. Dresseeni keeps these signatures and its scan index in protected local storage and excludes them from its iCloud sync. You can erase them with Forget photo identity in Profile → Wardrobe & photos.

Sign-in, purchases, and communication

When you sign in, we use account identifiers, verified sign-in information, and session records to connect your account and protect access. We use Sign in with Apple for Apple sign-in. Google Firebase Authentication handles Google and email-link sign-in. We store the verified email address Firebase supplies for those sign-in methods. The app keeps its session credentials in iOS Keychain.

Apple handles App Store payments and subscriptions. RevenueCat uses a Dresseeni-issued customer ID, purchase receipts, and transaction and subscription information to verify access and purchases. We keep records for credit balances, refunds, reconciliation, and accounting.

If you contact us, we use your message and contact details to respond. We store in-app messages with your account. Cloudflare hosts this website and routes email to Gmail. These services process the request or message and delivery information to provide and secure the service. Marketing messages depend on your choice and you can turn them off in the app.

Location, iCloud, and usage records

If you allow location access or choose a city, Dresseeni uses Apple weather and map services to provide local forecasts and outfit suggestions. You can choose a city and change location or Photos permissions in iOS Settings.

If you turn on private iCloud sync, Dresseeni can save wardrobe, outfit, and preference details and the selected display image and thumbnail to your private iCloud storage. Turning sync off stops new updates. Use the app's cloud-data controls to request removal of the existing copy.

We use account-linked activity, timing, job status, and error information to operate the service, diagnose failures, prevent abuse, and understand how features work. Some job records include identifiers and fingerprints used to reconcile results and charges.

How long we keep information

We keep account data while your account is active and retain photos and results while they support a saved garment, an open review, or an available result. Eligible failed, stopped, or abandoned photo jobs enter cleanup after 30 days without server activity. Cleanup can take longer if a worker is still using a file, the file also supports other work, or a cleanup step needs a retry. Older Studio and try-on workflows use a separate, shorter cleanup schedule. Stopping an upload or closing the app does not itself erase an uploaded copy.

We rotate operational logs and backups. Scheduled data-disk snapshots have a seven-day retention policy. A disk snapshot can also contain an older database dump. A separate deletion journal lets us apply completed deletions when restoring a covered backup. We retain the limited deletion records needed to keep deleted accounts from coming back after recovery. We may keep accounting, security, or legal records for as long as those purposes require.

Our backend runs in the United States. Google Firebase Authentication processes sign-in data in the United States. Google Cloud Gemini uses a global endpoint and may process data in other regions. On supported models, Google Cloud may store derived input cache data for up to 24 hours. Google may also retain data under its abuse monitoring terms. Firebase privacy and retention · Google Cloud caching and retention

Your choices and account deletion

You can change Photos or location access in iOS Settings, remove your recognition data, and manage your local wardrobe in the app. Profile → Privacy & data → Delete local data clears data on your phone. To request removal of your connected account and server data, sign in and use Profile → Account → Delete account and all data.

We revoke access and process deletion of the account, its linked sign-in records, cloud work, and its RevenueCat customer record. The request can show as pending while we finish provider or file cleanup. Apple controls App Store subscriptions. If you want to cancel a subscription, manage it with Apple.

You can email us to request access, correction, a copy, or deletion of your information, or to object to or restrict processing where applicable. We may need to verify that the request relates to your account. Where we rely on consent, you can withdraw it for future processing. If local law gives you the right to complain to a data protection authority, you can contact that authority. privacy@dresseeni.com