Privacy Policy

Privacy Policy

Games by MEDIOCRESOFT TECHNOLOGIES - FZCO · Android, iPhone and iPad

Effective date: 10 November 2026
Last updated: 10 November 2026

This privacy policy explains what information is collected when you play our games, who collects it, why it is collected, how long it is kept, and what choices you have.

Our games on Android and on iPhone and iPad do not work in exactly the same way. Where they are different, this policy says so with a label: On Android: or On iPhone and iPad:. A label applies to everything after it in the same item. Everything without a label applies to both.

1. Who we are and which games this policy covers

Our games are published by MEDIOCRESOFT TECHNOLOGIES - FZCO ("we", "us", "our"), a company in the United Arab Emirates. On Google Play, our developer name is "Mediocresoft Technologies".

This policy applies to every game that we publish on Google Play and on the App Store, for example Harbor Smash. It applies to new games too. A game can have its own additional privacy information. If it does, that information is shown in the game or on the game's store page.

We decide which partner tools are part of our games. We are responsible for the processing of personal information described in this policy. Each partner named in section 10 is also responsible for its own use of the information it collects.

Contact: work.uae.mediocresoft@gmail.com

2. Summary

  • You do not create an account. Our games do not ask for your name, e-mail address, phone number, postal address or age.
  • Your game progress is saved on your device. Our games have no cloud save. If backup is switched on for your device, your backup can contain a copy of the game data (section 3).
  • We do not run our own game servers. Our games send information to the servers of our partners, not to a server of ours. We can see reports from some partners, for example Google Analytics for Firebase.
  • Our games show ads and use analytics. Other companies ("partners") provide these services through software kits (SDKs) inside the games. These SDKs collect information about your device and about how you use the game, and they send it to the partners.
  • Partners collect information about crashes and errors (section 4g).
  • On iPhone and iPad: iOS asks for your permission before a game can track you. You can say no and still play the whole game (section 8a).
  • On Android: our games do not show a tracking prompt. You can delete or reset your advertising ID in the Android settings (section 8b).
  • In the European Economic Area, the United Kingdom and Switzerland, a consent form from Google can be shown (section 9).
  • Google Play (on Android) or Apple (on iPhone and iPad) handles all payments. We never see your card or bank details.
  • We do not sell your personal information for money. Under some US state laws, giving device identifiers to ad partners can count as "selling" or "sharing" (section 12).

3. Information stored on your device

a) Game data

Each game saves your progress in a file on your device. The file can contain:

  • your coins or other game currency, and the items and boosters you have;
  • your lives and the timers for lives;
  • the levels you finished, your stars or scores, and rewards you claimed;
  • how many times you have played;
  • which tutorials you have seen;
  • your settings, for example music, sound effects and vibration;
  • which purchases you made that you keep, for example No Ads;
  • counters and dates for game features, for example daily rewards, events, videos with rewards watched today, and the request to rate the game.

The file does not contain your name, your e-mail address, an account ID, a device ID or an advertising ID. Our games do not send this file to us or to our partners.

b) Other information on your device

  • Settings of the ad tools, for example whether you bought No Ads, and timers for ads.
  • A copy of the latest remote settings (section 7).
  • Your answer to Google's consent form, if the form was shown (section 9). Google's consent tool stores it.
  • On iPhone and iPad: your answer to the tracking prompt (iOS stores it), and the transaction IDs of recent purchases of items that are used up. The game uses these IDs to make sure that it gives each item only once.
  • Partner SDKs also store their own data on the device, for example their own IDs.

Our games read the amount of memory (RAM) of your device. They use it to choose the graphics quality and to decide which ad tools to start. The game's own code does not send this information anywhere.

c) Reset progress

Some games have a RESET PROGRESS button in their settings. It starts your progress again from the beginning.

  • Coins and items, including coins and items that you bought, are lost.
  • Purchases that you keep, for example No Ads, are not lost.
  • A reset does not delete the information in section 3b. It does not delete information that partners have already collected.

d) Deleting a game and device backups

  • When you delete a game, its save file and its other data are deleted from your device.
  • On Android: if backup is switched on for your device, the game data can be included in your backup, for example in your Google account. The data can then come back when you install the game again.
  • On iPhone and iPad: the game data can be included in iCloud backups or computer backups of your device.
  • Backups are controlled by you and by Google or Apple. We do not receive them.

