Privacy

Scope: iOS app, TestFlight and landing page

This privacy policy covers the native MixMyLook iOS app in private TestFlight testing and the promotional website at mixmylook.app and the previous addresses mixmylook.de and mixmylook.com. The iOS app is the primary application; no separate web app is planned. The app is in development and this landing page does not yet offer a public download link.

The app sections describe the current test version. The separate website sections apply only to visits to the landing page. Controller, contact and rights information applies to both services. Outstanding contractual and configuration questions are expressly identified below.

Review date: 15 October 2026. New style-profile features are implemented in the development source and prepared for a subsequent mobile test build. Actual access depends on your app version, test access and feature permissions. This description does not establish a public sales launch or clearance of AI use by minors.

Controller for app and website

For privacy questions and requests concerning your rights, contact info@soreviq.de.

Email enquiries

If you email us, we process your sender address, any name you provide, message content and technical message details to respond. The email link opens your email app; the website itself does not send a message.

The legal basis is Article 6(1)(f) GDPR for general enquiries, or Article 6(1)(b) GDPR for a contract or pre-contractual steps you request. Please include only information needed for your question.

After the enquiry is resolved, we delete it when it is no longer needed. Statutory retention obligations or the need to establish, exercise or defend legal claims may require longer retention, with use restricted accordingly. The email provider for info@soreviq.de, any further recipients and possible processing outside the EEA still need verification.

Your rights – app and website

Subject to the applicable legal conditions, you have rights to access (Article 15 GDPR), rectification (Article 16), erasure (Article 17), restriction (Article 18) and portability (Article 20). You may withdraw any consent you have given for the future, without affecting the lawfulness of earlier processing.

Right to object: Where processing relies on Article 6(1)(f) GDPR, you may object under Article 21 on grounds relating to your particular situation. We will assess whether the processing must stop. Contact: info@soreviq.de.

Under Article 77 GDPR, you may complain to a supervisory authority, particularly in the country of your habitual residence, workplace or an alleged infringement. The authority at the provider’s location is the State Commissioner for Data Protection and Freedom of Information Baden-Württemberg.

iOS app: local data, photos and backups

Clothing, original and edited images, person photos, looks, downloaded try-on images and local profile details are stored on your device. Signing in does not synchronise this collection to the cloud. Only a separately selected online function transmits the data required for that function.

Apple Vision removes backgrounds on the iPhone without sending images to an image service. Camera access, selected photos and files are used for the import functions you choose. You can manage permissions in iOS.

Manual exports are independent backup files. You choose their destination, such as iCloud Drive, and whether to share them. Apple processes files saved in iCloud under its own terms. Local data remains until the relevant deletion or removal of the app’s data. Deleting data in MixMyLook does not automatically remove external backups or photo-library images. Enabled iCloud sync propagates changes and individual deletions to other devices; see the iCloud section for limits. Device-wide backups depend on your iOS settings.

The purpose is to provide the wardrobe management and display functions you request. Where personal data is processed to provide the service, the basis is Article 6(1)(b) GDPR. Local functions do not require uploading the entire wardrobe.

Original images may contain capture time, device or location information. Full backups include original files and any embedded metadata. Deleting one item does not automatically erase older internal backups. Eligible older internal backups can be explicitly removed in settings. iOS device backup is separate from CloudKit sync: depending on system settings, local app data may be included in iCloud or computer backups even with MixMyLook sync disabled.

The optional style profile under My style is separate: confirmed style preferences are synchronised between devices through Supabase. The style-profile section below explains its scope and deletion options.

iOS app: family wardrobes and children’s looks

Parents can manage up to three children’s wardrobes in their own account. Data includes chosen names, optional wardrobe images, clothing details and sizes, and assignments of garments and saved combinations. This does not create a child account. Children’s looks consist of clothing images; person photos and virtual try-on are unavailable for these looks. An optional wardrobe profile image is an orientation aid, not a try-on photo.

Enabled iCloud sync also includes wardrobe profiles, images and assignments through Apple CloudKit. Full backups include this data too. This differs from the personal account profile: its optional display name and profile photo remain local. Parents should provide only necessary details. Managing clothing is distinct from minors using the app or AI themselves; outstanding requirements are described in the minors section.

iOS app: sharing look images and requesting access

When you choose to share a look, the app creates a PNG locally from existing images, such as a look card or clothing collage. This starts no new AI job. The generated file does not copy private source metadata; full backups may include it. Try-on images and clothing with verified AI-editing history are labelled in the export. Children’s exports contain no person try-ons. Choose a destination in the system share menu or save to Photos. The selected recipients’ terms also apply; deleting in MixMyLook does not remove those copies.

