Tekoworld
Privacy Policy
Last updated 14 November 2026
This explains what our games, Gemfire and Beat Bash, and this website collect about you, why, and what you can do about it.
Who we are
Gemfire and Beat Bash are published by Tekin Dabaj, trading as Tekoworld, of Famagusta, Cyprus, the same publisher named on both games’ store listings. For the purposes of the UK and EU General Data Protection Regulation, we are the data controller for the information described here. You can reach us at arcadetkn@gmail.com.
This policy covers Gemfire and Beat Bash on Android and iOS, and this website. The two games are separate apps with separate accounts and separate saves: nothing is shared between them. What each one collects is listed in its own table, Gemfire’s first and Beat Bash’s after it; everything else in this policy applies to both.
What Gemfire collects, and why
We have tried to make this specific rather than exhaustive-sounding. If something is not in this table, Gemfire does not collect it.
| What | Why | When |
|---|---|---|
| An anonymous account identifier, generated by Firebase Authentication | So your progress can be saved to our servers and restored on a new device. It is a random string. It is not linked to your name, email or phone number unless you choose to link a sign-in account. | First launch |
| Your game progress: which sieges you have finished and with how many stars, your best wave in the Endless Watch, your coins, gems, hearts and whispers, the turrets, kit and companions you own, the layout of your kingdom and the land it stands on, your daily streak, and your settings | So the game can continue where you left off, and so the same progress appears on your other devices. | As you play |
| A public kingdom card: the keeper name you chose, the companion you wear as your avatar, your keeper level, your kingdom’s score and star count, and your league | So other players can see you on the boards and visit your kingdom. This is the only information other players can see. You can switch it off from the Profile tab at any time, which takes your card down. | While the boards are enabled |
| Your chosen keeper name, held as a reservation so two players cannot claim the same one | To keep names unique. You choose this name; please do not use your real name if you would rather it were not public. | If you set a name |
| A linked sign-in: an identifier from Apple or Google, and whatever that provider passes to us, which may include your email address | Only if you choose to link an account so your progress survives losing your device. We do not receive your password. | Only if you link |
| Purchase records: the store transaction identifier and what was bought | To confirm a purchase with Apple or Google and to give you what you paid for, once. We never see your card details. The payment happens inside the store, not inside the game. | If you buy something |
| Advertising identifiers and related data, handled by our advertising partners | To show the adverts you choose to watch, and to pay for the game being free. See Advertising below. | When you watch an advert |
| Gameplay analytics: events such as a siege being started, won or lost, a turret bought, a chest opened or a purchase completed, with a device-level identifier | To see where players get stuck and which parts of the game are not working. Handled by Google Analytics for Firebase. See Analytics and attribution below. | As you play, subject to your consent where required |
| Install attribution: which advert or link, if any, led you to install the game, and confirmation of purchases you make | To know which of our advertising is worth paying for. Handled by AppsFlyer. | Once, after consent is resolved |
| A report you file about another player’s keeper name | So we can review the name and, where needed, replace it. The report records which account filed it, so that reports cannot be forged. | Only if you report a name |
| Basic technical information: device model, operating system version, language, and error diagnostics | To find out why something crashed or a screen drew wrongly on a device we do not own. | As needed |
What Beat Bash collects, and why
Beat Bash is built the same way. Its data is kept in its own Firebase project, separate from Gemfire’s, and stored in the European Union. If something is not in this table, Beat Bash does not collect it.
| What | Why | When |
|---|---|---|
| An anonymous account identifier, generated by Firebase Authentication | So your progress can be backed up from the first run and restored on a new device. It is a random string, not linked to you unless you link a sign-in. | The first time the game is online |
| Your game progress: your best score, grade, accuracy, combo and Flawless hits on each level, your gems (the purchases and rewards that added them, and the skins you unlocked with them), the skin you wear, any ad-free time you have, where to continue, and your settings | So the game can continue where you left off, and so progress from several devices can be merged without losing any of it. | As you play |
| Your runs: for each run of 16 taps or more, the level, the score the game showed, and the exact times of your taps; for your best run on each board, those taps are kept | Our server replays every run from its taps before it ranks it or counts it towards an achievement, so the boards only show scores that were really played. Runs played offline wait on your phone until it is online. | After each run, when online |
| A public player profile: your nickname (or a name generated from your account identifier if you have not chosen one), your scores and places on the boards, the badge and title you wear, the badges and titles you have earned, your best combo, number of Flawless hits, top tempo, number of runs, best league finish, weeks ranked, and your play time rounded to the hour | So other players can see you on the leaderboards and open your profile from them. This is the only information other players can see. If you would rather not appear on the boards, write to us and we will take you off them. | Once you have a run on a board |
| Your chosen nickname, held as a reservation so two players cannot claim the same one | To keep names unique and to filter names that are offensive or impersonate someone. You choose this name; please do not use your real name if you would rather it were not public. | If you set a nickname |
| Your achievements record: totals from your replayed runs (such as Flawless hits, best combo and play time), your best results on each level, this week’s quests, your league division, the badges and titles you have unlocked and when, and short fingerprints of your last runs | So our server can award badges, titles, quests and league rewards, and so the same run is never counted twice. It is kept on our server only. | As your runs are counted |
| A linked sign-in: an identifier from Google or Apple, and whatever that provider passes to us, which may include your name and email address | Only if you choose to sign in, so your progress follows you to another device. We do not receive your password. | Only if you sign in |
| Purchase records: the store order identifier and what was bought (a gem pack, the Starter Bundle or the No Ads subscription) | To give you what you paid for, once, on every device you play on, and to know whether a subscription is active. We never see your card details. | If you buy something |
| Advertising identifiers and related data, handled by Google AdMob | To show adverts between runs. See Advertising below. | When an advert is requested |
| Gameplay analytics: events such as a level being started and finished (with the score, grade, accuracy and how long it took), a level being downloaded, an advert being shown, a skin being worn, an achievement being unlocked or a reminder being opened, with a device-level identifier and your account identifier | To see which levels are too hard and what is not working. Handled by Google Analytics for Firebase, with its advertising features switched off. See Analytics below. | As you play, subject to your consent where required |
| Crash reports: device model, operating system version, the state of the app when it crashed, and your account identifier | To find and fix crashes. Handled by Firebase Crashlytics. | If the game crashes |
| An app integrity check: a token from Google Play Integrity (Android) or Apple DeviceCheck (iOS) that confirms a request comes from the genuine app on a real device | To keep scripts and modified apps off the leaderboards. Handled by Firebase App Check; it tells us nothing about you. | When the game talks to our server |
| A Firebase installation identifier, used to fetch the game’s settings | So we can tune things such as how often adverts are shown without releasing a new version of the app. Handled by Firebase Remote Config. | From time to time, when online |
Some things Beat Bash keeps on your phone only and never sends to us: how adverts have been paced for you, your reminder settings, whether the game has asked you for a store review, and your consent choices (stored by Google’s consent form). Reminders are scheduled by your phone itself: there is no push server and no notification token. Beat Bash does not use install attribution, does not ask iOS for permission to track you, and collects nothing listed under “what we deliberately do not collect” below.
What we deliberately do not collect
- Your name, unless you type one in as a Gemfire keeper name or a Beat Bash nickname, or a sign-in provider passes it to us.
- Your email address, unless you email us or link a sign-in account.
- Your contacts, photos, microphone, camera or precise location.
- Your payment card details. Those never reach us.
- Messages. There is no chat, and no way for players to contact each other.
Our legal bases (UK and EU)
- Performance of a contract: saving and restoring your progress, and honouring a purchase. Without these the game does not work.
- Consent: personalised advertising, gameplay analytics and install attribution where the law requires consent, and appearing on Gemfire’s public boards. All of these are optional and all can be withdrawn.
- Legitimate interests: keeping the games working, diagnosing crashes, measuring which levels are too hard, showing Beat Bash’s leaderboards and player profiles, reviewing and filtering names, verifying runs before they are ranked, and preventing fraud and abuse of the in-game economy.
- Legal obligation: keeping records of purchases for tax and accounting.
Advertising
Both games are free, and adverts are how they are paid for.
In Gemfire
Adverts are optional in the sense that matters: there are no adverts between levels and no banners. Every advert in Gemfire is one you choose to watch in exchange for hearts, coins or a whisper, and each kind has a daily limit.
Adverts are delivered by Unity LevelPlay (ironSource) as the mediation platform, and by the advertising networks it works with, which currently include Unity Ads and Google AdMob. These partners are independent controllers of the data they collect and have their own policies:
- Unity: player and app user privacy policy
- Google: how Google uses information from sites or apps that use our services
In Beat Bash
There are no adverts in your first six runs, never one during a run, and no banners. After that, a full-screen advert may play when you leave the results screen of a run that lasted at least 40 seconds: never more than one every 90 seconds, usually one every two or three runs, and fewer after a string of bad runs or once you have bought something. The No Ads subscription, and the ad-free days in the Starter Bundle, turn them off. How often adverts are shown is tuned remotely and kept on your phone; it is not sent to us.
Beat Bash’s adverts are served by Google AdMob alone, an independent controller of the data it collects (see Google’s policy above). On Android, AdMob may use the device’s advertising ID, which you can reset or delete in Android’s settings. Beat Bash does not ask iOS for permission to track, so on iOS the advertising identifier is not available to it.
Your choice, and how to change it
If you are in the European Economic Area or the United Kingdom, you are asked before any personalised advertising happens, in either game, through a Google-certified consent form. If you decline, you will still see adverts and still receive the rewards for watching them. They will simply not be based on a profile of you.
You can change your answer at any time. In Gemfire, open Settings (the gear icon on the Home or Profile screen) and choose Privacy & ad choices. In Beat Bash, open Settings and choose Ad privacy choices, which is shown wherever the law requires it. In Beat Bash, the same form also covers analytics (see below).
On iOS, Gemfire also asks separately whether the app may use the device advertising identifier. That answer belongs to the operating system and can be changed in iOS Settings › Privacy & Security › Tracking.
Analytics, crash reports and attribution
We use Google Analytics for Firebase to record gameplay events, such as a siege being started or a chest being opened in Gemfire, or a level being finished in Beat Bash, so that we can see where players struggle and what is not working. Where consent is required, these events are only recorded after you have given it. In Beat Bash, analytics is switched off until the game knows your choice: in the EU and the UK it starts only if you agree, in Google’s consent form, to information being stored on your device and used to measure content and for statistics; if you do not, nothing is sent. Analytics in Beat Bash never uses advertising storage or personalisation: those signals are switched off in the game, so the events are used for measurement only.
Beat Bash uses Firebase Crashlytics to receive a report when the game crashes, so we can fix it. Crash reports are not used for anything else.
Gemfire uses AppsFlyer to learn which advert or link, if any, led to an install, and to confirm purchases. AppsFlyer is started only after your consent choice is known, and where you have not agreed to personalisation it runs in an anonymised mode. Its policy is at appsflyer.com.
Who your data is shared with
We use a small number of providers, each for one job:
- Google Firebase (Authentication, Cloud Firestore, Cloud Functions, Analytics, Crashlytics, App Check, Remote Config): the anonymous accounts, the saved progress, both games’ boards, Beat Bash’s run checks and achievements, and crash reports. Saves are stored in the European Union, in a separate project for each game.
- Apple and Google: app distribution, sign-in if you choose it, payments and purchase verification.
- Unity LevelPlay and its advertising networks: advertising in Gemfire, as described above.
- Google AdMob: advertising in Beat Bash, as described above.
- Upstash: holds the ranking index of Beat Bash’s leaderboards (your account identifier, scores, nickname and the badge and title you wear) on servers in Frankfurt, Germany. The runs themselves are stored in Firebase.
- Cloudflare: delivers the levels and cube skins you download in Beat Bash. Like any server, it sees your IP address to send you the files; it does not receive your account or save data.
- AppsFlyer: install attribution in Gemfire, as described above.
We do not sell personal information, and we do not share it for cross-context behavioural advertising beyond what the advertising partners above do with your consent.
International transfers
Our save data is held in the European Union. Some of our providers are based in the United States and may process data there, relying on the European Commission’s standard contractual clauses, the EU-US Data Privacy Framework, or an equivalent safeguard.
How long we keep it
- Saved progress: for as long as the account is in use, and for up to 24 months after it goes quiet, after which it may be deleted.
- Your public kingdom card (Gemfire): until you hide it or delete your data, whichever comes first. Leaderboards are rebuilt nightly, so a hidden card leaves the boards within a day.
- Beat Bash’s leaderboards, profile and achievements: your best run on each board, your nickname and your achievements record are kept while your account exists. Weekly rankings are kept for four weeks after their week ends.
- Crash reports (Beat Bash): for 90 days.
- Purchase records: for as long as tax and accounting law requires, which is generally seven years, and for as long as needed to stop a receipt being redeemed twice. These survive deletion of your game data, because we are not permitted to destroy them.
- Reports you file about other players’ names (Gemfire): for as long as the reported account exists, so that the review can be shown to have happened.
Your rights
If the UK or EU GDPR applies to you, you have the right to ask for a copy of your data, to have it corrected, to have it deleted, to restrict or object to how we use it, and to withdraw consent you have given. Similar rights exist under the California Consumer Privacy Act and other laws.
The quickest routes are in the games themselves. In Gemfire, the boards opt-out is on the Profile tab, the advertising choice is in Settings, and account deletion is on the Profile tab. In Beat Bash, the advertising choice and Delete account are both in Settings, and your nickname is changed from the profile key on the main menu. For anything else, or to delete everything, see deleting your data or write to arcadetkn@gmail.com. We answer within 30 days.
Because accounts are anonymous by default, we may need you to prove which account is yours before we act on a request, usually by sending the request from a linked sign-in address, or by giving us the account identifier shown in Gemfire.
If you think we have handled your data badly, you can complain to your national data protection authority.
Children
Gemfire and Beat Bash are general-audience games. Neither is directed at children under 13, and neither is registered as a child-directed app with our advertising partners. We do not knowingly collect personal information from children under 13. If you believe a child has given us information, write to arcadetkn@gmail.com and we will delete it.
This website
This site is static. It sets no cookies, runs no analytics, and does not track you. The only thing it knows about you is what your browser tells our host in order to send you the page. If you choose a language, or close the offer of one, your browser remembers that for as long as the tab is open; it is kept on your device and never sent to us.
Changes
If we change this policy we will update the date at the top, and for anything significant we will say so in the games before the change takes effect.
This policy is also published in other languages. They are translations of this English text, and where one differs from it, this text applies.
Contact
Tekin Dabaj, trading as Tekoworld
Famagusta, Cyprus
arcadetkn@gmail.com