MirrorMe — AI hairstyle preview
Effective date: TODO 1 — date · Last updated: 28 September 2026
This policy explains what personal data MirrorMe (the "App") collects, why we collect it, who we share it with, and what rights you have. It applies to the iOS and Android apps and the backend services that support them. TODO 16 — Turkish-language version
The data controller is Fusapp OÜ, a private limited company registered in Estonia (registry code 17058392), Meistri tn 6, Mustamäe, 13517 Tallinn, Estonia. TODO 2 — confirm that Fusapp OÜ is the MirrorMe controller and is the seller / developer named on the App Store and Google Play
For any privacy question or to exercise your rights, contact privacy@fusapp.com. For help with the App itself you can also write to support@fusapp.com.
| Category | Examples | Where it comes from |
|---|---|---|
| Account data | Your account identifier, your email address (if you use Apple's "Hide My Email", this is an Apple relay address), your name, and, for Google accounts, the web address of your Google profile picture. Apple shares your name only the first time you sign in. Our servers keep your account identifier, email address and name; the profile-picture address is held only by Firebase Authentication. | You, via Sign in with Google or Sign in with Apple, through Google Firebase Authentication |
| Photos you provide | The photo you take in the App or choose from your photo library, sent as the complete image file, including any metadata stored in it (see section 3) | You |
| Face analysis results | Whether a face was detected, your face shape and skin tone (each one of five categories), and a confidence score. We keep your face shape, your skin tone and the time of the analysis on your profile. | Derived from your photo by Google's Gemini API at our request |
| Generated images and generation records | The hairstyle images created for you, the style you chose, the status and timing of each request, and the web addresses of your original photo and of the generated image | Created by our service |
| Purchase data | The product you bought, the store (Apple or Google), the store's proof of the purchase (a signed transaction from Apple or a purchase token from Google), your plan, subscription period, expiry and renewal status, your credits, and a random code we create to match store purchases to your account | You, and the Apple App Store / Google Play |
| Service records | Records of the AI requests made for your account (provider, model, estimated cost, duration and outcome); the last daily motivational message shown to you; when your account was created and when it was last active | Created by our service |
| Request data | Your IP address, which Cloudflare (our network provider) receives whenever the App connects to our servers. fal.ai also receives it when the App loads your generated images from fal.ai's network, Microsoft Azure receives it when the App loads the style catalogue images, which we store in Azure Blob Storage, and Google receives it when the App shows your Google profile picture. TODO 12 — confirm that the style images are served from our Azure storage Which style catalogue you browse (men's or women's styles) and any style category you filter by. | Collected automatically when the App connects to these services |
| Crash and diagnostic data | Crash reports, error reports and, on Android, reports that the App stopped responding (section 4) | Collected automatically by Google Firebase Crashlytics, in release versions of the App only |
| Analytics data | App usage events and identifiers (section 5) | Collected automatically by the Google Analytics for Firebase SDK |
| Messages you send us | Your email address and the content of the emails you send to our support or privacy addresses | You |
The App does not add your device model, operating-system version or device identifiers to its requests to our own servers. The App does not ask for access to your location, contacts or calendar, and it does not record audio: the camera is used with sound switched off. The App does not show advertising.
Permissions. The App asks for access to your camera (to take a photo) and for permission to show notifications. The permissions screen says notifications are used to tell you when your hairstyle is ready, but the App does not currently send notifications, and it does not register your device with our servers for notifications. Automatic creation of a push-notification (Firebase Cloud Messaging) token is switched off. On Android, Google's Firebase Cloud Messaging component may still create such a token for this installation of the App and register it with Firebase, because Google Analytics (section 5) stays on and Google's documentation says that on Android both must be switched off to prevent this. We do not read or use this token, and the App does not send it to our servers. On iOS, no such token is created. TODO 17 — ship and verify TODO 7 — remove the notification request or change its text, or implement notifications and update this policy Depending on your device, choosing a photo from your library or saving a generated image to it may also ask for your permission.
This is the most sensitive data the App processes, so we describe it separately.
TODO 3 — legal input needed: confirm whether facial imagery processed this way, and the face-shape and skin-tone classification derived from it, is treated as biometric / special-category data under GDPR Art. 9 and Turkish KVKK Art. 6 in your target markets, and whether explicit consent must be collected in the App before the first upload.
The App uses Google Firebase Crashlytics to tell us when it crashes or runs into an unexpected error, so that we can find and fix the problem.
TODO 8 — product decision and legal input needed: the App has no setting to switch crash reporting off. Decide whether to add one; if not, objections are handled by email as described above. Confirm the legal basis (legitimate interests or consent) together with the Google Analytics question in TODO 9, and whether the identifiers above must be declared as linked to you in the App Store privacy details.
The App includes the Google Analytics for Firebase SDK, and the SDK's automatic data collection is switched on. We have not added any custom analytics events, and we do not send your account identifier, email address or name to Google Analytics. Without any action from you, the SDK collects the following and sends it to Google:
Google Analytics is provided under Google's own Google Analytics terms, separate from the Firebase terms. We do not use analytics data for advertising. TODO 10 — the Google Analytics SDK brings in advertising-related parts: on iOS, Google's on-device conversion measurement component (GoogleAdsOnDeviceConversion); on Android, the permissions for Android's ad-services APIs (ACCESS_ADSERVICES_AD_ID and ACCESS_ADSERVICES_ATTRIBUTION). Confirm what they do when the App never calls them, or remove them, before relying on this sentence
TODO 9 — decision and legal input needed: decide whether MirrorMe uses Google Analytics at all and confirm whether our Firebase project is linked to a Google Analytics property. If it is not used, switch automatic collection off in the App and replace this section with a statement that no analytics are collected. If it is kept, confirm the legal basis (collection currently starts at first launch without asking; consent may be required; decide this together with crash reporting, TODO 8), the data-retention setting, that Google signals and Google Ads links are off, and whether Google acts as our processor or as an independent controller under the Google Analytics terms.
| Purpose | Data used | Legal basis (GDPR) |
|---|---|---|
| Create and secure your account, and sign you in | Account data | Performance of a contract |
| Analyse your face shape and skin tone, show hairstyle suggestions for your face shape, and generate hairstyle previews | Photos, face analysis results, account identifier | Performance of a contract TODO 3 — explicit consent if Art. 9 applies |
| Process purchases and manage your credits | Purchase data, account identifier | Performance of a contract |
| Keep purchase and accounting records | Purchase data | Legal obligation TODO 11 — statutory period |
| Show the style catalogue | Which style catalogue you browse and any style category you filter by | Performance of a contract |
| Show daily motivational messages | Account identifier, the last message shown to you | Performance of a contract |
| Keep the App stable and fix faults | Crash and diagnostic data (section 4) | Legitimate interests TODO 8 |
| Understand how the App is used | Analytics data (section 5) | Legitimate interests; consent where required TODO 9 |
| Prevent abuse, enforce usage limits and control the cost of AI requests | Account identifier, request data, records of the AI requests made for your account | Legitimate interests |
| Operate, secure and back up our servers, including server logs and backups | The data held on our servers, request data | Legitimate interests |
| Answer your messages and requests, including requests to exercise your rights | Messages you send us, account data | Legitimate interests; legal obligation for requests to exercise your rights |
| Comply with the law, and establish or defend legal claims | The data relevant to the case | Legal obligation; legitimate interests |
Do you have to give us your data? You are not required by law to provide personal data to us. Account data and a photo are needed to use MirrorMe: without an account you cannot sign in, and without a photo we cannot analyse your face or create previews. Purchase data is needed only if you buy something. Crash-report and analytics data are collected automatically and are not needed for you to use the App; you can object to them as described in sections 4 and 10.
Automated decision-making. We do not make decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you. The face analysis in section 3 is automated: Google's Gemini model classifies your face shape and skin tone, and we use the result to show you hairstyle suggestions for your face shape and to tailor the hairstyle previews you request. TODO 4 — counsel to confirm whether this classification is profiling and that the Art. 22 statement holds
We do not sell your personal data.
| Provider | What they receive | Purpose |
|---|---|---|
| Google Firebase Authentication | The sign-in token from Google or Apple, your account identifier, email address, name, profile-picture address, and the IP address and app details of the device you sign in from | Sign-in and account management |
| Google Firebase Crashlytics (with Firebase Sessions and Installations) | Crash, error and session data (section 4) | Crash reporting |
| Google Firebase Cloud Messaging (Android only) | If Google's component creates a push-notification token (section 2): the token and the Firebase installation ID | Push-notification registration. We do not use it and send no notifications. |
| Google (Gemini API) | Your photo | Face analysis (face detected, face shape, skin tone) TODO 5 |
| fal.ai | A temporary link to your photo, whose web address contains your account identifier (or the photo itself), and an instruction containing your chosen style, face shape and skin tone; your IP address when the App loads your generated images from fal.ai's network | Hairstyle image generation, and hosting of the generated images TODO 5 |
| Microsoft Azure (Blob Storage) | Your original photos, stored under your account identifier; daily backups of our database; your IP address when the App loads the style catalogue images we store there | Photo storage, backups and hosting of the style catalogue images |
| Scaleway | Everything held on our servers: your profile, generation, purchase and AI-usage records, and server logs | Hosting of our servers and database |
| Cloudflare | All traffic between the App and our servers, including your photos and your IP address | Secure network connection to our servers |
| Microsoft (Microsoft 365) | The emails you send to our support or privacy addresses, including your email address, and our replies | Receiving and storing our email |
Google acts as our data processor for the Firebase services above under the Firebase Data Processing and Security Terms. TODO 12 — confirm the data-processing agreement with each of the other providers, and confirm that no mail service other than Microsoft 365 handles MirrorMe support or privacy email, including our replies (the fusapp.com SPF record also authorises Brevo, and names a Contabo host (vmi1844495.contaboserver.net) that does not currently resolve)
| Company | What they receive | Purpose |
|---|---|---|
| Google Analytics | Analytics data (section 5) | Usage analytics, under Google's Google Analytics terms TODO 9 — Google's role |
| Google and Apple, when you sign in | Your sign-in with your Google account or Apple ID | Sign-in. Google and Apple handle this as independent controllers, under their own privacy policies. |
| Apple (App Store) and Google (Google Play) | Your purchases, which you make with them, and the random code that matches them to your MirrorMe account | Payments and purchase verification. Apple and Google handle payments as independent controllers, under their own terms. |
| Google, when the App shows your Google profile picture | Your IP address | Loading the picture from Google's servers |
We also use OpenAI models to write the general motivational messages shown in the App; no data about you is sent to OpenAI for this. The App and our MirrorMe servers do not send you emails or text messages, and apart from the providers listed in this section they use no analytics or advertising services.
We may also disclose data where we are legally required to, or to establish or defend legal claims.
| Data | Retention |
|---|---|
| Your profile on our servers (account identifier, email address, name, face shape, skin tone, time of the face analysis, last daily message shown, and when your account was created and last active) | Until you delete your account |
| Your Firebase sign-in account | Until you delete your account; Google then removes it from its live and backup systems within 180 days. IP addresses logged by Firebase Authentication are kept for a few weeks. |
| Original photos | No retention period is set yet. Photos are not deleted automatically, and are not deleted when you delete your account. TODO 11 — set and implement a retention period |
| Generated images (held by fal.ai) | At least 7 days by default, according to fal.ai. We do not currently ask fal.ai to keep them for a shorter time, and we cannot currently delete them earlier. TODO 11 — confirm fal.ai's actual retention; set a shorter retention period for each request, or obtain a deletion commitment |
| Generation records (style chosen, status, timing, image addresses) | Not currently deleted automatically or when you delete your account. TODO 11 |
| Purchase and credit records (including the stored Google purchase token or Apple transaction ID) | Not currently deleted automatically or when you delete your account. TODO 11 — statutory accounting period |
| Records of AI requests made for your account (provider, model, cost, outcome) | Not currently deleted automatically or when you delete your account. TODO 11 |
| Server logs (contain your account identifier, storage names that include it, and the full instruction for each generation, including your face shape and skin tone) | Kept in size-limited rotating files (three files of up to 10 MB per service); older entries are overwritten. TODO 11 — confirm no other copies are kept |
| IP addresses received by Cloudflare, and any request logging by our server software | TODO 11 |
| Crash reports and their identifiers | 90 days, after which Google starts removing them from its live and backup systems |
| Firebase installation ID (a random identifier for this installation of the App, which the Firebase components in the App register with Google) | For Firebase Cloud Messaging, which is included in the App, Google states that it keeps installation IDs until the app developer asks for them to be deleted, and then removes them from its live and backup systems within 180 days. We do not currently ask for this, including when you delete your account. Google starts removing the copy attached to crash reports after 90 days (see the row above). TODO 11 |
| Firebase Cloud Messaging token (Android only, if Google's component creates one; see section 2) | TODO 11 (not stated on Google's Firebase privacy page). We do not currently ask for it to be deleted, including when you delete your account. |
| Firebase Sessions data | TODO 11 (not stated on Google's Firebase privacy page) |
| Analytics data | TODO 9 (Google Analytics data-retention setting, section 5) |
| Messages you send us | Stored in our email, which Microsoft 365 hosts (section 7). TODO 11 |
| Backups | A full backup of our database is made daily and stored in Microsoft Azure; our server also keeps up to three recent daily copies and the last five copies taken before each software update. Backups in Azure are not currently deleted automatically, so deleted data remains in older backups. TODO 11 — set a backup rotation period |
Some of our providers, including Google, process data in the United States and other countries outside your own. For Firebase, Google states that it complies with the EU-U.S. and Swiss-U.S. Data Privacy Frameworks and the UK Extension to the EU-U.S. Data Privacy Framework. Where data leaves the European Economic Area, the United Kingdom, or Türkiye, transfers are made under the safeguards permitted by applicable law. TODO 12 — confirm the regions of our Scaleway servers, Azure storage and Microsoft 365 email, the mechanism relied on for each provider (Data Privacy Framework, Standard Contractual Clauses), and the KVKK transfer basis for users in Türkiye.
Depending on where you live, you may have the right to access your data, correct it, delete it, restrict or object to processing, withdraw consent, receive a copy in a portable format, and lodge a complaint with your supervisory authority.
Deleting your account. You can delete your account from within the App, under Profile. Before any of your data is deleted, the App always asks you to sign in again with Google or Apple to confirm that it is you; if you cancel, nothing is deleted. It then asks our servers to delete your profile (including your email address, name, face shape, skin tone and the last daily message shown to you), and then deletes your Firebase sign-in account. If you signed in with Apple, the App also asks Apple to revoke MirrorMe's access to your Apple ID; if you signed in with Google, it disconnects MirrorMe from your Google account. If our servers cannot delete your profile, the App does not delete your sign-in account, so you can try again. TODO 17 — ship and verify, in the App and on our servers Deletion cannot be undone. If you no longer have the App, you can request deletion of your account and its data by writing to privacy@fusapp.com.
What account deletion does not yet delete: your original photos, the generated images held by fal.ai, your generation records, your purchase and credit records, the records of AI requests made for your account, server log entries until they are overwritten, and copies in our backups. Google removes your Firebase sign-in account from its systems within 180 days, and Google starts removing crash reports after their 90-day period. Analytics data, the Firebase installation ID and, on Android, any Firebase Cloud Messaging token are not linked to your account and are not deleted with it (see section 8). TODO 11 — delete these on account deletion, or state why and for how long each is kept Until then, you can ask us to delete this data, except the generated images held by fal.ai, by writing to privacy@fusapp.com. We cannot currently delete those images before they expire under fal.ai's retention (see section 8).
To exercise any other right, including objecting to crash reporting or analytics, contact privacy@fusapp.com.
The list of your generations shown in the App is kept only in memory and is lost when the App is closed.
No system is perfectly secure, and we cannot guarantee absolute security. TODO 13 — add encryption at rest, the access level of the photo storage, and staff access controls once confirmed
MirrorMe is not directed to children under TODO 14 — age; must match the App Store and Google Play age rating you declare, and we do not knowingly collect their personal data. If you believe a child has provided us with personal data, contact us and we will delete it.
We may update this policy. When we do, we will change the "Last updated" date above, and for material changes we will give notice in the App before the change takes effect.
Fusapp OÜ TODO 2
Meistri tn 6, Mustamäe, 13517 Tallinn, Estonia
Registry code 17058392
privacy@fusapp.com
TODO 15 — if you have an EU or UK representative or a Data Protection Officer, name them here.