Privacy Policy

1. Introduction, Scope & the Standards We Follow

Your privacy matters to us. This Privacy Policy explains, in plain language, what information our games and our website collect, why we collect it, who receives it, how long we keep it, and how you can control or delete it. It is written to be read — not to be bypassed.

This policy applies to:

• Our games distributed on the Apple App Store (iPhone and iPad) and on Google Play (Android phones, tablets and Chromebooks), including all updates of those apps.
• Our website at www.mimigames.games, including our support and legal pages.
• Our player support channels (email, phone/WhatsApp and the support form).

It does not apply to third-party content or services that we do not operate, such as the Apple App Store, Google Play, or a social network account that you choose to use — those are governed by their own privacy policies.

This policy is designed to align with, and to support compliance with, all of the following:

• Apple App Store Review Guidelines, including Guideline 5.1 (Privacy), 5.1.1 (Data Collection and Storage), 5.1.2 (Data Use and Sharing), 5.1.4 (Apps for Kids) and the rules for apps offering in-app purchase.
• Apple's App Tracking Transparency (ATT) framework introduced in iOS/iPadOS 14.5, and Apple's definition of “tracking”.
• Google Play Developer Program Policies, the Google Play Data Safety section requirements, the Families Policy, and the Google Play Billing requirements for apps that sell digital goods.
• The General Data Protection Regulation (GDPR) and UK GDPR, the California Consumer Privacy Act (CCPA) as amended by the CPRA, and the Children's Online Privacy Protection Act (COPPA), together with other applicable national laws such as PIPEDA and applicable children's codes of practice.

Where a provision of this policy is more protective than the minimum required by a platform or law, we follow the more protective provision. If you are in the European Economic Area, the United Kingdom or Switzerland and additional country-specific rights apply, those rights are in addition to those described here.

2. Key Terms Used in This Policy

3. App-Specific & Version-Based Data Collection

What an app collects is determined by the features its build actually contains — not by this document alone. The sections below that describe advertising identifiers, App Tracking Transparency, the Android Advertising ID, third-party partners, analytics, crash diagnostics, social sign-in and push notifications apply only to builds that integrate the SDK or feature in question.

3.1 Disclosure status by build

3.2 How to check the build you have installed

1. On iPhone or iPad, open the game’s page in the App Store and scroll to App Privacy. It lists the data types the shipped build collects.
2. On Android, open the game’s page in Google Play, scroll to Data safety, and compare it with the table above.
3. If either store page says something different from this policy, treat the store page as the description of your build and tell us at developer@mimigames.games so we can correct the mismatch.

3.3 Our three-surface rule

Apple expects three things to agree: the app binary, the App Privacy answers, and this privacy policy. Google requires the same consistency between the binary, the Data Safety form and this policy. We therefore commit to the following — which is why you can rely on a single policy URL instead of a separate page per version:

• We never ship a build containing an SDK that is not declared for that build.
• We never declare, in a store form or in this policy, a data category the build does not actually collect.
• Before any release that adds or removes a data category, an SDK or a purpose, we update this policy, the App Privacy answers and the Data Safety form in the same release.
• Where a build integrates an SDK, that SDK’s own privacy manifest and required-reason API declarations ship inside the build, so the binary, the label and this policy describe the same behaviour.

4. Your Privacy at a Glance

The short answers to the questions players and parents ask us most often.

5. What Information We Collect

Our games work without an account and are designed around data minimisation. The table below is the complete catalogue of data categories that a Mimi Games app, its integrated SDKs, or our website may process. Read the “Applies when” column together with Section 3: a category applies to you only if your build actually contains the feature that collects it. The current iOS release collects none of them.

5.1 Gameplay data stored only on your device

Settings, sound preferences, level progress, XP, unlocks and cosmetic items are stored locally on your device. They are not transmitted to us or to any third party. If you uninstall the app, that local data is removed with it, and it cannot be recovered by us. Cloud saving, where a title supports it, is described in Section 10 and is handled by Apple Game Center or Google Play Games Services rather than by us.

5.2 What we never collect

Our games do not request, access or transmit any of the following:

• Your name, phone number, postal address or date of birth (unless you voluntarily include them in a support message).
• Your contacts, photo library, camera roll, files or documents.
• Precise GPS location. We never ask for location permission; coarse, IP-derived region may be inferred by ad partners for regional ad content.
• Health, fitness, biometric or religious or political beliefs data.
• Microphone or camera recordings, and no in-game voice or text chat.
• Card numbers, bank details, Apple ID passwords or Google account passwords. Payment credentials never reach our systems — Apple and Google process them as merchant of record.
• Contents of your emails, SMS, call history or other apps.

5.3 How the data is collected

• Automatically by the app and its SDKs as the game runs, in builds that include them.
• With your permission, where a permission is required — most importantly the ATT prompt on iOS and the notification permission on both platforms.
• By you, if you choose to contact our support team or submit a deletion request.

5.4 Where the data is processed

Data is processed on servers operated by Apple, Google, Unity, Meta, InMobi and other providers named in Section 8, primarily in the United States, the European Economic Area and India. Mimi Games does not operate its own public cloud storage for player data; where we hold a record ourselves (for example a support email or a purchase receipt record), it is held in access-restricted company accounts. See Section 19 for international transfer safeguards.

6. iOS: App Tracking Transparency (ATT) and the IDFA

In a build that does track, on iOS or iPadOS 14.5 or later, the app presents an App Tracking Transparency (ATT) prompt before any tracking takes place. The prompt explains that we, and our advertising partners, would like to access your Identifier for Advertisers (IDFA) to show more relevant advertising and to measure whether those ads work.

If you tap “Allow”:

• Our advertising and mediation partners — including Google AdMob, Unity LevelPlay (powered by IronSource), Unity Ads and InMobi, where those SDKs are integrated — may access your IDFA to serve personalized advertising and to measure ad performance, subject to their own privacy policies.
• You may still see non-personalized ads, but the app gains no additional access to your IDFA.

If you tap “Ask App Not to Track” (or decline the prompt):

• Your IDFA is not accessed, and no tracking occurs across other companies' apps and websites.
• Our ad partners fall back to contextual or non-personalized advertising, which is not linked to you across apps or websites.
• No game feature is lost. Purchases, social features, gameplay and support all continue to work exactly the same way.

Other iOS privacy controls you can use, whatever build you have:

• Limit Apple’s own ad tracking: Settings > Privacy & Security > Tracking > Apps Allowed to Request to Track — switch off the individual apps you do not want to ask you. (The label was “Limit Ad Tracking” on earlier iOS versions.)
• Reset the advertising identifier: Settings > Privacy & Security > Advertising > Reset Advertising Identifier (available on recent iOS versions; older versions expose the same control as “Reset Advertising ID” under Privacy & Security).
• Apple Advertising: Settings > Privacy & Security > Apple Advertising — turn off Personalized Ads, and use “Delete Advertising Data” to clear Apple’s ad data.

We do not use fingerprinting, device graphs, or probabilistic multi-app matching in place of ATT, and we do not attempt to circumvent an ATT denial. Where a build we ship requires an App Privacy “privacy nutrition label” or a privacy manifest, those declarations describe the same categories and purposes as this section. Data collected for this section’s purposes is limited to the purposes described here, and is not used for any other purpose. A build that does not integrate a tracking SDK — such as the current iOS release — accesses no IDFA and declares no tracking.

7. Android: Advertising ID (AAID) and Google Controls

On Android builds that serve advertising, ads are supported by the Android Advertising ID (AAID). You are always able to reset it, delete it, or opt out of personalised advertising, and doing so does not reduce any game feature. A build with no advertising SDK does not access the AAID at all.

Our games request only the permissions they need to function, and they do not request background location. In-game, where a title offers it, a Reset Advertising ID or privacy options control performs the same reset from inside the game. When no advertising identifier is available, our ad partners fall back to non-personalized or contextual advertising. If Google Play has flagged a title or session as child-directed, ad partners are instructed to operate in child-directed / non-personalized mode.

8. Advertising, Mediation & Other Third-Party Partners

The partners below are the ones we may integrate to keep the games free, to serve and measure ads, and to improve them. They are listed here so that this policy stays accurate when a build adopts them. None of them is present in the current iOS release. For any given title, only the SDKs actually compiled into that build receive data, and that build’s App Store “App Privacy” answers and Google Play “Data Safety” form are the authoritative per-title disclosure. Where an SDK is not integrated into a build, that SDK receives no data from that build.