4. Information collected by our partners

The partner SDKs in our games can collect the following information and send it to the partner. Section 10 says which partners are used on Android and which on iPhone and iPad.

a) Identifiers

On Android:

  • The Android advertising ID. Our games declare the Android permission that lets SDKs read this ID. The ad SDKs, AppMetrica (part of the Yandex Ads SDK), Google Analytics for Firebase and SolarEngine can collect it.
  • The App Set ID. This ID is the same for all apps from the same developer on your device. GameAnalytics, AppMetrica and Google SDKs can collect it. Under Google Play rules, the App Set ID may be used only for analytics and fraud prevention. It must not be used for personalised ads or to measure ads.
  • A hashed form of the Android ID. Hashed means that the ID is changed by a calculation so that the original ID cannot be read. Google Mobile Ads can use it.
  • IDs that the SDKs create: the Firebase app instance ID and Firebase installation ID, the GameAnalytics user ID, SolarEngine IDs, a Unity installation ID, an anonymous Unity player ID (section 7), and IDs created by ad networks.

On iPhone and iPad:

  • Apple's Advertising Identifier (IDFA), only if you choose "Allow" on the tracking prompt (section 8a).
  • Apple's Identifier for Vendors (IDFV).
  • IDs that the SDKs create: the Firebase app instance ID and Firebase installation ID, IDs created by ad networks, and SolarEngine IDs when SolarEngine is switched on (section 10).

The games' own code does not read any device ID or advertising ID. Only the partner SDKs do this.

b) Device and network information

For example: device maker and model, operating system and version, language, time zone, screen size, network type (Wi-Fi or mobile data), mobile carrier and IP address.

The Unity game engine can also send anonymous hardware statistics to Unity Technologies: device model, operating system, graphics chip and memory.

c) Approximate location

Country, region or city, calculated from your IP address. Our games do not ask for permission to use your precise location (GPS) and do not collect it.

d) Game usage

Our games send events about how you play to Google Analytics for Firebase. On Android: the same events also go to GameAnalytics.

Examples of events:

  • game start;
  • level start, level win and level fail, with the level number;
  • actions in a level, for example a shot or a move, with the level number;
  • an offer to continue a level, and whether you accepted it;
  • booster or item used, with its name;
  • ad shown, with the place in the game where it was shown, and video watched to earn a reward;
  • purchase, with the product ID (section 11);
  • rewards claimed, progress in game events, tutorial steps, screens opened, and requests to rate the game.

Google Analytics for Firebase also records some events by itself, for example the first start of the game, sessions and how long you use the game. On Android: GameAnalytics can also record sessions by itself.

e) Advertising information

  • The ad SDKs collect information about ads, for example which ads were requested, shown and tapped, the ad network, the ad format, and rewards from videos you chose to watch.
  • For ads shown through AppLovin MAX, our games send the ad network, the ad unit, the ad format and the revenue of the ad (in US dollars) to Google Analytics for Firebase.
  • Our games send ad revenue information (for example the ad network, the ad format, ad IDs, the revenue and the currency) to SolarEngine. On iPhone and iPad: this happens only when SolarEngine is switched on (section 10).

f) Purchase information

When you buy something, the product ID is sent in an event to Google Analytics for Firebase. Section 11 explains which other partners receive purchase information. Payment card details are never included.

g) Crash, error and performance information

  • On iPhone and iPad: Firebase Crashlytics collects crash reports. A crash report contains information about the app and the device at the time of the crash, for example the free memory. Firebase Crashlytics also collects errors that the game did not handle.
  • On Android: our games do not include Firebase Crashlytics. The AppMetrica SDK inside the Yandex Ads SDK can send crash and performance reports about the ad SDK to Yandex.
  • Other partner SDKs can collect information about their own errors and performance, for example how long ads take to load.

h) Ad reports

Some ads have a button to report the ad. If you use it, the ad network receives the information that you send in the report.

5. Information that is not collected