A wardrobe backup is not a full personal-data access response. Contact the privacy contact for account, consent, credit and AI-job data. The in-app request opens an email app; it sends nothing and attaches no data automatically.

iOS app: optional iCloud synchronisation

You can enable iCloud separately in settings. Only then are clothing and accessory details, original and edited images, person photos and the default-photo reference, saved outfits and completed try-on images transferred to Apple CloudKit in your Apple account’s private area. Technical account and record identifiers, checksums, change states and deletion markers support identification and synchronisation. All participating devices must run an updated app version; older versions may not honour the cloud-deletion block. Devices must use the same Apple and MixMyLook accounts. Data counts towards your iCloud storage.

Personal account profile details, passwords and session keys, pending AI jobs, the credit ledger, the unsaved outfit draft and external backup files are not synchronised. The app makes a local recovery copy before the first sync. Offline changes or insufficient storage may leave data only on the device for a time. Immediate background synchronisation is not guaranteed.

The purpose is the device synchronisation you request (Article 6(1)(b) GDPR, where necessary for that function). Apple processes data for iCloud under its applicable terms. Exclusively European processing or verified end-to-end encryption for every data type is not promised. Specific provider roles, transfer safeguards and provider log retention remain to be reviewed.

Disabling sync stops further synchronisation but does not delete existing cloud data. Individual deletions propagate while sync is enabled; unreferenced image files can remain until full cloud deletion. The separate iCloud deletion function removes the collection and its image files. A minimal blocking record remains without a fixed automatic deletion period to prevent updated devices from uploading again; reactivation of this deleted account area is not currently supported. Local data and exports remain. The current account-deletion flow first requires successful deletion of the associated iCloud collection. Sync is not an independent backup.

iOS app: Apple purchases, image credits and voice minutes

The Apple and Supabase purchase integration is tested through Apple sandbox purchases in private testing. This is not a public sales launch. Processing includes account, product and transaction identifiers, subscription periods and server-side image-credit and voice-time entries. Apple processes details in its purchase dialogue; MixMyLook does not receive card numbers. Balances, reservations, job identifiers, times, status and technical receipts are linked to your account for limits, restoration and protection against duplicate entries.

Image credits and voice minutes are separate balances. A local journal or display does not replace a confirmed server-side entry. Purchase and balance records are not part of wardrobe iCloud sync or exported wardrobe backups. Resetting a wardrobe does not cancel a subscription. Cancel an Apple subscription separately, including when deleting your account. The specific contractual and statutory retention periods for transaction and billing records still need to be established; local deletion does not automatically erase Apple’s records.

Use from age 13: protecting minors

MixMyLook is intended for people aged 13 and over. This does not mean every online feature has been cleared for minors. The current test version has no verified age-assurance or parental-authorisation process.

In Germany, where an online service is offered directly to a child and processing relies on consent, a parent or guardian must provide or authorise that consent below age 16 (Article 8 GDPR). This particularly concerns the optional AI image processing described here. An App Store age rating, Apple account or simple confirmation checkbox does not replace verification. Other legal bases and the interests of minors require separate assessment.

Approval of these consent-based features for ages 13–15 remains outstanding until a suitable process is implemented and checked. OpenAI guidance additionally requires implementing Zero Data Retention before processing personal data below the applicable age of digital consent. This has not been confirmed for this project. Policy wording does not implement technical access restrictions. See Article 8 GDPR and OpenAI: Under-18 guidance.

In simple terms: your photos are not publicly shared. If you enable iCloud, Apple receives data to sync your devices. If you confirm an AI feature, selected photos go to the listed image services. Do not use photos of other people without the necessary permission. Ask a parent or guardian if unsure, and contact us for help deleting data.

Separately, the OpenAI API agreement requires parental or guardian consent for use by minors, including 16–17-year-olds. A verified process and the required provider settings remain outstanding. Existing AI consent is not evidence of age or parental responsibility. Parent-managed children’s looks without person try-on are a separate case. A parent account does not automatically authorise sending children’s photos to an AI service.

iOS app: sign-in and email delivery

For sign-in, which is required in the current app version, Supabase processes your email address, account ID, authentication data and technical connection and security information. Resend delivers requested one-time codes and recovery emails, processing recipient addresses, message content and delivery information. Password sign-in transmits the entered password to Supabase for authentication. If your version offers Sign in with Apple, Apple processes sign-in and Supabase receives the identity token, provider identifier and shared email or relay address. Session keys are stored in the iOS Keychain. Signing in does not upload the optional local display name and profile photo as a wardrobe synchronisation.