8.1 Advertising networks & mediation

Purpose: ad delivery, frequency capping, ad measurement, conversion attribution, and invalid-traffic prevention. These partners act as independent controllers for their own processing.

8.2 Analytics, diagnostics & backend services

8.3 Attribution & marketing measurement

Attribution partners measure whether an install or purchase resulted from an advertising campaign. Where permitted by law and by your platform privacy choices, this can involve the advertising identifier. You can opt out via the same controls in Sections 6, 7 and 15.

8.4 Social features

8.5 Billing & payments

8.6 How we constrain partners

• We configure each SDK to collect only the data it needs, and disable any collection that is not required for a declared purpose.
• We do not build our own cross-app advertising profile, and we do not sell player data.
• We configure ad SDKs for child-directed and under-age treatment where a title is available to children, which restricts them to contextual advertising.
• Each partner processes data under its own privacy policy; you can read each policy using the links above and the partner's own opt-out controls.

9. Analytics, Crash Diagnostics & Performance Data

In builds that integrate them, we use analytics to understand how the games are played, and crash reporting to find and fix faults. These tools record events such as session start, session length, cold or warm start, levels completed, tutorial steps, and feature usage, together with crash stack traces, ANR (app-not-responding) events and performance traces. The current iOS release includes no analytics or crash SDK, so none of this is collected in that build.

• Firebase Analytics / Unity Analytics, where integrated: attach events to a random installation identifier (an App Instance ID) rather than to a person, so sessions can be counted and grouped. The Android Advertising ID may also be used as an analytics identifier where you have not reset it and where permitted; resetting or deleting the AAID severs that link.
• Firebase Crashlytics, where integrated: records the crash, the device/OS version and the stack trace. It does not collect your contacts, files or messages.
• Firebase Remote Config, where integrated: allows us to change game configuration remotely. It delivers configuration values to the app and, where enabled, records that a fetch succeeded.

Analytics data is used to determine what to fix first, to balance difficulty, to measure whether an update improved things, and to detect crashes immediately after an update. It is not used to build an advertising profile of you, and it is never sold. Crash logs and performance traces are typically purged by our providers after 90 days.

You can stop this collection yourself at any time:

• Android: reset or delete the Advertising ID (Settings > Google > Ads), then clear the game’s data (Settings > Apps > [Game] > Storage > Clear data). Clearing data generates a new installation identifier.
• iOS: delete the app and reinstall it to generate a new vendor/instance identifier, and use Settings > Privacy & Security > Advertising > Reset Advertising Identifier where available.
• Either platform: you can also submit a deletion request as described in Section 16.

10. Apple Game Center & Google Play Games Services

Leaderboards, achievements and cross-device progress are provided by the platform, not by us. You only share data here if you choose to sign in to these services inside the game. Both services are optional, and skipping sign-in does not limit gameplay.

10.1 What is shared

• A platform player identifier (Game Center player ID, or Google Play Games player ID) used to attribute your scores and achievements to you.
• Your platform display name and avatar, so the game can greet you and show leaderboards. Mimi Games does not store a copy of these on its own systems.
• Scores, achievement progress, and — where a title enables it — saved game state, synchronised across your devices through Apple or Google.

This data is used only for those social features. We do not use it for advertising, and we do not combine it with our analytics or advertising data sets.

10.2 Android: manage or delete Play Games data

For anything else in your Google account, including Play Games data, use myaccount.google.com/data-and-privacy. You can also sign out of Play Games inside the game at any time, after which no further Play Games data is transmitted from that session.

10.3 iOS: manage or delete Game Center data

Game Center is part of your Apple Account. Apple does not operate a separate Game Center account, so there is no standalone “delete Game Center account” action. You can stop sharing, delete the data a game has stored, or delete your whole Apple Account:

Apple holds this data under its Privacy Policy; see also the Game Center documentation. Leaderboard entries, achievements and saved games that are deleted cannot be restored, and deleting the Apple Account removes them permanently.

11. In-App Purchases: Google Play Billing & Apple App Store IAP

