BumuStudios·Türkçe·العربية·Français·Delete your account
Privacy Policy — Tabula Domino
Online domino game for Android, package com.bumustudios.domino
Effective date: 17 October 2026. Last updated: 17 October 2026. Policy version 5.
No email address, no phone number, no real name. You play with a guest account and a display name you choose. Signing in with Google, Apple, Facebook or X is optional and only lets you get your account back on another device.
Tabula Domino is an online game, so your matches are played on our own servers, run by Hetzner in Germany (EU). This page lists everything those servers keep, why, and for how long. We do not sell your data.
Ads and Google services. The game shows ads from Google AdMob in the menus and, at most every third finished match, between matches; never during a match and never when the app opens. Ads are personalised only if you agree in Google's consent form. Crash reports (Google Firebase Crashlytics) and usage measurement (Google Analytics for Firebase) are sent only if you allow them. Players aged 13 to 17 get none of the optional parts.
Akçe. The game's currency is only earned (by playing, from the daily gift and from rewarded ads you choose to watch). It cannot be bought, cashed out or sent to another player. Our servers keep a record of every change to your balance.
From version 1.0.3: an optional Ad-free Pack you can buy once through Google Play (Google takes the payment; we never see your card), notifications only if you allow them, and an automatic check of new profile photos that runs on our own servers.
Who this policy is from
This policy covers the Android game Tabula Domino: Online Oyna (shown on your phone as
Tabula Domino), distributed through Google Play under the package name
com.bumustudios.domino. It is written by the game's developer, BumuStudios, an independent
developer, who is the data controller for the personal data described here under Turkey's
Personal Data Protection Law No. 6698 ("KVKK") and the EU General Data Protection Regulation ("GDPR").
Questions and data requests can be sent to the address in Contact, or through the
in-app form under Settings → Account → Support and appeals.
BumuStudios is not a company yet, so it has no trade registry number and no postal address is published; when a company is founded, this policy will be updated with its details. An EU and a UK representative (GDPR Art. 27) have not been appointed yet; one will be appointed before the game is distributed in the EU or the UK. Until then, we answer every request ourselves at the address in Contact.
What the game is
Tabula Domino is an online domino game. You are matched with other players by rating, or you open a private table with a code for friends. Matches, ratings and leaderboards are kept on our servers so that they are fair and so that a dropped connection does not lose your game. When no suitable opponent is found, you can play against computer opponents.
This version of the game
This policy describes the version of the game in Google Play's closed test. It contains:
- Ads (Google AdMob). A small banner in the menus (home screen, profile, settings) and an ad between matches, at most once every third finished match and at least 3 minutes apart. No ads during a match or when the app opens. See Ads.
- Crash reports and usage measurement (Google Firebase). Only with your permission, on Android. See In-app analytics and Crash reports.
- Akçe, the game's currency (from version 1.0.1). Earned only; tables you are matched to take an entry and pay the winners in Akçe; a daily gift; rewarded ads you may choose to watch. See Akçe and Ads.
- Update notices from Google Play (from version 1.0.2). In the lobby the game asks Google Play, on your phone, whether a newer version is ready; if you agree, Google Play downloads it and the game offers to restart. This happens between your phone and Google Play; nothing about it reaches our servers.
- The Ad-free Pack through Google Play (from version 1.0.3). A one-time purchase under Settings → Purchases: no ads in the menus or between matches, plus two table themes. Rewarded ads stay available if you choose to watch one. See Purchases.
- Notifications (from version 1.0.3), only if you allow them. For example when it is your turn while you are away from the game, or a friend invites you to a table. See Notifications.
- Automatic photo check (from 17 October 2026). A new profile photo is checked by a model that runs on our own servers before other players can see it. See Profile photo check.
Features the game does not have yet, such as sign-in on iPhone or other purchases, are not described here; this policy will be updated, with a new "last updated" date, before any of them arrives.
What we process
We collect only what the game needs. Every record on our servers is linked to you through a random player number, not through your name.
Account and profile
| Data | Why |
|---|---|
| Player number — a random number created with your account | To recognise you across matches |
| Display name — 2 to 20 characters that you type; it does not have to be your real name | To show you to other players |
Player tag — a random tag such as #K7M2Q9XA, and your choice of preset avatar |
So friends can find you; your profile's appearance |
| Profile photo (optional) — a photo you upload or take, or one you choose to copy from a Google, Facebook or X account you have linked. We keep two square copies that our server re-encodes; location, camera and date data (EXIF/GPS) and all other metadata are removed. We also keep where the photo came from and when you set it | To show you to other players. You can change or remove it at any time |
| Account type, status and times — guest or linked, active or not, when it was created and last used | To manage the account; to tell bots from people |
| Session records — only a hash of the session key stored on your device (never the key itself), plus each session's device label, platform, app version and times | To keep you signed in; so you can see where you are signed in and sign out |
| Linked sign-in (optional) — the account number Google, Apple, Facebook or X gives for you | To restore your account on another device |
| Name history — your previous display names and when you changed them | So that changing your name cannot be used to escape a report |
Country — a two-letter code (for example TR) estimated from your connection's IP
address when you create the account |
The flag on the leaderboard; regional content; knowing in which countries the game is played |
Your IP address is not stored with your account. It is read only at that moment to estimate your country and then let go. The estimate is made on our own server with DB-IP's "IP to Country Lite" database (IP Geolocation by DB-IP, licensed under CC BY 4.0); your address is not sent to anyone for it. The estimate can be wrong, for example over a VPN.
When you link Google, Apple, Facebook or X, we verify the sign-in with that provider and keep only the account number it gives for you. We do not read or store your email address, and we send no game data to the provider. A profile photo is copied from that account only if you choose it, and only once: if it later changes there, our copy does not.
Profile photo check
Every new profile photo is checked automatically by an image model that runs on our own servers. It looks only for nudity and sexual content; it does not recognise faces, and the photo is not sent to anyone for the check. Then:
- a photo that is clearly not allowed is refused and not stored; your previous photo stays;
- if the result is not clear, the photo is shown only to you until someone on our team has looked at it and approved or refused it;
- otherwise it is shown to other players.
We keep the model's score and result (approved, held for review, refused), the model's name, and our team's decision and its time. A stricter threshold applies if you are 13 to 17 or have not told us your age. Violence and other problems are handled through player reports and our team. If an image is suspected to be child sexual abuse material, we report it to the competent authorities as the law requires and keep it as evidence, shown to nobody, for as long as the law requires (at least 1 year), even if the account is deleted.
Matches, ratings and leaderboards
| Data | Why |
|---|---|
| Match records — game, mode, rules version, start and end, result and score; your seat and team and a copy of your display name at the time | The game itself; your match history and your opponents' |
| Match state and move log — the tiles on the table, your hand, every move | The server runs the game; to restore a match after a dropped connection; to look into disputes and cheating |
| Private table codes and rematch offers | To join a friend's table; the rematch feature |
| Statistics and rating — matches played, won and lost, streaks, your rating and its history, your place on leaderboards | Your progress; finding an even opponent; leaderboards |
| Matchmaking records — when and in which queue you searched, your rating then, whom you were matched with, how it ended | To match you; to avoid the same pairing again and again; to measure waiting times |
| Fair-play counters — searches cancelled in a short time, matches you were placed in but did not join | To keep matchmaking fair for everyone |
Your tiles stay on the server; your opponents never see your hand.
Akçe (the game's currency)
Akçe can only be earned: you start with a balance, matched tables take an entry and pay the winners, and there is a daily gift and rewarded ads. Private tables, rematches and tables with computer opponents take no entry. Akçe cannot be bought, exchanged for money, cashed out or transferred to another player.
| Data | Why |
|---|---|
| Akçe record — every change to your balance: when, how much, and why (table entry, payout, refund, daily gift, rewarded ad), with the match it belongs to; your current balance | Keeping your balance right; settling tables fairly; preventing cheating and abuse |
| Rewarded ad records — the random one-time reward number created before the ad, what it was for (a refill, or half your entry back after a lost match), whether it was granted, and the transaction number and ad unit that Google's confirmation carries | Giving the reward only once and only for an ad that was really watched |
Friends, quick messages and reports
| Data | Why |
|---|---|
| Friends list, friend requests, invites to a private table, players you blocked | The in-game friends feature. This is a list inside the game: the game never reads your phone's contacts |
| Recent players — whom you played recently | The "Recent players" list; friend requests and reports are possible only for people you met |
| Quick messages — which preset phrase or emoji you sent, and when | Rate limiting; evidence if someone reports abuse. There is no free-text chat: only preset messages can be sent |
| Reports — the category (leaving matches, abusive quick messages, suspected cheating, an inappropriate profile photo), the match, and that match's quick messages as evidence | Moderation |
| Online visibility setting | Whether your friends can see that you are online. Being online is kept only in memory and never written down |
A player you report or block is not told, and you are not told who reported or blocked you.
Support requests, appeals and moderation
When you use the in-app form (Settings → Account → Support and appeals) we keep the topic, the words you write (up to 2,000 characters), the match or decision it concerns, the app's platform and version, and our reply. Please do not write passwords or other personal details in it. When our team acts on an account — a suspension, a ban, removing a matchmaking wait, hiding a photo — we keep a record of the decision, its reason and which team member made it.
Notifications — only if you allow them
From version 1.0.3 the game can send notifications while you are away from it: when an opponent is found, your table is ready, it is your turn, your table wants a rematch, or a friend invites you to their table; players aged 18 or over may also get announcements about the game. On Android 13 and later the game asks first, and you can say no; on older Android versions notifications are on unless you turn them off in Android's settings. A notification carries nobody's name: an invitation says "A friend is inviting you to their table", and you see who when you open the game. Turn, invitation and announcement notifications do not come during the quiet hours you can set, and you can switch each kind off under Settings → Notifications.
When notifications are allowed, we keep a device record: the notification address (push token) that Google Firebase Cloud Messaging gives your phone, a random number for the installation, platform, app version, the phone's language and time zone. We also keep which kinds of notification you want, your quiet hours, and which notification was sent when. The notification address is created only after you allow notifications.
Purchases
From version 1.0.3 you can buy the Ad-free Pack once, under Settings → Purchases. Google Play takes the payment under its own terms; we never receive your card or bank details. Our server checks the purchase with Google Play and keeps a purchase record: a fingerprint (hash) of Google Play's purchase token (not the token itself), the product, the time, any refund, and that the pack is yours. The game gives Google Play a random account code with the purchase so that it can be restored on a new phone; it is not your player number and tells Google nothing else about you. Akçe can never be bought. Players aged 13 to 17 see an extra explanation before buying.
In-app analytics — only with your consent
The game can send usage events, such as "progress screen opened", with the app version, platform and a session number that changes on every launch, only if you allow it. The question appears in the app, and you can change your answer at any time under Settings → Privacy → Help us improve the game. These events go to our own servers. Your name, IP address, advertising ID, anything you type and the tiles in your hand never enter an analytics event. We keep your answer, the text version it was given for and its time, to respect and prove it.
On Android, with the same permission, Google Analytics for Firebase (Google LLC, acting on our behalf as data processor) also measures how the app is used: automatic events such as the app opening, session and engagement time, device model, operating system and app version, a random number for the installation, and a coarse location (country, city) derived from the IP address. No advertising ID is collected and none of this is used for ads. If you do not allow it, or withdraw it, nothing is sent to Firebase. Nothing is sent for players aged 13 to 17.
Separately, our servers count things that already happen on them, such as "match found" and "match finished", to measure how the service runs (number of matches, waiting times). If you decline analytics, or delete your account, these records are kept without your player number.
Crash reports — only with your permission
If you turn on Settings → Privacy → Crash reports (it starts off), a technical report is sent to Google Firebase Crashlytics (Google LLC, data processor) when the app crashes, so we can find the problem: the error trace, device model, operating system and app version, and a random number for the installation. The report does not include your name, your player number, anything you wrote or the tiles in your hand. Turning it off deletes reports that have not been sent yet. For now crash reports are sent on Android only, and never for players aged 13 to 17.
Ads
Ads are served by Google AdMob (Google LLC and Google Ireland Limited): a small banner in the menus (home screen, profile, settings), an ad between matches (at most once every third finished match, at least 3 minutes apart) and, where the app offers one, a rewarded ad that you watch only if you choose to. No ads are shown during a match or when the app opens.
AdMob processes your device's advertising ID, IP address, device information and ad interactions to show ads, limit how often you see them, measure them and prevent fraud. Your advertising ID is used for personalised ads only if you agree in Google's consent form (Google User Messaging Platform), which the game shows after your first finished match where the law requires a choice (for example in the EU, the UK and some US states). You can open it again at any time under Settings → Privacy → Ad choices and give or withdraw your consent. If you do not agree, you still see ads, but they are not personalised. In countries where no choice is asked (Türkiye included), ads are for now always non-personalised. Players aged 13 to 17 only get non-personalised ads, and the ad network is told that the player is a minor. Your advertising ID never reaches our servers or our analytics.
Rewarded ads. You may choose to watch one to refill your Akçe when it no longer covers the smallest table, or, after a lost match, to get half of your entry back. Before the ad, our server creates a random one-time reward number, and the app gives it to AdMob with the ad. When the ad has been watched, Google's server sends our server a message signed by Google with that number, and only then is the Akçe added. The reward number is not your player number and tells Google nothing about you.
Google's own use of the data is described in How Google uses information from sites or apps that use its services.
Technical records
- IP address. Our application servers use it only in memory: to answer the request and, for at most an hour, as the key of a rate-limit counter that protects the service from abuse. It is never written to our database or linked to your account.
- Edge logs. The network layer in front of our servers keeps access logs with the IP address and the app's identification string (user-agent) for 7 days, for security and to investigate faults, and then deletes them.
- Monitoring logs. Our servers' error and monitoring logs may contain a player number, never names or session keys, and are kept for 14 days.
- App version. Sent with every request so that the server can tell an outdated app to update.
- Backups. Our database backups are kept for at most 16 days.
What stays on your phone
Your session key (in Android's secure storage), your sound, vibration and theme settings, the tips you have already seen, the target score you last chose, your answer to the age screen, and the choices you made in Google's ad consent form (kept on the phone by Google's consent library). The game reads your phone's language to show the interface in it. It asks for the camera or your photos only if you choose to set a profile photo, asks to show notifications (from version 1.0.3, on Android 13 and later), and requests no location, contacts or microphone permission. From version 1.0.2 none of this is copied to Android's cloud backup or to a new phone: the game switches Android's backup off, so uninstalling the game removes it all.
What we do not collect
Email address, phone number, real name, postal address, precise (GPS) location, your phone's contacts, your photos and files (other than a profile photo you choose), voice recordings, payment details, browsing history. We do not collect your advertising ID on our servers. We do not process special categories of personal data, such as health data.
What other players see
- At the table: your display name, profile photo or avatar, country flag, your moves (never your hand), the quick messages you send, and the result.
- Everyone: your display name, profile photo or avatar, country and rank on leaderboards and in friends lists. A profile photo is visible to other players once the automatic check has passed it (see Profile photo check); you can remove it at any time in your profile. Other players can report a photo they find inappropriate, and our team can hide or delete it.
- Your friends: whether you are online or in a match, unless you turn this off.
- Players you met recently, and anyone who knows your player tag: can send you a friend request.
Bots
When no suitable opponent is found, or in practice, you may play against computer opponents (bots). Bots are always labelled BOT next to their name and on the end-of-match screen; there are no hidden bots. Bot profiles are invented and do not belong to real people.
Purposes and legal bases
| Purpose | KVKK | GDPR |
|---|---|---|
| Creating and running your account, matches, matchmaking, ratings, leaderboards, profile photo, friends, invites and quick messages; answering support requests | Art. 5(2)(c) — performance of a contract | Art. 6(1)(b) — contract |
| Your Akçe balance and its record, table entries and payouts, the daily gift, rewards for ads you chose to watch | Art. 5(2)(c) — performance of a contract | Art. 6(1)(b) — contract |
| Notifications about your matches and friends' invitations | Art. 5(2)(c) — performance of a contract | Art. 6(1)(b) — contract |
| Announcement notifications (18 and over; you can turn them off) | Art. 5(2)(f) — legitimate interest | Art. 6(1)(f) — legitimate interest |
| Selling and delivering the Ad-free Pack, refunds; keeping purchase records | Art. 5(2)(c); for keeping records Art. 5(2)(ç) — legal obligation | Art. 6(1)(b); for keeping records Art. 6(1)(c) — legal obligation |
| Automatic profile photo check; reporting suspected child sexual abuse material and keeping it as evidence | Art. 5(2)(f); for illegal content Art. 5(2)(ç) | Art. 6(1)(f); for illegal content Art. 6(1)(c) |
| Fair play, preventing cheating and abuse, security, edge and monitoring logs, name history, reports and moderation, records of team decisions | Art. 5(2)(f) — legitimate interest | Art. 6(1)(f) — legitimate interest |
| Estimating your country from your IP address | Art. 5(2)(f) — legitimate interest | Art. 6(1)(f) — legitimate interest |
| In-app analytics, including Google Analytics for Firebase | Art. 5(1) — explicit consent | Art. 6(1)(a) — consent |
| Crash reports (Firebase Crashlytics) | Art. 5(1) — explicit consent | Art. 6(1)(a) — consent |
| Non-personalised ads, limiting how often they are shown, ad fraud prevention | Art. 5(2)(f) — legitimate interest | Art. 6(1)(f) — legitimate interest |
| Personalised ads | Art. 5(1) — explicit consent | Art. 6(1)(a) — consent |
| Server-side operating counts | Art. 5(2)(f) — legitimate interest | Art. 6(1)(f) — legitimate interest |
| Records kept after an account is deleted (see How long we keep data) | Art. 5(2)(f); for decisions and disputes also Art. 5(2)(e) | Art. 6(1)(f); Art. 17(3)(e) |
| Legal claims and requests from authorities | Art. 5(2)(ç) and (e) | Art. 6(1)(c) and (f) |
Our legitimate interests are keeping matches fair and the service secure, protecting players from harassment and cheating, understanding in aggregate how well the service runs, funding a free game with ads, and keeping the other players' match records intact. You can object to this processing (see Your rights).
Who receives data, and where it is stored
We do not sell your personal data for money.
| Recipient | What | Where |
|---|---|---|
| Hetzner Online GmbH — hosting and storage, acting on our behalf as data processor | All data on our servers, including profile photos | Germany (EU) |
| Google, Apple, Meta (Facebook), X — only if you sign in with them | We send no game data. We check the sign-in token they issue; for Facebook and X we ask them to confirm it. If you choose to use the photo of that account, we download it from them once | Depends on the provider |
| Google AdMob and Google's ad partners — independent controllers | Advertising ID, IP address, device information, ad interactions; your consent choices; for a rewarded ad, the random one-time reward number | USA and other countries |
| Google Play — the store you installed the game from, an independent controller | When the game checks for an update (from version 1.0.2), Google Play on your phone answers it under Google's own terms; we receive nothing from that check | USA and other countries |
| Google Play Billing — the payment for the Ad-free Pack, taken by Google as an independent controller (from version 1.0.3) | Google takes your payment under its own terms. Our server asks Google Play to confirm a purchase and to tell us about refunds; the game gives Google a random account code, not your player number | USA and other countries |
| Google Firebase Cloud Messaging — data processor, only if you allow notifications (from version 1.0.3) | The notification address and the installation ID Google gives your phone for it, the notification text and type | USA and other countries |
| Google Firebase Crashlytics — data processor, only with your permission (Android) | Crash reports | USA |
| Google Analytics for Firebase — data processor, only with your permission (Android) | App usage events, device information, installation number, coarse location from the IP address | USA |
| Competent authorities and courts | What the law requires | Turkey or the relevant country |
Transfer abroad (KVKK). Our servers are in Germany, so data of players in Turkey is transferred abroad. This transfer is made under Article 9 of the KVKK on the basis of a standard contract with our hosting provider, notified to the Turkish Personal Data Protection Board as the law requires, and the same applies to the Google services above. For players in the EU, data on our servers stays in the EU; transfers to Google in the USA rely on the EU–US Data Privacy Framework and/or the European Commission's standard contractual clauses. You can ask for a copy of these safeguards at the address in Contact.
How long we keep data
Retention periods are applied automatically. When a period ends, data is deleted, anonymised (every player number and anything that could single you out is removed), or kept without your name: your name and linked accounts are removed and the record stays only under a random player number. A record kept without your name in this way is still personal data.
| Data | Kept | Then |
|---|---|---|
| Account and profile | While your account exists | Deleted when the account is deleted (see Deleting your account) |
| Guest account not used for a long time | 24 months after last use | Deleted as if you had deleted it |
| Profile photo | Until you remove or change it, our team deletes it, or the account is deleted | Deleted within minutes; gone from backups when they expire |
| Photo check results and team decisions about a photo | As long as the photo, or the account, exists | Deleted |
| An image reported to the authorities as suspected child sexual abuse material | As evidence, shown to nobody, for as long as the law requires (at least 1 year), even after the account is deleted | Deleted |
| Device record and notification address | Until it stops working, 60 days without renewal, you sign out, or you withdraw the permission | Deleted at once |
| Notification records (which notification was sent when) | 30 days | Deleted |
| Purchase records | As long as the law on financial records requires, at most 10 years | After account deletion, kept without your name; deleted at the end of the period |
| Ended session records | Up to 30 days after they end | Deleted |
| Name history | Up to 180 days | Deleted |
| Match results, statistics, rating | While your account exists | After account deletion, kept without your name |
| Match move log | Up to 2 years | Kept without your name |
| Akçe record and rewarded ad records | While your account exists, then as long as the law on financial records requires, at most 10 years | After account deletion, kept without your name; deleted at the end of the period |
| Matchmaking records | 90 days | Deleted |
| Fair-play counters | 30 days after the last wait ends | Deleted |
| Friends, blocks, visibility setting | While your account exists | Deleted with the account |
| Friend requests | 30 days after the answer or expiry | Deleted |
| Invites | 7 days after expiry | Deleted |
| Recent players, quick-message records | 30 days | Deleted, except copies attached to a report as evidence |
| Reports | 1 year | Player numbers and evidence removed; category, outcome and match number remain |
| Support requests and replies | 365 days after an answered or closed request last changed | Deleted; deleted at once if you delete your account |
| Records of team decisions (suspensions, bans, support actions) | Up to 5 years | Deleted |
| In-app analytics events | 13 months | Deleted |
| Your analytics answer | While your account exists | Deleted with the account |
| Google Analytics for Firebase events | Up to 14 months | Deleted by Google |
| Crash reports (Crashlytics) | 90 days | Deleted by Google |
| Edge logs (IP address, user-agent) | 7 days | Deleted |
| Monitoring logs | 14 days | Deleted |
| Database backups | Up to 16 days | Deleted data disappears from backups when they expire |
| List of deleted accounts — the random number, account type, creation, last use and deletion times, with a fixed placeholder instead of the name | Indefinitely | Kept so that delayed system messages cannot recreate a deleted account, and so that match histories kept without names stay consistent |
Deleting your account
You can delete your account from inside the app: Settings → Account → Delete account. Your account is frozen at once and deleted after 14 days; during those 14 days you can open the app and tap Cancel the deletion, and everything comes back as it was. You can also ask for deletion by email without the app. Step-by-step instructions, and the full list of what is deleted and what is kept, are on the account deletion page.
- Deleted: your display name (also the copies in match records), player tag, avatar choice, profile photo, linked sign-ins, sessions, name history, friends, requests, blocks, invites, quick-message records, matchmaking records, support requests, your analytics answer, your device records and notification settings. Your Akçe balance is closed and cannot be restored.
- Kept without your name, under a random number only: match records and move logs (they are also the other players' records), statistics and rating totals, your Akçe record, purchase records, and records of team decisions, for the periods above. An image kept as evidence for the authorities (see Profile photo check) is kept for the period the law requires.
- Player number removed as well: analytics events and server-side counts.
- A report made about you stays until its period ends, with your player number replaced by a new number that cannot be traced back.
- Deletion reaches our backups when they expire, within 16 days.
- Crash reports and Firebase usage events are not linked to your player number; they expire at Google after 90 days and 14 months. Ad data is held by Google under its own policy.
Children and protected mode
The game is not directed at children. You must be at least 13 to play. Players aged 13 to 17 play in a protected mode: only non-personalised ads, with the ad network told that the player is a minor; no ad, analytics or crash-report consent prompt, so no in-app analytics, Firebase data or crash reports are sent; no announcement notifications; a stricter profile photo check; and an extra explanation before a purchase. We use the age information you give in the app only to apply these rules. If we learn that a player under 13 has an account, we delete it. If you believe a child under 13 is using the game, write to the address below.
Security
- All traffic between the app and our servers is encrypted (TLS).
- There are no passwords. Your session key is kept in your phone's secure storage; our server keeps only its hash, and session keys are never written to logs.
- Your display name and linked sign-ins are kept in one part of the database; the other parts know only your player number.
- Your hand and other hidden information stay on the server; your phone receives only what you are allowed to see.
No system is perfectly secure. If a data breach affects you, we will notify the authorities and you as the law requires.
Automated decisions
- Matchmaking picks your opponent automatically, based on rating.
- If you cancel many searches in a short time, or do not join matches you were placed in, matchmaking may make you wait a short time before searching again. This is not a sanction; you can still play private tables, and our team can lift it.
- Profile photo check: a new photo may be refused automatically, or shown only to you until someone on our team has looked at it. You can challenge this in the app under Settings → Account → Support and appeals, and a person reviews it.
- Reports never trigger an automatic sanction. Every suspension or ban is decided by a person on our team, and you can appeal it in the app.
Your rights
Your right to object. You can object at any time, on grounds relating to your situation, to processing based on our legitimate interest. We then stop, unless there are compelling legitimate grounds that override your interests or the data is needed for legal claims.
Under Article 11 of the KVKK you have the right to learn whether your personal data is processed and to request information about it; to learn the purpose of processing and whether it is used for that purpose; to know the third parties in Turkey or abroad to whom it is transferred; to ask for incomplete or inaccurate data to be corrected; to ask for it to be deleted or destroyed under Article 7; to ask that correction or deletion be notified to those third parties; to object to a result against you that arises solely from automated analysis; and to claim compensation for damage caused by unlawful processing.
Under the GDPR, players in the EU have the rights of access, rectification, erasure, restriction, data portability and objection, the right to withdraw consent at any time without affecting earlier processing, and the right to lodge a complaint with the data protection authority of the country where they live.
How to use them:
- In the app: change your display name and photo; delete your account; turn analytics and crash reports on or off; give or withdraw ad consent under Settings → Privacy → Ad choices; download a copy of your data under Settings → Account → Account and profile → Privacy and data where the app offers it.
- By email to the address below, from any address. Include your player tag, shown under Settings → Account → Account and profile. A guest account has no email address attached, so before acting we check that the account is yours, for example by asking you to send a short code through the in-app support form, or to sign in with the account you linked. We never ask for a password.
- We answer free of charge within 30 days at the latest.
- If your request is rejected, the answer is not enough, or we do not answer in time, you can complain to the Turkish Personal Data Protection Board (Kişisel Verileri Koruma Kurulu), or, in the EU, to your national data protection authority.
US states (California and states with similar laws): you have the right to know, delete and correct, and to opt out of the "sale or sharing" of personal information. We do not sell your data for money, but personalised advertising counts as "sharing" under some state laws; you can stop it under Settings → Privacy → Ad choices. Brazil: you have the rights in Article 18 of the LGPD and can complain to the ANPD.
Changes to this policy
Each version of this policy has a number and an effective date. When the game's data practices change, for example when purchases or notifications are added, this page is updated first and the "last updated" date at the top changes. Material changes are also announced in the game. If the analytics, crash-report or ad questions change materially, the game asks you again. Version 2 (17 October 2026) added Google AdMob ads, Google's consent form, Firebase Crashlytics and Google Analytics for Firebase. Version 3 (17 October 2026) added Akçe, the game's earned-only currency, and rewarded ads confirmed by Google's server, and states that no company, postal address or EU/UK representative exists yet. Version 4 (17 October 2026) adds the update notices from Google Play and says that the game keeps nothing in Android's cloud backup (both from version 1.0.2); what is collected did not change. Version 5 (17 October 2026) adds, from version 1.0.3, the Ad-free Pack bought through Google Play and notifications that you allow, and the automatic check of new profile photos on our own servers, with evidence kept for the authorities when the law requires it.
Contact
For any question about this policy, or to make a data request:
BumuStudios, data controller for Tabula Domino. In the app, you can also write to us under Settings → Account → Support and appeals.