Processing supports sign-in, recovery and account security (Article 6(1)(b) GDPR). Abuse prevention and technical security logs support our legitimate interest in secure testing (Article 6(1)(f) GDPR). Account-based test features require the necessary account data. Account data is retained until account deletion. Exact retention periods for authentication, delivery and provider logs remain to be confirmed.

iOS app: optional AI image processing

Only after your confirmation are the clothing or person photos selected for a particular operation and processing instructions transmitted via Supabase Edge Functions to the OpenAI API. Signing in alone does not upload images. Our own backend does not persist input images; it processes them temporarily for the request. Provider logs are a separate matter.

Optional transmission and AI processing of selected images is based on your consent (Article 6(1)(a) GDPR). You can avoid further AI requests and withdraw consent for future processing in Settings → Privacy & consent or using the contact below. This cannot reverse processing already completed. Declining does not exclude local wardrobe features. Only use person photos you are entitled to process. Try-on images are illustrative and are not used for biometric identification or reliable fit assessment.

OpenAI states that API data is not used for model training by default without explicit permission. Abuse-monitoring logs may contain content and generally be retained for up to 30 days, with possible legal or safety exceptions. Neither Zero Data Retention nor exclusively European processing is confirmed for this project. The settings and terms actually enabled for the service govern its processing.

Acknowledgement of account privacy information and optional AI consent are recorded separately. Supabase stores account ID, purpose, decision, document version, language, app version, server time and request identifier. These records document your decision and are checked for new AI jobs. Withdrawal in Settings → Privacy & consent applies to future processing; completed transfers cannot be reversed. A wardrobe reset preserves these records; account deletion removes them. Final legal classification and evidence-retention requirements remain to be reviewed.

iOS app: automatic clothing details

With separate voluntary consent, new clothing and accessory photos are sent through Supabase to OpenAI during import to suggest a name, garment type, description, colour and visible attributes. This analysis does not redraw the photo and is separate from AI image editing and virtual try-on. It requires a supported active paid subscription and an enabled feature. Without consent, local import, local background removal and manual entry remain available. Person photos, the existing collection, backup restoration and iCloud sync do not trigger this analysis.

Consent applies to your signed-in account across devices until withdrawal or a material change. You can withdraw it separately under Settings → Privacy & consent. New transfers and automatic application of later responses are blocked locally immediately; a pending server update is shown. This does not recall data already transmitted.

The metadata service does not additionally store original photos permanently. Results remain available for recovery for seven days; technical cleanup may occur later. Accepted details remain with the garment and are included in enabled iCloud sync. A minimal job journal remains until account deletion; cost and consent records follow separate rules. OpenAI store:false does not guarantee immediate provider deletion or confirmed Zero Data Retention.

iOS app: optional style profile and local dictation

Under My style you can optionally enter occasions, colours, patterns, fit preferences and exclusions, then review the summary before saving. Confirmed catalog preferences, the setting controlling their use and technical revision identifiers are linked to your account and synchronised between devices through Supabase. This is separate from optional wardrobe sync through Apple CloudKit and from the local personal account profile with its display name and photo. Learning hints derived from saved looks are calculated on your device; this does not train a personal AI model.

You can select, type or locally dictate answers. Speech recognition uses Apple SpeechAnalyzer and SpeechTranscriber on your device. A required language model is downloaded only after your confirmation. Onboarding audio is not sent to OpenAI or saved as audio files.

Only when you explicitly start the separate text analysis and have consented are short answers sent through Supabase to OpenAI. Suggestions are saved only after your confirmation. MixMyLook does not permanently store raw answers or raw transcripts; it stores confirmed catalog preferences and technical job, consent, usage and cost records. The provider applies its own retention rules. You can withdraw this versioned, account-bound consent under Privacy & consent. Without text analysis you can select all preferences yourself.

You can disable use of the profile or reset the style profile separately. Disabling does not delete stored preferences. Resetting removes the profile preferences; a technical deletion and revision marker remains for device synchronisation. This profile reset does not delete clothing or saved looks. Technical text-analysis records currently have no fixed automatic deletion period; account deletion removes the account-related records.

iOS app: optional AI voice styling

Voice styling requires an active Pro subscription, available voice allowance and your separate consent. It is intended for the active adult wardrobe. You deliberately start each conversation. Account-bound consent applies across devices until withdrawal or a material change and is checked again before every conversation.