Some of our titles offer optional digital purchases — for example remove-ads upgrades, virtual currency, or subscriptions. All digital purchases are completed exclusively through the Apple App Store or Google Play, using Apple's In-App Purchase (StoreKit) system or the Google Play Billing API. Apple and Google are the merchant of record for these transactions.

11.1 What never reaches us

We do not access, receive or store your card number, bank details, Apple ID password, Google account password, or any full payment credential. Payments are processed, authenticated and charged entirely by Apple or Google under their own terms and privacy notices (Apple Media Services Terms, Apple Privacy Policy, Google Privacy Policy).

11.2 What we do receive

Purchase data is used only for the purposes above. We do not use purchase data for advertising, we do not share it with our ad partners, and we do not build advertising profiles from it.

11.3 Manage subscriptions and auto-renewal

Any subscription auto-renews until cancelled. You can cancel at any time, and access continues to the end of the period you have already paid for.

11.4 Request a refund

Because Apple and Google process the payment, refund eligibility and approval are decided by them, and we cannot issue refunds directly for digital items. If a purchase was made through a store, the fastest route is the store's own refund channel:

• iOS: use the App Store's reportaproblem.apple.com refund request flow, or Apple's refund request guidance.
• Android: open play.google.com/store/account/orderhistory, find the order, and select Request a refund, or read Google Play's refund policy.

In every case, email support@mimigames.games with your order identifier and we will support your request with the store, including unlocking anything that was paid for but not delivered.

11.5 Restore purchases

If you reinstall the app or switch devices, sign in to the same Apple ID or Google account that made the purchase and use the in-game Restore Purchases option where available. Store entitlements are then re-granted automatically, and cached purchase tokens stored on the old device are deleted with that device. Progress that was never synchronised (see Section 10 for Game Center and Play Games saving) cannot be transferred because we never held a copy of it.

11.6 Retention of purchase records

• Entitlement records are kept while your installation is active, and for as long as needed to restore or validate a purchase.
• Non-legally-required purchase records are deleted within 30 days of a verified deletion request.
• Financial records such as order identifiers and amounts are retained for up to 7 years only where tax or accounting law requires it, after which they are permanently deleted.

11.7 Purchases by minors

Where a title is tagged under the Google Play Families Policy, purchases by users under 18 require parental or guardian approval through Google Play's own parental controls, and our apps use no alternative checkout that could bypass it. On Apple platforms, purchases are made through your Apple ID, and Apple's Screen Time, Ask to Buy and Family Sharing controls apply. We do not knowingly collect personal information from children in connection with a purchase transaction.

12. Push Notifications

If a title offers notifications — for example important game updates, maintenance notices or offers — we send them only after you have granted notification permission. Declining permission removes notifications and does not affect any other feature. Notification delivery uses Apple Push Notification service (APNs) on iOS and Firebase Cloud Messaging (FCM) on Android. These services receive the delivery token and delivery metadata, such as whether a message was delivered; they are not used for advertising purposes.

13. Information You Give Us (Support, Email & Website)

This is the only place where you give us personal information, and it happens entirely at your choice. The apps themselves never ask for your name or email address.

Support correspondence is stored in access-restricted company email, is used only to respond to you, and is never sold, never shared with advertising partners, and never used for advertising or marketing lists. We do not add you to a newsletter because you contacted support. We never ask you for your Apple ID or Google password, your passcode, or your full card or bank details — and we never ask for payment information by email. If anyone claiming to be Mimi Games asks for those, do not share them, and report it to support@mimigames.games.

14. Children's Privacy

Our games are intended for users aged 16 and above and are not directed at children under 13. We do not knowingly collect, use, or share personal information from children under 13, and we do not require an account, an email address, or any personal detail to play.

To make that meaningful in practice:

