Privacy Policy
Effective date: 29 September 2026
1. Who we are
Miro Flight (called Miro Uçuşu in Turkish) is a game for iOS and Android published by Mire Bilişim A.Ş., İstanbul, Türkiye (“we”). We are the data controller for the data described on this page. Contact: games@trademire.ai.
- No account and no sign-in. We never ask for your email address or phone number.
- No advertising identifier and no tracking: the Android app has the advertising-ID permission removed, and the iOS app never asks to track you. Our own Player ID (2.1) is never given to Google or to any other outside service.
- No location, contacts, camera or microphone, and the app never reads your photos.
- No outside analytics or crash-reporting service: the only crash and error reports go to our own update server (2.6). The only outside services that receive data from the app are Google’s ad and consent tools (2.8), the App Store or Google Play for purchases (2.9), and, on Android, Google Play when the app asks it whether a newer version is available (2.6).
- Payments are handled entirely by Apple or Google. We never see your card.
- Other players can see only the picture you choose, the name you choose (shortened to its first and last letter), your scores, and the replay of a top flight.
2. What we process and why
2.1 Player ID
On first launch the app creates a random ID and keeps it on your device. It is not derived from your phone’s hardware or from any advertising identifier. The app sends it only to our own server, with the requests described below, so that the server can keep your records apart; it is never given to Google or to any other outside service, and no ad request carries it (2.8). Other players never see it: the leaderboard shows a public number derived from it (for example “#1234”).
2.2 Scores and replays
When a flight ends with a better score than your best on this device, the app first replays the flight on your device to check the score. Only a best that passes this check is sent: your Player ID, the score, the platform (iOS or Android), a fingerprint of the game version, and the replay of the flight, which includes the game mode and the number the flight’s course was generated from. A replay is the list of moments you tapped (and the revive, if you took one), not a video. The app never sends a replay larger than 300 KB (some ten thousand taps); a best with a longer replay stays on your device only. The same request carries the name you chose, if any, and our server ignores it there (names reach the leaderboard only as described in 2.3). If the app cannot reach our server, the best waits on your device and is sent later. We use this to show the monthly and all-time leaderboards and to check top scores against cheating by replaying the flight on our server. The replay of a flight in the top 100 of a leaderboard is kept so that other players can watch it; they see it with your public number, not your name. To show your rank and the players just above and below you, including at the start of a flight, the app reads the leaderboards with your Player ID. The app also sends a short signal with your Player ID, the platform and how long the app has been open, when a flight starts and when it ends; if you are offline, the signal waits on your device and is sent later. Our server currently discards it without storing it.
2.3 Optional name and picture
You can choose a leaderboard name (3 to 16 characters) and one of the game’s own 16 pictures, drawn for Miro Flight. Your picture is shown publicly on the leaderboards. Other players see your name only masked: its first and last character with at most four stars between them (for example, “Ahmet” appears as “A***t”); a name whose masked form would read as a swear word is shown to them as your public number instead. Only your own device shows it to you in full. Our server keeps the full name so that it can check it and act on reports. Names are checked by a filter on your device and again on our server. If you report another player’s name, we store the report together with your public number; a name reported by several players is marked and then removed. “Hide player” is stored on your device only. You can clear your name at any time in the Profile panel.
2.4 Invites
The app gives you an invite code linked to your Player ID, and our server notes when it created the code. A new player can enter a friend’s code during their first 60 finished flights, and then receives a welcome gift of 150 coins in the game. If you enter a friend’s code, we store the link between your two IDs, when you entered it, how many flights you had finished by then, and whether you have finished a flight since, so that your friend’s reward can be counted; when five friends have counted, we record your ad-free reward. To stop abuse of rewards we also store a salted one-way hash of your IP address, never the address itself.
2.5 Technical data on every request
Like any internet service, our servers receive your IP address, the time, the address requested (which can include your Player ID) and the app’s technical identification with every request. Our web server logs keep this for up to 14 days for security and troubleshooting. Request limits use your IP address in memory only.
2.6 Update checks and live updates
When the app starts, it reads a public file from our server to learn whether a newer version is available in the store, and may tell you so. On Android the app also asks Google Play, through the Play Store app on your phone, whether an update is available; that check is between your phone and Google. The app can also receive small updates to the game’s own content from our update server. For that it sends the app’s ID and version, the operating system version, the platform and a random identifier created by the update component, along with technical details such as that component’s version and whether the app was installed from the store. We use this only to deliver the update that fits your app version and to count, without identifying you, how many devices received it.
That random identifier is separate from your Player ID, and we do not link the two. The update component keeps it outside the game’s own storage, so deleting the app does not always delete it: on iPhone it is kept in the Keychain, which is not emptied when you delete the app, so the same identifier is used again if you reinstall it; on Android it is kept in the app’s storage, and Android’s backup can bring it back when you reinstall the app.
The update component also reports technical events to our update server, each with the details above, including its random identifier: the app starting and how long it took to be ready, update checks, downloads and installs, the app moving to the foreground or background, and failures – an update that did not start; the app closing unexpectedly (a crash, the app freezing, or the system closing it for lack of memory, with the reason and the memory figures the system gives); a low-memory warning; and an error in the game’s code, with its message, the place in the code where it happened, the steps that led to it (the stack trace), the browser identification of the app’s web view and a random number for that session of the app. Our server keeps only a daily count of each kind of event for each app version; it does not keep the device’s identifier or the error details, and it deletes the counts after 90 days. We use them to find and stop a faulty update and to see how well the app runs. These requests reach our servers like any other and fall under the server logs described in 2.5.
2.7 Ads for our own apps
Between flights, the app may show a full-screen card for another app made by us: only as you leave the card of a flight that has just ended, to fly again or to go to the menu; never before you have finished 8 flights; after that at most once every three finished flights and three minutes; at most four times each time the app is opened; and never within two minutes of a video ad you chose to watch. A flight counts as finished once it has ended on its own; a flight you leave before it ends, and a replay you watch, do not count. It never shows one when the app starts, during a flight, while the game is paused or offering you a revive, while you are offline, or if you have Remove Ads or ad-free play earned through invites. So that a card can appear without a wait, the app downloads the list of these ads, and the pictures and videos of a few of them, from our server ahead of time and keeps them on your device: when the app starts and after a flight, whenever you are online and have neither Remove Ads nor ad-free play earned through invites – also before a card may be shown to you, for example before your 8th finished flight. These downloads carry no Player ID or other identifier of yours. (At the first start after the app is reinstalled, the list may be read once before the store has confirmed that you own Remove Ads.) So that it does not advertise an app you already have, the app checks on your device whether that app is installed; the result stays on your device.
You can report any ad, ours or Google’s: tap the Ad tag on the card, or “Report an ad” in the Profile panel. That opens your own email app with a message to games@trademire.ai that names only the ad, the app, its version, your platform and the app’s language. Nothing is sent unless you send that email yourself.
2.8 Rewarded ads (Google AdMob)
The app contains the Google Mobile Ads SDK. A video ad plays only when you choose to watch one: to keep flying after a crash (at most once per flight), to double the coins a flight earned when it earned 10 or more (at most once per flight, on the card after it), or to wear one of the shop’s two ad outfits for a day. Every ad request is non-personalized and limited to content suitable for all ages (rated G); your advertising identifier is not used (the app asks for no tracking permission on iOS and carries no advertising-ID permission on Android). To deliver ads, measure them and prevent fraud, Google receives technical data such as your IP address, device and app information, an app-scoped identifier, ad interactions and diagnostic data. The app itself gives Google no identifier of ours: your Player ID (2.1), your name and your scores are never part of an ad request. Google processes this data under its own policies: How Google uses information from apps that use its services. The reward is granted on your device; we do not record which ads you watch.
Consent before the first ad. Before the app requests any ad, it asks Google’s consent tool (the User Messaging Platform) whether you must be asked for consent where you are; for that, the tool receives technical data such as your IP address and device and app information. Where the law requires consent – in particular in the EU, the EEA, the UK and Switzerland – the app then shows Google’s consent message over its main menu, never during a flight, and requests no ad until you have answered it. Your answer decides what Google may do on your device: if you consent, Google may store and read information on your device (for example to limit how often you see the same ad, and to measure ads) to show non-personalized ads; if you do not, Google shows only limited ads that use no identifier stored on your device, or none. If ads cannot be requested, the game works as usual and simply offers no ad to watch. Your answer is stored on your device by the consent tool and sent with each ad request. It never makes the ads personalized: every request stays non-personalized, whatever you answer. You can change or withdraw your answer at any time with Ad privacy options in the Profile panel or at the bottom of How to play; the entry is there wherever Google’s consent message applies. If you have Remove Ads, or ad-free play earned through invites, the app shows no Google ads and asks for no consent: the revive, the doubled coins and the outfits a video would unlock are yours without one.
2.9 Purchases
“Remove Ads” is sold through the App Store or Google Play, which process the payment. We receive no card or billing details. The app asks the store only whether you own the item and what it costs in your store’s country.
2.10 Kept on your device only
Your settings, language and sound choices, coins, goals and crowns, Miro’s outfits (and when an outfit worn for a video runs out), your best scores and the replay of your best flight, the players you hid, the names you reported (2.3), a copy of your invite code and its progress (2.4), whether you own Remove Ads and its price in your store (2.9), when the app last told you about an update (2.6), when you last saw one of our own ads and which one (2.7), the pictures and videos of our own ads (2.7), and the counter and the random number, made on your device, that your flights’ courses are drawn from (2.2) are stored only on your device. A best flight waiting to be checked or sent to the leaderboard (2.2) waits there too until it is sent. A flight you leave is not kept: it is there, paused, while the app stays open, and gone once the app is closed. All of this is deleted when you delete the app; a backup of your phone that includes the app (such as iCloud or Google backup) keeps its own copy, and Android may restore it when you reinstall.
2.11 Sharing and links
When you share your score, a flight video, a picture or an invite, it is made on your device and handed to your phone’s share sheet; you choose where it goes. On Android a video or picture is first copied into the app’s own temporary storage on your phone, where the share sheet reads it from; the next file you share replaces it, and Android may clear it sooner. If the share sheet cannot be opened, an invite is copied to your clipboard for you to paste yourself. If you choose to save it to your photos, your iPhone asks your permission to add it there; the app never reads your photo library. The privacy policy and links to our social media pages open in your browser or in their own apps.
3. Legal bases
For users in Türkiye (Law No. 6698 on the Protection of Personal Data, “KVKK”, article 5) and in the EU, EEA and UK (GDPR, article 6):
- providing the features you use, such as leaderboards, invites, purchases and updates: KVKK art. 5(2)(c), GDPR art. 6(1)(b);
- our legitimate interest in running a fair and secure game (checking scores, limiting abuse, server logs, update counts and error counts): KVKK art. 5(2)(f), GDPR art. 6(1)(f);
- your own choice to show a name and picture, which you can undo at any time;
- rewarded ads, which you choose to watch: where Google’s consent message asks for it, your consent, GDPR art. 6(1)(a), which you can withdraw at any time with Ad privacy options (see 2.8); in Türkiye, providing the reward you ask for when you choose to watch an ad, KVKK art. 5(2)(c).
4. Who receives data
- Other players: your chosen picture and your chosen name (masked, see 2.3), your scores, and the replay of a top flight.
- Our hosting provider: our servers are rented from Contabo GmbH and located in the European Union. As we are based in Türkiye, this means your data is transferred abroad. The servers run only our own services and are administered by us.
- Google for ads, as described in 2.8; Apple and Google for app distribution and purchases, and Google Play for the update check on Android (2.6).
These are the only parties outside our company that receive data from the app, and each receives only what the sections above name: Google, for the rewarded ads and the consent tool (Google AdMob and the User Messaging Platform, 2.8); Apple and Google, for app distribution, for purchases through the App Store and Google Play (2.9) and, on Android, for Google Play’s update check (2.6); and Contabo, which hosts our servers. Everything else – the leaderboard and its replays, names and pictures, invites, our update-check file and live updates with their crash and error reports, and the list and media of our own ads – is handled by our own services on those servers, and no one else runs them. We confirm that each of these third parties provides the same or equal protection of your data as this policy does: Google and Apple under their own published privacy policies and data protection terms, and Contabo as a processor that handles the data on our servers only to host them for us, on our instructions.
We do not sell your data, and we do not share it for personalized advertising.
5. How long we keep it
- Scores, name and picture, and invite records: while the game’s online service runs, or until you ask us to delete them.
- Replays: only for flights in the top 100 of a leaderboard; monthly replays are removed after the following month.
- Name reports: while the game’s online service runs, or until you ask us to delete them; the reports on a name we give back after review are deleted.
- Web server logs: up to 14 days.
- Update and error counts (2.6): daily counts with no identifier, up to 90 days.
6. Children
Miro Flight is a casual game for a general audience. It is not directed at children under 13, and we do not knowingly collect personal information from them. The game asks for no personal information: the leaderboard name is optional and filtered, and every ad request is non-personalized and limited to ads suitable for all ages. If you believe a child has entered personal information as a leaderboard name, write to us and we will delete it.
7. Your rights and deleting your data
Under KVKK article 11 and the GDPR you can ask whether we process your data and for a copy of it, have it corrected or deleted, object to its processing, and learn who received it. You can also complain to the Turkish Personal Data Protection Authority (KVKK) or to your local data protection authority.
Write to games@trademire.ai and include your invite code (shown in the game’s Invite panel) or your leaderboard name and number, so that we can find your records. We answer within 30 days. Because there is no account, deleting the app does not delete what is on our server: ask us, and we delete your scores, replays, name, picture, invite records and the reports you made. You can remove your name yourself at any time in the Profile panel.
What is not deleted on request: the web server logs, which expire on their own within 14 days (section 5), the update and error counts, which carry nothing that identifies you, and what Apple or Google keep about a purchase, which is theirs to delete. Deleting the app removes everything that is kept on your device only (2.10). The update component’s random identifier (2.6) is the exception: on iPhone it stays in the Keychain, and on Android a backup can bring it back. It is not linked to your Player ID, and our server does not store it.
8. Security
All connections between the app and our servers use HTTPS (TLS). Your Player ID is never shown to other players, and our leaderboard service records only your public number in its own logs.
9. Changes
If this policy changes, we will update this page and its effective date.