The current audio connection sends microphone audio directly between your device and OpenAI GPT Live. OpenAI also processes necessary connection data such as your IP address. Earlier app versions relay audio through Supabase. Supabase still checks access and allowance, controls the conversation and temporarily processes mirrored audio and transcript events. For outfit selection, the server receives clothing details from the active adult wardrobe and optional style preferences. Limited relevant clothing details, including descriptions and their provenance, and specifically requested saved looks with names and composition are sent to OpenAI. Clothing and person photos are not sent for this advice; try-on requires a separate image request. OpenAI also receives a pseudonymous safety identifier derived from your account ID. This is not anonymous data.

MixMyLook does not permanently store audio recordings or voice transcripts. Contents are processed temporarily during the conversation; during a technical controller change a limited conversation context may briefly pass through your device memory. The provider may retain contents and technical logs under its rules and active settings. store:false is no promise of immediate deletion or confirmed Zero Data Retention.

Account-related session identifiers, times, status, usage counters, costs and voice-time entries are stored for usage limits and billing. Some technical details are minimised no earlier than seven days after completed and resolved activity. Billing and duplicate-protection receipts and unresolved activity are excluded; there is no blanket deletion of all voice data after seven days. Specific receipt-retention periods still need to be established.

Muting stops microphone transmission. Ending, closing or moving the app to the background ends the conversation. Withdrawal immediately blocks new voice styling on this device and ends an active conversation; a pending server update is shown. It does not recall previously transmitted data. New AI text styling is no longer offered; historical text conversations and results may remain linked to the account. Combining by tags produces suggestions locally.

iOS app: results, job data and retention

Generated images are temporarily made available in private Supabase storage. App access expires one hour after job reservation, not one hour after completion. Technical cleanup runs on later authenticated requests by authorised test accounts. Physical deletion at exactly one hour is not guaranteed; failures or a lack of subsequent requests may extend retention. Results saved on your device remain independently.

Account IDs, job and attempt identifiers, input checksums, status, error details and timestamps support access control, reuse and prevention of duplicate paid requests. The basis is Article 6(1)(f) GDPR, particularly our legitimate interest in abuse prevention and reliable cost control. These metadata currently have no automatic time-based deletion and generally remain until account deletion. A bounded retention policy for ongoing operation still needs to be defined. The one-hour image-access limit is not a deletion deadline for job metadata.

A separate cleanup record containing account ID, job ID, storage path and expiry remains until successful file cleanup, including after account deletion. Non-personal aggregate daily budget counters remain independently.

Cost and error monitoring for image jobs also processes account and job identifiers, model, usage and cost data, timestamp, outcome and provider request identifier (Article 6(1)(f) GDPR: reliable operation and abuse prevention). Cost cleanup documented on 10 September 2026 removes details after 30 days plus possible maintenance delay and on account deletion. Daily aggregates without account IDs remain for operational reporting; they are not categorically described as anonymous. This period does not apply to the job metadata above or to consent and purchase records.

Automatic clothing details, style-profile text analysis and voice styling follow their separately described retention rules. A 30-day period stated for image-cost details does not apply generally to these other records.

iOS app: account and local deletion

“Reset wardrobe” removes digitised contents, including internal recovery copies, and handles the associated iCloud collection through the designated deletion flow. The account, personal account profile, credits and privacy decisions remain. “Permanently delete account” first requires successful deletion of the associated iCloud collection, then removes the Supabase sign-in account and its local data area. For an Apple-linked account, Apple authorisation is revoked; your Apple account itself is not deleted. Account-related profile, test-access, consent and job records are deleted. Other local accounts remain; the technical local-account mapping prevents accidental adoption as a guest.

A failed step means deletion is incomplete. Temporary AI files use a separate cleanup process; immediate physical deletion is not guaranteed. Data on offline devices, external backups, exported images, photo libraries and provider logs are not automatically fully erased. An Apple subscription must be cancelled separately. Use the privacy contact for further access or deletion requests.

Account deletion also covers the account-related style profile and its text-analysis records. Active or unresolved voice activity must pass through the designated closing process; account deletion may remain pending until this is confirmed. Separately resetting the style profile removes its preferences while retaining a technical revision marker for device synchronisation.

Private TestFlight testing

Apple distributes the beta through TestFlight and processes invitation or account data, device and version details, installation and usage data, and crash diagnostics. TestFlight automatically collects and shares crash and usage data with Apple and us as the developer; this cannot be opted out of within TestFlight. With a private email invitation, your name and email address may also be visible to us. Optional feedback can contain text and screenshots; check for personal information before submitting it.

We use available test information to organise testing and fix faults, based on our legitimate interest in a stable, secure app (Article 6(1)(f) GDPR). Apple also processes data for its own purposes under its privacy notices. Apple specifies one year for beta feedback; crash and usage information may be retained until the issues are resolved. Retention for feedback separately kept by us still needs to be defined. MixMyLook account deletion does not automatically delete this information.