Our games do not collect:

  • your name, e-mail address (unless you e-mail us), phone number or postal address;
  • your age or date of birth;
  • your precise location (GPS);
  • your contacts;
  • your photos, videos or other files;
  • sound from the microphone or images from the camera;
  • payment card or bank details;
  • health information.

Our games do not have permission to use your location, camera, microphone or contacts. Because of this, the partner SDKs in our games cannot use them either.

6. Device permissions

On Android: our games use these permissions:

  • Internet access, network state and Wi-Fi state: to connect to the internet and to check whether a connection exists.
  • Advertising ID (com.google.android.gms.permission.AD_ID): lets the SDKs read the Android advertising ID.
  • Google Play billing: for purchases through Google Play.
  • Vibration: for vibration effects, if vibration is on in the game's settings.

On Android: partner SDKs and the game engine can add more permissions when a game is built, for example permissions for Android's ad services, or storage permissions. Our games save only in their own app folder. They do not read or write your photos or other files. If Android asks you for a storage permission, you can refuse it. The game's page on Google Play shows the full list of permissions.

On Android: our games do not ask for permission to use location, camera, microphone, contacts or your phone, and they do not send notifications.

On iPhone and iPad: the only permission that our games ask for is the tracking permission (App Tracking Transparency, section 8a). Our games do not ask for permission to use location, camera, microphone, contacts or photos, and they do not send notifications.

7. How the information is used

  • To show ads. We earn money from ads. This money pays for making the games. Ads can be personalised. Where the law requires consent, Google's consent form asks for it (section 9).
    • On iPhone and iPad: ads can use the IDFA only if you choose "Allow" on the tracking prompt (section 8a).
    • On Android: you can limit personalised ads in the Android settings (section 8b).
  • To measure ads. This means to count ad views and taps, to calculate ad revenue, and to find out which ad campaign led to an install of a game (attribution). Google Analytics for Firebase and SolarEngine are used for this.
    • On iPhone and iPad: SolarEngine is used for this only when it is switched on (section 10). Our games also list ad networks for Apple's SKAdNetwork. SKAdNetwork tells an ad network that an ad led to an install, without giving it your IDFA. The Firebase Analytics SDK also contains Google's on-device conversion measurement, which can help to measure whether an ad campaign led to an install.
  • To check the quality of ads and to prevent fraud. For example, AppLovin Quality Service checks the ads shown through AppLovin MAX.
  • To understand how players use our games, so that we can improve levels, difficulty and features (analytics).
  • To find and fix crashes and errors.
  • Remote settings. We can change some game settings without an app update, for example how often ads are shown and which ad tools are used.
    • On Android: our games use Unity Remote Config. To get the settings, the game signs in to Unity Gaming Services without an account (anonymous sign-in). This creates an anonymous Unity player ID.
    • On iPhone and iPad: our games use Firebase Remote Config. A remote setting can switch on SolarEngine (section 10) and can switch off the request to rate the game.
  • To deliver the items you buy and to restore purchases (section 11).
  • To ask you to rate the game. The rating window comes from Google Play or from the App Store. Google or Apple handles the rating.
  • To answer your e-mails (section 16).

8. Tracking and ad personalisation choices

a) On iPhone and iPad: App Tracking Transparency

  • When a game starts, while the loading screen is shown, iOS shows Apple's tracking prompt. It asks if the game may track your activity across other companies' apps and websites.
  • The ad, analytics and purchase tools start after you answer the tracking prompt. If you do not answer within a short time, the tools start anyway. Until you choose "Allow", they do not get the IDFA.
  • The prompt is shown only once. iOS remembers your answer.
  • If you choose "Allow", the IDFA is available to the game's partners. They can use it, together with information from other apps and websites, to show you personalised ads and to measure ads.
  • If you choose "Ask App Not to Track", the IDFA is not available, and our partners must not track you across other companies' apps and websites. You still see ads, but they can be less relevant to you. You can still play the whole game.
  • Your answer does not switch off Google Analytics for Firebase or Firebase Crashlytics. They run with either answer. If you did not choose "Allow", they work without the IDFA.
  • To change your choice at any time, open the Settings app of your iPhone or iPad: Privacy & Security > Tracking, or Settings > [name of the game] > Allow Tracking.

