TABULAPrivacy Policy
Current versionVersion 3.0.1In effect since
Also in: Türkçe Español Português (Brasil) Français العربية
Contents
Effective date: 26 October 2026 · Version 3.0.1
This policy explains which personal data we process when you play Tabula Domino, why, who we share it with, how long we keep it and how you can use your rights. It is written for players everywhere. Players in Türkiye can also read the Turkish KVKK notice (KVKK Aydınlatma Metni).
1. In short
- To play, we do not ask for your email address, phone number or real name. You choose a display name.
- If you sign in with Google, we may put the name and profile photo of your Google account on your profile once: the name only if you still have the name given automatically, the photo only if you have no photo yet (section 3.1). You can change both later in Profile. We still do not take your email address.
- We process the data needed to run the game: your matches, moves, results and rating.
- We do not sell your personal data.
- In-app analytics and personalised ads run only if you allow them. You can withdraw your permission at any time. If you say no, the game works just the same.
- Crash reports (Android only, for now) are on by default; you can turn them off at any time with the Settings → Privacy → "Crash reports" switch.
- If you are 13 to 17, the game runs in protected mode: no personalised ads, no analytics, no crash reports and no announcement notifications; the name and photo of your Google account are not taken.
- Our servers are in the European Union, in Germany.
- You can delete your account from inside the app. If you change your mind within 14 days, the deletion is cancelled.
2. Controller and contact
| Controller | BumuStudios, an independent developer. No company has been founded yet; when one is, this policy will be updated with its details |
|---|---|
| Registration | None yet: BumuStudios is not a company, so it has no MERSIS number, trade registry entry or KEP address. No postal address is published yet |
| Privacy and data requests | privacy@tabulastudios.com · in the app: Settings → Support and appeals |
| Our EU representative (GDPR Art. 27) | Not appointed yet. One will be appointed before the game is distributed in the EU; until then, send requests to privacy@tabulastudios.com |
| Our UK representative (UK GDPR Art. 27) | Not appointed yet. One will be appointed before the game is distributed in the UK; until then, send requests to privacy@tabulastudios.com |
Once a representative has been appointed, players in the EU or the UK will also be able to write to them, and they will pass the request on to us. Until then, we answer every request ourselves.
3. What data we process
The tables below say what the data is and why we need it. Legal bases are in section 5 and retention periods in section 9.
Your display name, age information and game data are needed for the Service itself; you cannot play without them. Analytics and personalised ads are optional: they run only if you allow them. Crash reports are on by default; you can turn them off at any time (section 3.10).
3.1 Account and profile
| Data | Description | Why |
|---|---|---|
| Player number | A random number created with your account | To recognise you. Other records are linked only by this number |
| Display name and name history | The 2-to-20-character name you choose (or the name taken from your Google account, see below); your earlier names and when you changed them | To show you to other players; to stop people escaping reports by renaming |
| Birth year and age group | The birth year you choose on first launch (we do not ask for day or month); the age group it gives (13–17 or 18+); any age-range signal your app store provides | To apply the age limit; to turn on protected mode for ages 13 to 17 (section 6) |
| Player tag and avatar | A random tag such as #K7M2Q9XA; the ready-made avatar you pick | So friends can find you; your profile |
| Profile photo (optional) | A photo you upload, the photo of a linked account that you choose to use, or the photo taken once from your Google account (see below). We keep two small copies on our servers and remove all metadata, including location and camera details. We also keep where the photo came from and when it was set | To show you to other players |
| Linked account ID | The account number Apple, Google, Facebook or X gives you. We do not take your email address | To bring your account back on another device |
| Name and photo of your linked account (Google today) | When you sign in with Google or link your account to Google, the name (your Google account's display name) and the profile-photo address in Google's verified sign-in token | To show you to other players with the name and photo of the account you chose to link |
| Sessions | Only a hash of your session key; device type, platform, app version, times | To keep you signed in without registering again; so you can see and close your sessions |
| Country (approximate location) | The country estimated from your connection address (IP), as a two-letter code. The estimate is made on our own server with a data file; your IP address is not stored for this and is not sent to anyone | To show your country on the leaderboard; to apply country-specific legal rules (for example ad consent and countries where we do not offer the Service) |
| Account status and times | Guest or linked; when created and last used; any deletion request | To manage the account; to find accounts unused for a long time |
Name and photo taken from Google. The first time your account meets Google (sign-in, registration or linking), we do this once only:
- The first name on your Google account (for example "Mustafa"; never your surname) becomes your display name only if you still have the name given automatically (such as "Player #K7M2", never changed). A name you chose yourself is never replaced. The name goes through the same rules as any name (2 to 20 characters, blocked words); if it does not pass, your account keeps its name.
- Your Google account's photo becomes your profile photo only if your account has no profile photo yet. Our server downloads the photo from Google once, re-encodes it (two small copies, all metadata removed) and runs the same automated check as for any uploaded photo; other players see it only once it is approved.
- You can change your name in Profile, and remove or replace your photo; we do not take them from Google again.
- If you are 13 to 17 (protected mode), the name and photo of your Google account are not taken: your name stays the one given automatically, and your profile shows an avatar.
- We never read your email address. Apple's sign-in token carries no name; Facebook and X sign-in are turned off.
Other players see this name and photo like any display name and photo (section 7). The name is kept in your name history like any other name; both are deleted with your account like any name and photo.
The country estimate uses DB-IP's "IP to Country Lite" database (db-ip.com) under the Creative Commons Attribution 4.0 licence. The estimate may be wrong (for example when you use a VPN).
3.2 The game
| Data | Description | Why |
|---|---|---|
| Match records | Game type, rules version, players at the table, start and end time, result and score; a copy of your display name at the time of the match | The game itself; match history |
| Match state and move log | Tiles on the table, your hand, every move | To run the game; to restore a match after a dropped connection; to look into suspected cheating and appeals |
| Private room code and rematch | The join code you share; rematch requests | Playing with friends |
| Statistics, rating, season | Matches played, won and lost; your rating and its history; your season rank | Your progress; finding fair opponents; the leaderboard |
The tiles in your hand are kept only on the server; your opponents never see your hand.
3.3 Matchmaking and fair play
| Data | Description | Why |
|---|---|---|
| Matchmaking records | When and for which table type you searched, your rating at the time, who you were matched with | Matching you with opponents; measuring waiting times |
| Abuse counters | How often you cancelled searches in a short time or did not show up after a match was found; any short wait that followed | Keeping matchmaking fair for everyone |
| Sanction records | Type and length of a suspension, reason code; the note of the staff member who decided | Enforcing the rules; reviewing appeals |
| Staff action records | Actions staff took on your account: who, when, what, why | Auditing staff actions |
3.4 Social features
| Data | Description | Why |
|---|---|---|
| Friends, requests, invites, blocks | Your friends list, requests and invites you sent and received, players you blocked | Friendship and invites; not being matched with someone who bothers you. The blocked player is not told |
| Recent opponents | Who you played recently | The "Recent players" list; reporting |
| Quick messages | Which preset phrase or emoji you sent and when. Free text cannot be typed | Rate limits; evidence in reports |
| Online visibility | Your setting for whether friends can see you online. Whether you are online is not recorded | Your choice |
3.5 Support, reports and moderation
| Data | Description | Why |
|---|---|---|
| Support and appeal requests | Topic, the text you write, the number of a related match, purchase or sanction, app version; our staff's reply | Answering your request; reviewing your appeal |
| Reports | Type of report, the match, the quick messages in that match or the reported photo or name as evidence | Moderation; protecting other players |
| Photo moderation | The score and result (approved, held for review, refused) our own servers' automated model gives a new photo, the model's name, and our team's review decision and its time. The model does not recognise faces, and photos are not sent outside. A stricter threshold applies if you are 13 to 17 or have not told us your age yet | Stopping inappropriate photos being shown to everyone |
Please do not put passwords, card numbers or other personal details in the support form.
3.6 Notifications
| Data | Description | Why |
|---|---|---|
| Device record | Notification address (push token), a random number for the installation, platform, app version, device language, time zone | Sending notifications to the right device, in your language, respecting your quiet hours |
| Notification preferences and logs | Which kinds of notification you want (match, friend invitation, announcement) and your quiet hours; which notification was sent when | Following your choices; investigating delivery problems |
We only receive a notification address if you allow notifications on your device. A notification comes only while you are away from the game: 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. Turn, invitation and announcement notifications do not come during your quiet hours. 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 app. You can switch each kind off on its own in Settings › Notifications.
3.7 Virtual currency and purchases
| Data | Description | Why |
|---|---|---|
| Virtual currency movements | When, how much and why your Akçe changed (table entries and payouts, daily gift, rewarded ads); your balance | Keeping your balance right; preventing cheating and abuse |
| Purchase records | Store transaction number, product, time, refund information; the confirmation you gave on the purchase screen | Verifying and delivering your purchase; handling refunds; legal records |
Your payment is taken by the App Store or Google Play. We never receive your card or bank details.
3.8 Ads
Ads are served by Google AdMob: an interstitial between matches, limited in how often it appears (at most once every third finished match and at least 3 minutes apart), a small banner in the menus (home screen, profile, settings) and rewarded ads that you watch only if you choose to. No ads are shown during a match or when the app opens. The Ad-free Pack removes the banner and the ads between matches.
AdMob processes your device's advertising ID, IP address and ad interactions to show ads, limit how often you see them and prevent fraud. Your advertising ID is used for personalised ads only if you allow it (section 5 and "Ad Choices and Permissions"). If you do not, you still see ads, but they are not personalised. In countries where you are not asked (Türkiye included), ads are for now always non-personalised. To verify the reward of a rewarded ad, AdMob is sent only a random, single-use reward number created for that one reward; it is not your player number and does not identify you. Your player number is not sent to AdMob. Your advertising ID never reaches our servers or our analytics.
3.9 Product analytics
| Data | Description | Why |
|---|---|---|
| In-app events | Predefined events such as "progress screen opened", their times, app version, platform and a session number renewed on every launch | Improving the game. Sent only if you allow it |
| Server events | Records of things that already happen on the server, such as "match ended" or "match found" | Running and measuring the Service. If you declined analytics, kept without being linked to you |
| Consent record | Your decision, the text version it applies to, the time | Following your decision and being able to prove it |
Your name, email, IP address, advertising ID, precise location, any text you write and the tiles in your hand are never included in analytics.
On Android, with the same permission, Google Analytics for Firebase (Google LLC, processor) also measures how the app is used: automatic events such as the app opening and 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–17.
3.10 Crash reports
When the app crashes, a technical report is sent to Google Firebase Crashlytics 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, any text you wrote or the tiles in your hand. Crash reports are on by default: keeping the app working and fixing crashes is our legitimate interest (section 5). You can turn them off at any time with the Settings → Privacy → "Crash reports" switch; when you do, sending stops and reports waiting on your device are deleted. For now they are sent on Android only, and never for players aged 13–17.
3.11 Technical records
- Access logs in front of our servers: each time you connect, your IP address, the time and path of the request and the app's identification string (User-Agent) are logged for security and fault investigation.
- Application logs and metrics: our servers keep logs to find errors. Logs may include your player number; they do not include your name, your IP address or your session key.
- Rate limiting: to prevent abuse, your IP address is kept in memory only, for the length of the counter's window (at most 1 hour).
- Backups: encrypted backups of our database are kept in a separate store in the EU.
3.12 What stays on your device
Your session key (in your device's secure storage), your sound and theme preferences, the result of the age screen, your ad consent record and similar settings are stored on your device. Details are in "Cookies, Device Storage and Tracking".
4. What we do not collect
Your email address, phone number, postal address, precise location (GPS), contacts, other photos in your gallery, voice recordings (the app does not ask for microphone access), files, health data or payment card details. There is no free-text chat in the app. We do not process special categories of personal data (such as health, religion, ethnic origin or biometric data), and we do not use facial recognition on photos.
We do not ask for your real name. However, if you sign in with Google, Google's sign-in token carries your Google account's name, which may be your real name. We use it only as described in section 3.1.
5. Purposes and legal bases
| Purpose | Data | GDPR / UK GDPR | KVKK (Türkiye) |
|---|---|---|---|
| Creating and managing your account; running matches, matchmaking, progress, rating, seasons | 3.1, 3.2, 3.3 (matchmaking records) | Art. 6(1)(b) contract | Art. 5(2)(c) contract |
| Showing your profile photo | 3.1 (photo) | Art. 6(1)(b) | Art. 5(2)(c) |
| Putting your Google account's name and photo on your profile once (you can change them at any time) | 3.1 (name and photo of your linked account) | Art. 6(1)(b) | Art. 5(2)(c) |
| Friends, invites, quick messages, blocking | 3.4 | Art. 6(1)(b) | Art. 5(2)(c) |
| Match and friend invitation notifications | 3.6 | Art. 6(1)(b) | Art. 5(2)(c) |
| Learning your age and applying protected mode | 3.1 (birth year, age group) | Art. 6(1)(c) legal obligation and 6(1)(f) legitimate interests | Art. 5(2)(ç) legal obligation and 5(2)(f) legitimate interests |
| Fair play, preventing cheating and abuse, security | 3.1 (name history), 3.3, 3.11 | Art. 6(1)(f) | Art. 5(2)(f) |
| Reports, moderation, automated photo checks, sanctions and appeals | 3.3, 3.4, 3.5 | Art. 6(1)(f); for illegal content 6(1)(c) | Art. 5(2)(f); 5(2)(ç) |
| Answering support requests | 3.5 | Art. 6(1)(b) and (f) | Art. 5(2)(c) and (f) |
| Estimating your country from your IP | 3.1 (country) | Art. 6(1)(f) | Art. 5(2)(f) |
| Virtual currency and purchases | 3.7 | Art. 6(1)(b); 6(1)(c) for keeping records | Art. 5(2)(c); 5(2)(ç) |
| Announcement notifications (18+ only) | 3.6 | Art. 6(1)(f) (you can turn them off at any time) | Art. 5(2)(f) |
| Non-personalised and rewarded ads | 3.8 | Art. 6(1)(f) | Art. 5(2)(f) |
| Personalised ads | 3.8 | Art. 6(1)(a) consent | Art. 5(1) explicit consent |
| In-app analytics | 3.9 | Art. 6(1)(a) consent | Art. 5(1) explicit consent |
| Measuring the Service with server events | 3.9 | Art. 6(1)(f) | Art. 5(2)(f) |
| Crash reports | 3.10 | Art. 6(1)(f) (you can turn them off at any time) | Art. 5(2)(f) |
| Establishing and defending legal claims; answering official requests | As needed | Art. 6(1)(c) and (f) | Art. 5(2)(ç) and (e) |
Our legitimate interests are: keeping the game fair and safe; protecting players from harassment, inappropriate content and cheating; measuring how much and how well the Service works; keeping the app working and fixing crashes; funding a free game with ads; telling you about new features; and being ready for legal claims. You can object to this processing (section 10).
6. Ages 13 to 17: protected mode
If you are 13 to 17 (in India, if you are under 18), the game runs in protected mode:
- only non-personalised ads are shown, and the ad network is told that you are a minor;
- we do not ask for analytics permission; neither analytics nor crash reports are sent;
- the name and photo of your Google account are not taken;
- announcement notifications are not sent;
- your profile photo and name are moderated more strictly;
- an extra explanation is shown before a purchase.
Protected mode turns off by itself at the end of the year in which you turn 18; if we then ask for analytics or personalised-ad permission, the choice is yours. Details are in "Age Policy and Child Safety".
7. What other players see
- Players at your table: your display name, profile photo or avatar, your moves in the match (not your hand), the result and score, and the quick messages you send.
- Everyone: your name, photo or avatar, country and rank on the leaderboard; your profile photo.
- Your friends: whether you are online or in a match (you can turn this off in settings).
- Anyone who knows your player tag: can send you a friend request.
- When you report or block a player, they are not told.
8. Who we share data with
We do not sell your personal data. We share it only with the recipients below, for the stated purposes.
| Recipient | What | Why | Where |
|---|---|---|---|
| Hetzner Online GmbH (processor) | All data on our servers, profile photos and backups | Hosting and storage | Germany (EU) |
| Apple, Google, Meta (Facebook), X (sign-in providers) | We send them no game data; when you sign in we verify the token they issue. Google's token also carries your Google account's name and profile-photo address; we download the photo from Google once (section 3.1) | Linking your account; display name and profile photo | Depends on the provider, mostly the USA |
| Google Firebase Cloud Messaging, Apple Push Notification service (processors) | Notification address (on Android with the Firebase installation ID Google gives the device for it; only if you allow notifications), notification text and type | Delivering notifications to your device | USA and other countries |
| Google Firebase Crashlytics (processor) | Crash reports (on by default, you can turn them off in Settings → Privacy; Android; not sent for ages 13–17) | Finding errors | USA |
| Google Analytics for Firebase (processor) | App usage events, device information, installation number, coarse location from the IP address (only with your permission; Android) | Improving the game | USA |
| Google AdMob and Google's ad partners (independent controllers) | Advertising ID, IP address, device information, ad interactions; a random, single-use reward number (not your player number) for reward verification | Showing ads; personalising them if you allowed it | USA and other countries |
| App Store, Google Play | Transaction details for purchase verification | Verifying your purchase | Depends on the store |
| Competent authorities, courts | What the law requires | Legal obligations; reporting child sexual abuse material | Türkiye or the relevant country |
We sign contracts with our processors requiring them to process your data only on our instructions and with the same or equivalent protection as this policy.
International transfers.
- Data of players in Türkiye is transferred to our servers in Germany and to our service providers. We make these transfers under Article 9 of the KVKK using the standard contracts of the Turkish Personal Data Protection Board, and notify the Board within 5 business days of signing.
- Data of players in the EU and the UK is hosted in the EU. Transfers to providers in the USA rely on the EU–US Data Privacy Framework certification and/or the European Commission's standard contractual clauses (with the UK addendum for UK data).
- We apply the same contractual safeguards for players in other countries.
You can ask for a copy of these safeguards at privacy@tabulastudios.com.
9. How long we keep data
Retention periods are set in our server configuration and applied automatically by scheduled jobs. When a period ends, data is either deleted or kept under a pseudonym: your name and linked accounts are removed and the record stays only with a random player number. Pseudonymised records are still personal data, and this policy still applies to them.
| Data | Period | Then |
|---|---|---|
| Account, profile, birth year | While your account exists | Deleted when the account is deleted (section 11) |
| Unused guest account | 24 months after last use | Same as account deletion |
| Name history | 180 days | Deleted |
| Profile photo | Until you remove or replace it or delete your account. A photo hidden or refused by moderation: until staff delete it, you replace it or your account is deleted. An image reported to the authorities as suspected child sexual abuse material: as evidence for as long as the law requires (at least 1 year), even if your account is deleted; shown to nobody | Deleted |
| Expired session records | 30 days after they end | Deleted |
| Match records, statistics, rating | While your account exists | Kept under a pseudonym after account deletion |
| Move log | 2 years | Kept under a pseudonym; fields linking the match to a player are removed |
| Matchmaking records | 90 days | Deleted |
| Abuse counters | 30 days after the last wait ends | Deleted |
| Friends, blocks, settings | While your account exists | Deleted when the account is deleted |
| Friend requests | 30 days after an answer or expiry | Deleted |
| Invites | 7 days after expiry | Deleted |
| Recent opponents, quick message logs | 30 days | Deleted (copies attached to a report go with the report) |
| Reports | 1 year | Player numbers and evidence deleted; the report type and outcome remain for statistics |
| Support and appeal requests | 365 days after closing | Deleted; deleted at once if you delete your account |
| Sanction and staff action records | 5 years | Deleted |
| Device record and notification address | When invalid, after 60 days without renewal, when you sign out or withdraw permission | Deleted at once |
| Notification logs | 30 days | Deleted |
| Analytics events | 13 months after receipt | Deleted |
| Analytics consent records | While your account exists | Deleted when the account is deleted |
| Crash reports | 90 days (Crashlytics) | Deleted by the provider |
| Google Analytics for Firebase events | Up to 14 months (Google Analytics retention setting) | Deleted by the provider |
| Virtual currency movements and purchase records | As required by financial law, at most 10 years | Kept under a pseudonym after account deletion; deleted at the end of the period |
| Access logs in front of our servers (IP, User-Agent) | 7 days | Deleted |
| Application logs and metrics | 14 days | Deleted |
| Database backups | At most 16 days | Deleted data disappears from backups when they expire |
| Numbers of deleted accounts | Indefinitely; only the random number and the deletion time | To stop late records from re-creating a deleted account's data |
10. Your rights
Wherever you live, we give you these rights:
- to see your data and get a copy (in the app: Settings → Account and profile → Download a copy of my data);
- to have wrong data corrected (you can change your name in the app);
- to have your data erased (section 11);
- to restrict processing;
- to receive your data in a portable file;
- to object to processing based on our legitimate interests;
- to withdraw a permission at any time (Settings → Privacy). Withdrawal does not make earlier processing unlawful;
- to contest a decision based solely on automated processing that significantly affects you (section 12);
- to complain to a data protection authority.
Your right to object. You can always object, on grounds relating to your particular situation, to processing based on our legitimate interests. We will stop unless we have compelling grounds that override your interests or need the data for a legal claim. To object to announcement notifications, simply turn them off in settings; for crash reports, simply turn off the Settings → Privacy → "Crash reports" switch.
How to make a request. Use Settings → Support and appeals in the app or write to privacy@tabulastudios.com. Because we do not know your email address, we confirm your identity with your player tag and, if needed, a check inside the app. We answer within 30 days, free of charge. If a request is complex and the law allows, we may extend this period and tell you why.
Information for your region:
- Türkiye: your rights under Article 11 of the KVKK are set out in the KVKK notice. If you find our answer insufficient, you can complain to the Personal Data Protection Board.
- EU, EEA and Switzerland: you can complain to the data protection authority where you live, work or where the infringement took place.
- United Kingdom: you can complain to the Information Commissioner's Office (ICO).
- 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. However, personalised advertising counts as "sharing" under some state laws; you can stop it in the app under Settings → Privacy → "Ad choices" (Google's consent form). We will not treat you differently for using your rights. We do not process sensitive personal information. You may also make a request through an authorised agent.
- Brazil: you have the rights in Article 18 of the LGPD (confirmation, access, correction, anonymisation, deletion, portability, information about sharing, withdrawal of consent). You can complain to the Autoridade Nacional de Proteção de Dados (ANPD).
- Other countries: you can use the rights your local law gives you in the same way.
11. Deleting your account
- You can delete your account in Settings → Account and profile → Delete account. If you cannot reach the app, use the route on the "Deleting Your Account" page: bumustudios.github.io/tabula-domino/delete-account.
- After the request your account is frozen for 14 days: you cannot play and your name no longer shows in friends lists. You can cancel the deletion during this time. When it ends, the deletion happens automatically and the app shows you that it is complete.
- Deleted: your display name (including its copies in match records), name history, birth year, profile photo, avatar, player tag, linked accounts, sessions, country, notification records and preferences, friendships, requests, blocks, invites, quick message logs, matchmaking records, support requests and analytics consent records. If you signed in with Apple, your Apple link is revoked too.
- Kept under a pseudonym (without your name or account links, only with a random number): match records and move logs (these are also other players' records), statistics and rating totals, sanction and staff action records, virtual currency movements and purchase records. Their periods are in section 9.
- Your analytics events remain, unlinked from you.
- A report made about you stays until the end of its retention period; your player number in it is replaced with a new number that cannot be traced back to you.
- Deleted data disappears from backups when they expire (at most 16 days).
12. Automated decisions
- Matchmaking: the system picks your opponents automatically, based on your rating.
- Short matchmaking waits: if you cancel many searches in a short time or do not show up for a match, the system may keep you out of matchmaking for a few minutes. This is not an account sanction.
- Name and photo filters: a name that seems to break the rules may be refused automatically; a new photo may be refused automatically, or shown only to you until someone from our team has looked at it. You can challenge these decisions through the "Support and appeals" form; a person reviews your challenge.
- Account sanctions are always decided by a person.
These automated steps do not produce legal effects or similarly significant effects on you; you can still challenge them.
13. Security
- All traffic between the app and our servers is encrypted (TLS).
- Your session key is in your device's secure storage; only a hash of it is kept on our servers. We do not use passwords.
- Identity data is kept in a separate part of the database; other parts only know your random player number.
- Backups are encrypted and kept in the EU, in a store separate from the server.
- Our staff access data only when their work requires it, and every action is logged.
No system is completely secure. If a data breach occurs, we notify the competent authority within the legal deadlines (for example 72 hours under the GDPR and the KVKK) and, where required, we notify you.
14. Changes and languages
We may update this policy. Each version has a number and an effective date. We announce material changes in the app in advance. If processing based on your permission changes materially, we ask for your permission again. This policy is published in several languages; if the versions differ, the reading more favourable to you applies.
15. Contact
For any privacy question: privacy@tabulastudios.com · BumuStudios, an independent developer (no postal address is published yet) · in the app: Settings → Support and appeals. Our EU and UK representatives have not been appointed yet (section 2); until then, write to privacy@tabulastudios.com.