Apple: TestFlight and privacy

App recipients and international processing

Recipients or service providers include Supabase for authentication, backend, style-profile synchronisation, voice control and temporary results; Resend for authentication emails; OpenAI for authorised image, clothing-analysis, style-text and voice processing; and Apple for TestFlight, iCloud synchronisation or iCloud backups you choose. Contracting entities and roles must still be finally established from the relevant agreements. Apple acts as an independent controller for some of its own services.

The Supabase project is configured in eu-central-1. This does not establish exclusively European processing: edge execution, support, subprocessors, email delivery and AI services may involve processing outside the EEA, including the US. Providers publish privacy and data processing terms addressing international transfers. The applicability of standard contractual clauses, an adequacy decision or other safeguards to the specific contracts remains to be verified. This notice does not assert that data processing agreements or particular transfer guarantees have been confirmed. You can request information and, where applicable, copies of relevant safeguards using our contact details.

Supabase · Supabase DPA · Resend · Resend DPA · OpenAI API – Data controls · OpenAI DPA · Apple

Outstanding private-beta questions

Final provider and mandatory details, contracting entities and data processing agreements, actual transfer safeguards and regional settings, provider and diagnostic log retention, feedback retention, and a bounded job-metadata retention period remain to be clarified. The flagged website and contact details below also require final review. This policy describes the current state; it does not certify that all legal and technical requirements have been conclusively reviewed.

For the new style-profile, clothing-analysis, voice and purchase flows, the legal basis for profile storage, complete information and consent wording and bounded technical and purchase-record retention periods remain subject to final review. Source review is not current proof of all deployed features or provider data controls.

Website: At a glance

This separate section applies only to visits to the promotional website at mixmylook.app and the previous addresses mixmylook.de and mixmylook.com. Processing in the iOS app and private TestFlight testing is described above. You can read everything without an account. There are no photo uploads, newsletter sign-ups or payments. The outfit demo does not send your choices to a server or call an AI service.

Website: Website delivery and hosting

This landing page is hosted by IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany, using the “Website 5.0” web hosting plan. Delivering the website requires processing connection data, including your IP address.

IONOS’s general web hosting documentation lists the requested file, referrer, browser, operating system, device type, access time and an IP address anonymised on collection. It specifies eight weeks of retention and no transfer of this visitor data outside the EU. These product details still need confirmation for the existing “Website 5.0” plan. IONOS: processing by web hosting.

The purpose is website delivery, stability and security. Where personal data is processed, the legal basis is Article 6(1)(f) GDPR: our legitimate interest in an accessible, secure website. The necessary connection data is transmitted automatically; without it, the website cannot be delivered.

The hosting provider processes data as part of providing the service. Final verification of the data processing agreement under Article 28 GDPR and the privacy-related hosting configuration remains outstanding; completion of that review is not asserted here.

Website: IONOS WebAnalytics — pending verification

IONOS describes WebAnalytics as enabled by default, using either log files or a pixel and, according to the provider, no cookies. Whether and how the “Website 5.0” plan enables it for these domains has not yet been verified. IONOS: WebAnalytics.

The website code itself does not embed an analytics service. Host-side statistics still need to be checked and either disabled where possible or described with their actual technology, legal basis, retention and any necessary consent. A cookie-free implementation does not by itself remove the need for that assessment.

Website: Outfit demo, cookies and storage

The demo only processes fictional garment identifiers, locked pieces and saved combinations in the open page’s memory. They are not sent to us, linked to an account, or stored in cookies, localStorage, sessionStorage or IndexedDB. Reloading or switching languages resets the selection; browser restoration may temporarily preserve the page state.

Separately from the demo, a language manually selected using DE/EN is stored as “de” or “en” under “mixmylook-language” in this browser’s localStorage until you clear website data or select another language. It is not sent to us. Without a saved choice, only the general entry address uses the preferred browser languages; direct language links retain their language. This storage serves your expressly selected language setting.

The animation pause also applies only to the open page. Any storage or access on your device required for the demo is solely for the function you expressly choose (section 25(2)(2) TDDDG). The demo creates no usage profile.

Website: External links and locally delivered content

Fonts are selected from those already on your device. Images, styles and scripts are served from the website’s own webspace. There are no embedded videos, social widgets or externally loaded webfonts.

SOREVIQ and other linked websites load only when you follow a link. Their privacy notices then apply. Your demo selection is not passed on. GitHub is used for development and version control; the delivered website does not load content from GitHub.

Website: No automated decisions

This landing page makes no automated decisions with legal or similarly significant effects and performs no corresponding profiling. The random mixer merely selects sample clothing.