b) On Android: advertising ID and ad privacy settings

  • Our games do not show a tracking prompt. The partner SDKs start when the game starts.
  • You can control your advertising ID in the Android settings. The names of the menus can be different on your device. They depend on the device maker and the Android version.
  • Open Settings > Google > All services > Ads, or Settings > Privacy > Ads.
  • Choose "Delete advertising ID" to remove the ID. Apps then receive a row of zeros instead of the ID, and no new ID is created.
  • Choose "Reset advertising ID" to get a new ID.
  • On some older Android versions: open Settings > Privacy > Advanced > Ads and turn on "Opt out of Ads Personalization".
  • In Settings > Google > All services > Ads > Ads privacy, you can also switch off "Ad topics", "App-suggested ads" and "Ad measurement". Some ad SDKs in our games can use these Android features.
  • After you delete the advertising ID or opt out, you still see ads, but they can be less relevant to you. You can still play the whole game.
  • These settings do not switch off Google Analytics for Firebase, GameAnalytics, SolarEngine, AppMetrica or Unity Gaming Services. They can continue to work with the other IDs in section 4a.

c) The No Ads purchase

  • Some games sell No Ads. No Ads removes banner ads and the full-screen ads that are shown between screens.
  • Videos with rewards are still offered. You choose whether to watch them.
  • No Ads does not switch off the partner SDKs.

9. Ad consent in the European Economic Area, the United Kingdom and Switzerland

a) The consent form

  • When a game starts, it asks Google's consent tool (Google User Messaging Platform) whether a consent form is needed where you are. If it is needed, the game shows Google's consent form.
  • On iPhone and iPad: the consent form comes after the tracking prompt.
  • In the form, you can agree or not agree to the use of your information for personalised ads and related purposes. The form can also let you make a choice for each purpose and each partner.
  • If you do not agree, the ad partners show non-personalised or limited ads, according to their own rules.

b) What our games do and do not do with your answer

  • Our games start the ad SDKs at the same time as the consent check. They do not wait for your answer. Ads can therefore be requested before you answer. These ads are requested without a stored answer, and each partner then applies its own rules.
  • The games' own code does not pass your answer to the partners. Google's consent tool stores your answer on your device. Partner SDKs that support this can read it there.
  • The analytics tools start without waiting for your answer, and the games do not pass your answer to them.
    • On Android: Google Analytics for Firebase, GameAnalytics, SolarEngine, AppMetrica and Unity Gaming Services.
    • On iPhone and iPad: Google Analytics for Firebase, Firebase Crashlytics, Firebase Remote Config, and SolarEngine when it is switched on.
  • If you bought No Ads, the game does not show the consent form. Videos with rewards and the partner SDKs still run.

c) How to change your choice

  • At the moment, our games have no button to open the consent form again.
  • You can delete the game and install it again. The next time the game starts, the consent form is shown again if it is needed where you are. In some cases the form is not shown again, for example if the game's data comes back from a device backup, or if your No Ads purchase is active. Deleting the game also deletes your saved progress, unless the data comes back from a backup.
  • You can limit personalised ads at any time with the device settings in section 8.
  • You can e-mail us (section 22). Our games have no accounts, so we cannot change the choice that is stored on your device. We will answer your questions.

10. Our partners

The following companies provide SDKs in our games. Each company handles information according to its own privacy policy. "Used on" shows whether the SDK is in our Android games, in our iPhone and iPad games, or in both. Not every game uses every partner.

Each partner has its own terms for app developers and its own privacy policy. We use partners whose terms and policies give protection that is the same as or equal to the protection described in this policy.

Ads and ad mediation (ad mediation tools choose which ad network shows each ad)

Ad networks that can show ads through AdMob or AppLovin MAX. Which of them actually show ads depends on our settings in AdMob and AppLovin MAX. We can change these settings at any time.