• No behavioural advertising to children. Users known or flagged to be children — including anyone who is identified as under 13, or under the applicable consent age (16 in much of the EEA and UK, 13 elsewhere) — are shown non-personalized and contextual advertising only, and in a build with no advertising SDK they see no advertising at all.
• No IDFA access for children. Where a child-directed or under-age flag is set for a title, ad partners are instructed to operate in child-directed treatment, in which they do not access the IDFA and use contextual advertising only.
• No personal data in analytics. Our analytics events are not linked to a person, and we do not use them to build a profile of a child.
• No chat, no user-generated content, no precise location, and no contacts or photos. The apps do not include any of these features.
• Parental controls. Purchases by minors require approval through the store's own parental controls on both Apple and Google platforms. We implement no alternative checkout.
• No marketing to children. We do not send marketing communications to children and do not run personalised campaigns for them.

Where a title is listed in the Google Play Families program, that listing certifies compliance with the Families Policy, including contextual-only advertising, no interest-based advertising, no interstitials on app open or at the start of gameplay content, no phone-home ads, no data collection beyond the approved data types, and parental approval for purchases. In a build that contains no advertising SDK there are no advertisements to personalise in the first place, and no data is collected from any user, child or adult.

Where a title is not listed in the Apple Kids category it does not use the Kids API, and none of our games require it. In the current iOS release, no data is collected from anyone at all — including children — because the build contains no SDKs. If you are a parent or guardian and you believe a child under 13 has provided us personal information — for example by emailing support — contact us at developer@mimigames.games. We will verify the request, delete the information, and confirm to you. You may also ask us to review which advertising mode was used for a session, and we will check it.

15. Your Privacy Choices & Opt-Outs

You stay in control. Every control below is free, available at any time, and does not reduce any game feature.

15.1 Refuse or withdraw advertising tracking

15.2 In-game controls

Where a title provides an in-game privacy options menu or a “Reset Advertising ID” control, you can revoke consent and reset your identifier from inside the game. In-game options never remove gameplay features, and the current ATT status can be read at Settings > Privacy & Security > Tracking on iOS.

15.3 “Do Not Sell or Share My Personal Information” (California)

We do not sell personal information, and we do not share it for cross-context behavioural advertising as those terms are defined by the CCPA/CPRA. We therefore do not operate a “Do Not Sell or Share” link or a preference toggle. If you have nevertheless enabled Limit Ad Tracking, Ask App Not to Track, or a browser “Do Not Sell” signal, we honour it: you will receive non-personalized ads, and you can email developer@mimigames.games to ask us to confirm how your data has been handled or to request deletion.

15.4 Consent and how we demonstrate it

Where a platform requires consent before personalising ads or enabling tracking, our SDKs are configured to wait for that consent. If consent is refused or withdrawn, advertising falls back to non-personalized delivery. The consent or denial state is stored on your device only, and is transmitted to the relevant ad partner so that it is honoured app-wide.

16. Data Retention, Deletion & Data Deletion Requests

Our games have no Mimi Games account, so there is no in-app account to delete. You still have the right to request deletion of any data associated with your device or installation, and we honour that request. Step-by-step self-service instructions are on our Data Deletion Request page.

16.1 Retention by data type

16.2 Submitting a deletion request

We do not delete data that we are legally required to retain, such as tax and accounting records, but we restrict that retained data to the legal purpose and delete it as soon as the duty expires. We do not discriminate against you for exercising a privacy right, and we do not penalise you for refusing consent or withdrawing it.

17. Data Security Measures

• Encryption in transit: all data is transmitted over HTTPS/TLS connections. We do not request or accept sensitive information over unencrypted channels.
• Encryption at rest: our providers encrypt stored data at rest and manage their own access controls and certifications.
• Data minimisation: we collect only what is needed for the declared purpose, and we do not collect the categories listed in Section 5.2 at all.
• No payment credentials: card and account credentials are handled exclusively by Apple and Google and never reach our systems.
• Access control: where we hold a record ourselves, access is limited to the studio developer for support, legal and accounting purposes. We do not sell data and do not share it with third parties for their own purposes.
• Spam and abuse protection: our support form includes a hidden honeypot field that silently rejects automated submissions, so they are filtered before they reach the support inbox.
• Vendor diligence: we configure third-party SDKs to the minimum collection needed and rely on providers' published privacy and security programmes.
• Incident response: if we discover a breach affecting your data, we will investigate, mitigate, and notify you and the relevant supervisory authority within the time required by applicable law, and provide the information you need to protect yourself.

18. Your Legal Rights