Analytics, attribution, crash reporting and remote settings

  • Google Analytics for Firebase (Google). Used on: Android, iPhone and iPad. On iPhone and iPad: it contains Google's on-device conversion measurement. https://firebase.google.com/support/privacy
  • Firebase Crashlytics and Firebase Remote Config (Google). Used on: iPhone and iPad. https://firebase.google.com/support/privacy
  • GameAnalytics (GameAnalytics ApS). Analytics. Used on: Android. https://www.gameanalytics.com/trust/privacy-notice
  • AppMetrica (YANDEX LLC, Russia), part of the Yandex Ads SDK. Used on: Android. Yandex uses it for statistics about its ad SDK. It can collect device identifiers (including the Android advertising ID and the App Set ID), device and app information, information about how the game was installed, information about in-app purchases, and crash and performance reports of the ad SDK. It cannot collect GPS location, because our games have no location permission. https://yandex.com/legal/confidential/en/
  • SolarEngine (Reyun). Install attribution and analytics, with SolarEngine's remote settings tool. Used on: Android, iPhone and iPad. https://www.solar-engine.com/privacyPolicyEN.html
    • On Android: SolarEngine is switched on.
    • On iPhone and iPad: SolarEngine is part of the game but is switched off. We can switch it on with a remote setting, without an app update.
    • When SolarEngine is on, it collects device identifiers and device information, and the game sends it ad revenue information (section 4e). The games' own code does not send purchase information to SolarEngine.
  • Unity Gaming Services: Unity Remote Config and Unity Authentication (Unity Technologies). Remote settings, with anonymous sign-in. Used on: Android. https://unity.com/legal/privacy-policy

Purchases

  • Google Play Billing (Google). Used on: Android. Google processes all payments. https://policies.google.com/privacy
  • Apple App Store and StoreKit (Apple Inc.). Used on: iPhone and iPad. Apple processes all payments. https://www.apple.com/legal/privacy/en-ww/
  • Unity In-App Purchasing (Unity Technologies). Used on: Android, iPhone and iPad. It connects the game to Google Play or to the App Store. On Android: because Unity Gaming Services is started for remote settings, Unity In-App Purchasing and Unity Gaming Services can also send technical diagnostics to Unity. https://unity.com/legal/privacy-policy

Other

11. Purchases

a) Payments

  • On Android: Google Play processes the payment.
  • On iPhone and iPad: Apple processes the payment.
  • We never receive your card or bank details.
  • Unity In-App Purchasing connects the game to the store when the game starts. We do not run our own server, and our games do not send your receipts to us.

b) What our games send about purchases

  • To Google Analytics for Firebase: an event with the product ID. The games' own code does not send the price, the currency or the order number. Google Analytics for Firebase can also record in-app purchases by itself.
  • On Android: GameAnalytics receives an event with the product ID. AppMetrica (part of the Yandex Ads SDK) can collect information about in-app purchases by itself.
  • On iPhone and iPad: when the Unity Ads SDK is running, Unity In-App Purchasing passes the details of each transaction to Unity Ads for ad measurement. These details are the transaction ID, the product ID, the product information from the App Store (including its price), the transaction date, and the transaction data that Apple provides, including the transaction data signed by Apple.
  • The games' own code does not send purchase information to SolarEngine, to AppLovin or to the other ad networks.

c) Restoring purchases

  • Purchases that you keep, for example No Ads, can be restored. Use RESTORE PURCHASES in the game's settings or shop.
  • Our games also check your purchases with the store each time they start, and give back purchases that you keep. Each time this happens, the purchase event in section 11b can be sent again.
  • Items that are used up when you receive them, for example coins, cannot be restored.

12. US state privacy laws ("sale" and "sharing")

  • We do not sell your personal information for money.
  • Under some US state laws, for example in California, giving information to ad partners for personalised ads can count as "selling" or "sharing" personal information. In this sense, our games can "sell" or "share" identifiers, device information, approximate location, game usage and advertising information with the ad partners in section 10. On iPhone and iPad: purchase details are also shared with Unity Ads (section 11b).
  • Categories of personal information collected in the past 12 months:
    • Identifiers (advertising ID or IDFA, IDFV, App Set ID, IP address, IDs created by the SDKs). Source: your device, through the partner SDKs. Disclosed to our analytics, crash-reporting and remote-settings providers. Sold or shared with the ad networks and ad mediation providers in section 10.
    • Internet or other electronic network activity (game events, ad interactions, device and network information). Same sources and recipients.
    • Approximate location calculated from your IP address. Sold or shared with the ad networks.
    • Commercial information (product IDs of purchases; on iPhone and iPad also the transaction details in section 11b). Disclosed to our analytics providers. On iPhone and iPad, shared with Unity Ads for ad measurement.
    • Your e-mail address and name, if you e-mail us. Source: you. Not sold or shared.
  • We do not collect sensitive personal information as defined in California law. We do not create profiles about you. Ad partners can create them under their own privacy policies. Section 7 lists the purposes, and section 14 says how long information is kept.
  • To limit this:
    • On iPhone and iPad: choose "Ask App Not to Track" (section 8a). Partners then do not receive the IDFA and must not track you across other companies' apps and websites.
    • On Android: delete your advertising ID, or opt out of ads personalisation (section 8b).
  • Our games have no opt-out switch of their own, and they do not send an opt-out signal to the partners. You can e-mail us (section 22). Our games have no accounts, so we cannot connect your request to your device. We will reply and explain the settings above.
  • We do not knowingly sell or share the personal information of people under 16.
  • Requests from US residents: see section 15. You can let an authorised agent send a request for you. We can ask the agent for proof that you gave permission, and we can ask you to confirm the request. If we refuse a request, you can appeal by replying to our answer. We will answer the appeal within 60 days.
  • We will not treat you differently because you use these rights.

13. Legal bases (European Economic Area, United Kingdom and Switzerland)

  • Consent: personalised ads. Where consent is needed for the use of identifiers for ads, the ad partners rely on your answer in Google's consent form. On iPhone and iPad: also tracking, through Apple's tracking prompt.
  • Legitimate interests: analytics to improve our games, crash reporting, ad measurement and attribution, checking the quality of ads, security and fraud prevention, remote settings, non-personalised ads (which pay for the games), and answering e-mails. Our legitimate interest is to offer free games that work well and that are paid for by ads. You can object to this use (section 15).
  • Contract: delivering the items you buy and restoring purchases.
  • You do not have to give us any personal information. No law or contract requires it. If you refuse tracking or personalised ads, you can still play the whole game, but the ads can be less relevant to you.
  • We do not make decisions about you that are based only on automated processing and that have legal or similarly significant effects on you.

14. How long information is kept

  • Information on your device: until you delete the game. RESET PROGRESS overwrites the save file. Copies in device backups are kept as long as the backup is kept.
  • Google Analytics for Firebase: event data that is linked to an app instance ID is kept for no longer than 14 months. Reports with totals, which do not show single users, can be kept longer.
  • Firebase Crashlytics (iPhone and iPad): crash data is kept for 90 days. Then Google starts to delete it.
  • Firebase installation IDs (used by Google Analytics for Firebase on Android, iPhone and iPad, and by Firebase Remote Config and Crashlytics on iPhone and iPad): kept until they are deleted with Firebase's tools. After deletion, Google removes them within 180 days.
  • GameAnalytics (Android): event data up to 12 months; summarised player data up to 1 year; shortened IP addresses up to 30 days.
  • Unity Ads: data linked to an installation ID up to 12 months; transaction records up to 180 days.
  • Unity Gaming Services (Android): the anonymous Unity player ID and its sign-in record are kept in our Unity Gaming Services project until we delete them.
  • AppLovin: typically up to 2 years. Data linked to a device is often kept for a shorter time.
  • SolarEngine: generally no longer than 2 years.
  • Bigo Ads and Mintegral: no longer than 2 years.
  • Chartboost (iPhone and iPad): no longer than 365 days.
  • InMobi (iPhone and iPad): up to 13 months.
  • Liftoff: 30 days. During these 30 days, the data is stored in a form that does not directly show who you are (pseudonymised). Then it is deleted.
  • Google ads: Google removes part of the IP address from ad data in its server logs after 9 months, and cookie information after 18 months.
  • BidMachine, DT Exchange, Meta, Pangle, Yandex Ads and AppMetrica: as described in their privacy policies (section 10). Some of them do not give a fixed period.
  • E-mails to us: only as long as we need them to answer you. Then we delete them.

15. Your rights and how to use them