Depending on where you live, you may have the following rights over personal information. Mimi Games holds very little personal information — mainly support correspondence and purchase records — so most requests are straightforward.

How to exercise a right: email developer@mimigames.games with “Privacy Request” in the subject line and tell us which right you want to exercise and which game or email address it relates to. We respond within the period required by applicable law — typically within one month under the GDPR and UK GDPR, and within 45 days under the CCPA/CPRA — and we aim to complete every request within 30 days. We do not charge for this.

California specifics. In the 12 months preceding this update, the categories of personal information we have processed depend on the build and on which of our services you use: in the current iOS release, none, because that build contains no SDKs. Across builds that do integrate SDKs, and across this website, the categories are: identifiers (advertising and device identifiers), internet and other electronic activity (usage and ad-interaction data), commercial information (purchase and entitlement records), approximate geolocation inferred from IP address, and contact information that you provide to us in support correspondence. Our sources are you, our service providers and SDKs, and our advertising partners; our business purposes are advertising and measurement, analytics, app functionality, security and customer support. We do not sell these categories and we do not share them for cross-context behavioural advertising. Each title’s App Privacy section and Data Safety form lists the categories that apply to that specific build.

Automated decision-making. We do not use automated decision-making that produces legal or similarly significant effects on you. Advertising personalisation is performed by our ad partners under their own policies and only where your consent or opt-in state allows it.

Representative in the EEA and UK. Where Article 27 GDPR or its UK equivalent requires us to appoint an EU or UK representative, our current representative details are available on request from developer@mimigames.games.

19. International Data Transfers

Mimi Games is based in Pakistan. Data collected by our SDKs and providers is processed in the countries in which those providers operate, primarily the United States, the European Economic Area and India. Where a provider transfers personal information internationally, it does so under its own data transfer safeguards, including Standard Contractual Clauses where applicable. We do not sell personal information to third parties in any jurisdiction, and we do not transfer support correspondence outside our own company accounts.

20. Changes to This Policy

We update this policy when our practices, our SDKs, or the law change. Material changes — for example a new data category, a new partner, or a new purpose for existing data — will be highlighted at the top of the page and described in a short summary of what changed and why. The “Last Updated” date at the top always reflects the current version.

When this policy changes, we will:

• Publish the revised policy at this same permanent URL, www.mimigames.games/privacy-policy.
• Update the privacy policy link in both the Apple App Store Connect record and the Google Play Console listing for each affected title.
• Update the App Store “App Privacy” answers and the Google Play “Data Safety” form in the same release as the app change, so the policy and the store disclosures never disagree.
• Keep the previous version available on request for a reasonable period, so you can see what changed.

21. Contact Us, Complaints & Escalation

If you have a question, a complaint, or a request about this policy or our handling of your data, contact us and we will respond within 30 days (or sooner, where the law requires). We aim to answer player support questions within 24 hours on business days. We welcome constructive criticism and will explain the decisions behind our practices.

You may also escalate a concern through the store where you experienced it:

• Apple App Store: use Apple's reportaproblem.apple.com or contact Apple Support for what Apple lets you see, control and delete for App Store data.
• Google Play: use the flag an app or review in Google Play, or contact Google Play Developer Support.
• Data protection authority: you may complain directly to the data protection authority in your country of residence or work.

22. Our Commitments (Summary)

• We collect the minimum data needed to run the games, show ads where a build serves them, and support you — and nothing at all in a build with no SDKs.
• We do not require an account, and we do not ask for your name, contacts, photos or precise location.
• On iOS we ask permission before tracking, and if you decline, we stop — without limiting any feature.
• On Android you can reset or delete your advertising ID at any time.
• Children are shown non-personalized ads only, and no IDFA is accessed for them.
• Payment credentials are handled only by Apple and Google; we never see them.
• We do not sell or rent personal information, and we do not share it for cross-context behavioural advertising.
• We keep data only as long as we need it, and we delete it on request within 30 days.
• We keep the app binary, this policy, the store privacy labels and the Data Safety forms in agreement, updating all of them together before the release that changes them.
• A build containing no third-party SDKs collects nothing — which is what the current iOS release does, exactly as its “No Data Collected” label states.
• We never list a partner as active in a build that does not contain it.