Depending on where you live (for example the European Economic Area, the United Kingdom, Switzerland, California or other US states), you can have the right to:

  • know what personal information is processed about you, and get a copy of it;
  • receive it in a structured, commonly used and machine-readable format, and have it sent to another company (data portability);
  • correct it;
  • delete it;
  • restrict or object to its processing;
  • withdraw your consent at any time. This does not affect the lawfulness of processing before you withdrew it;
  • opt out of the "sale" or "sharing" of personal information for targeted advertising;
  • not be treated differently because you use these rights.

Things you can do yourself

  • Game data on your device: delete the game, or use RESET PROGRESS if the game has it (section 3).
  • On iPhone and iPad: allow or stop tracking in the Settings app (section 8a).
  • On Android: delete or reset your advertising ID, or opt out of ads personalisation (section 8b).
  • Ad consent: see section 9c.
  • AppLovin: use AppLovin's privacy request page: https://applovin.com/en/privacy-data-request
  • Unity Ads: tap the Data Privacy icon inside a Unity ad.
  • Other partners: their privacy policies (section 10) explain how to contact them.

Asking us

  • E-mail us at work.uae.mediocresoft@gmail.com. Please tell us what you want us to do, which game you play, and whether you play on Android or on iPhone or iPad.
  • To protect you, we can ask you for information that confirms that the request comes from you.
  • Our games have no accounts, so there is no account to delete. Our games also do not show you the IDs that partners use. Because of this, in most cases we cannot find your information in our partners' systems. We will tell you how to contact each partner directly, and we will help you with your request.
  • We answer requests within one month.
  • You also have the right to complain to the data protection authority in your country.

16. E-mails to us

  • Some games have a SUPPORT button. It opens your e-mail app with a new message to us.
  • The game does not add any device information, ID or game data to the message.
  • If you send us an e-mail, we receive your e-mail address, your name if your e-mail shows it, your message and anything you attach.
  • We use this only to answer you. We keep it only as long as we need it to answer you (section 14).

17. Children

  • Our games are made for a general audience. They are not directed at children under 13.
  • Our games do not ask for your age.
  • Our games tell Google's ad tools that they are not directed at children.
  • We do not knowingly collect personal information from children under 13 (or under 16 in the European Economic Area).
  • If you are a parent or guardian and you think that your child has sent us personal information, for example by e-mail, please contact us. We will delete it, and we will help you with partner data (section 15).
  • If we publish a game that is directed at children, that game will have its own privacy policy.

18. Transfers to other countries

We are based in the United Arab Emirates. Our partners are based in several countries, including the United States, Singapore, China, Denmark, the United Kingdom, the United Arab Emirates and Russia (AppMetrica, Android only). Their SDKs send information to their servers, which can be in a country other than your own.

The European Commission has not adopted an adequacy decision for the United Arab Emirates, China, Russia or Singapore. Some of our US partners are certified under the EU-U.S. Data Privacy Framework, which the European Commission has recognised as adequate. Other partners describe the legal safeguards they use in their privacy policies, for example the Standard Contractual Clauses of the European Commission. You can ask us for information about the safeguards for a partner (section 22).

19. Security

  • We do not run our own game servers, so we do not keep a database of players.
  • The save file on your device is a plain file without encryption. It contains only game progress and settings (section 3). It is protected by the security of your device.
  • Partner SDKs normally send information over encrypted connections (HTTPS).
  • On iPhone and iPad: our games do not switch off Apple's App Transport Security, which requires apps to use encrypted connections.
  • On Android: our games do not block unencrypted (HTTP) connections. We cannot promise that every connection that a partner SDK makes is encrypted.
  • No method of sending or storing information is completely secure.

20. Links to other websites and apps

  • A PRIVACY button in a game opens a privacy policy in your web browser.
  • A SUPPORT button opens your e-mail app (section 16).
  • Ads can open other websites, Google Play or the App Store.
  • The rating window comes from Google Play or the App Store (section 7).
  • The privacy policies of those websites and apps apply there.

21. Changes to this policy

We update this policy when our games or our partners change, for example when a new game uses a new partner. The dates at the top show the current version. The new version applies from its effective date. If a change needs your consent by law, we will ask for it.

22. Contact

© 2026 MEDIOCRESOFT TECHNOLOGIES - FZCO

Comments

Post a Comment