Privacy Policy — TapDash Royale
- Effective date: 4 October 2026
- Application: TapDash Royale
This policy explains what TapDash Royale collects, why, who it is shared with, and what you can do about it. It covers the app on Android and on iPhone. Where the two differ, the difference is named.
1. What we collect
1.1 The display name you type
Before you host or join a room, the app asks for a display name of up to 16 characters. You choose this yourself and it is shown to every other player in the room.
Please note: if you type your real name, your real name is what other players see and what is stored. We recommend a nickname.
In ONLINE play, the name is stored in our Firebase Firestore database alongside the room, and is visible to anyone who has the room’s code.
In LOCAL play, the name is transmitted only to the other devices on your Wi-Fi network and is never stored by us.
1.2 An anonymous identifier
The first time you create or join an ONLINE room, the app signs in through Firebase Anonymous Authentication. This produces a random identifier that lets the game tell players apart and lets you rejoin a match if your connection drops. The app reuses it for later ONLINE matches. It is not linked to a Google account, an Apple account, an email address, or any other identity, and we cannot use it to work out who you are. Firebase keeps it with the time it was created and last used, and nothing else.
If you only play LOCAL, no identifier is created.
1.3 Gameplay data
For each ONLINE room we store: the room code, the host’s anonymous identifier, the number of rounds, the current round, the number of players, when the room was created, and when the host was last heard from. For each player in it we store: their display name, their score for the current round and their total, whether they are the host, and when they joined and were last seen. The timestamps are what let the game notice that a player or the host has left.
Section 6 explains when this is deleted.
1.4 Crash and error diagnostics
The app uses Google Firebase Crashlytics to report crashes and certain handled failures — for example, being unable to create or join a room. These reports may include: the type and model of your device, its operating system version, the app version, the state of the app at the time, a stack trace, and a random Crashlytics installation identifier. We also attach two labels describing which mode (LOCAL or ONLINE) and which role (host or player) was in use, because a failure is difficult to interpret without them. Crashlytics also records when each session of the app starts, so that crash rates can be measured.
Crash reporting is disabled in development builds and is uploaded the next time you open the app after a failure. These reports do not include your display name or a room code.
1.5 Advertising
The app displays banner advertisements on some screens and one full-screen advertisement at the end of a match. These are served by Google AdMob.
Banner advertisements are never shown during a round of play or on the winner screen. The full-screen advertisement appears as the winner screen opens.
AdMob may collect and process your device’s advertising identifier, IP address, general device information, and your interactions with advertisements, in order to serve and measure ads. On Android 13 and later it may also use the ad topics and ad measurement features of Android’s Privacy Sandbox, where they are turned on on your device.
Where required by law — in the European Economic Area, the United Kingdom and Switzerland — the app presents Google’s consent form when it starts, before the advertising SDK starts, and your choice there governs whether you are shown personalised ads.
On iPhone, the app also asks, through Apple’s tracking prompt, whether it may use your device’s advertising identifier to track you. The game is the same whichever you choose, and you can change your answer at any time in Settings → Privacy & Security → Tracking.
Google’s use of this data is governed by its own policies:
2. What stays on your device
The following are stored on your phone. The app never uploads them to us:
- Your chosen language.
- A tap sound you import, if you choose to. The whole audio file is copied into the app’s private storage so it keeps working after you move or delete the original, along with its file name and the section you selected. This sound plays only on your own device — the other players in the room never hear it.
- A copy of the ONLINE rooms you played in, kept by Firebase on your device, including the other players’ display names and scores.
- Your anonymous sign-in (section 1.2), your advertising consent choice, and identifiers used by Google’s crash reporting and advertising software.
All of this is removed when you uninstall the app or clear its data. On iPhone, iOS can keep the anonymous sign-in in the device’s keychain after the app is deleted, so reinstalling may bring back the same identifier.
Your phone’s own backup can include some of it. On Android, if backup is on for your phone, Android includes the app’s data in its backup to your Google account and restores it if you reinstall the app. On iPhone, iCloud Backup and backups to a computer include your tap sound, your settings and the copy of rooms. Those backups belong to your Google or Apple account, and we have no access to them.
2.1 The camera
If you use the QR-code shortcut to join a room, the app opens your camera. The image is examined on your device for a room code and is not recorded, stored, or transmitted anywhere. The camera runs only while the scanner screen is open.
The camera is always optional. Typing the room code by hand does exactly the same thing, and the app installs and runs on devices with no camera.
2.2 Sharing your result
The winner screen can share an image of the final standings, showing the champion and the top five players’ display names and scores. The image is produced on your device and is handed to your phone’s own share sheet only when you tap the share button. You choose where it goes; we do not receive a copy. A copy stays in the app’s temporary storage until your phone clears it or you clear the app’s data.
3. What we do not collect
- No accounts, real names, email addresses or phone numbers.
- No location data. The app does not request location permission.
- No contacts, photos, files, microphone or call data.
- No general-purpose analytics or behavioural tracking SDK. The app does not include Google Analytics or any comparable product.
- No purchases. The app contains no in-app purchases.
4. Why we collect it
| Data | Purpose |
|---|---|
| Display name and score | To run the match and show the standings. |
| Anonymous identifier | To tell players apart and allow rejoining. |
| Timestamps | To detect players and hosts who have left. |
| Crash diagnostics | To find and fix defects. |
| Advertising data | To fund the app’s development. |
We do not sell your data, and we do not use it to build a profile of you.
5. Who it is shared with
Data described in section 1 is processed by Google LLC in its capacity as our service provider, through the following products:
- Firebase Authentication — anonymous sign-in
- Cloud Firestore — room and player data during ONLINE matches
- Firebase Crashlytics — crash and error reports
- Google AdMob — advertising
Other players in your room see your display name and score. That is the point of the game, but it is worth stating plainly: a room code is all that is needed to see the names in that room.
We do not share data with anyone else, and we do not sell personal information.
6. How long it is kept
The app deletes ONLINE room data at two points, and needs a connection to do so:
- When the host taps “PLAY AGAIN” on the winner screen, the room and every player in it are deleted.
- When a player taps “PLAY AGAIN”, or “LEAVE ROOM” after the host has left, that player’s record is deleted.
Nothing else deletes room data. If the host closes the app, loses the connection or stops before the winner screen, the room and its players remain in our database. If a player closes the app instead, their record remains in the room. We do not currently delete these rooms automatically. We delete one when asked (section 7).
The anonymous identifier is not deleted.
Crash reports are retained by Firebase Crashlytics under Google’s standard retention period, currently 90 days.
LOCAL play stores nothing off your device, so there is nothing to delete.
7. Your rights and choices
Advertising. The app does not yet have a button to reopen the consent form. To choose again, clear the app’s data on Android, or delete and reinstall the app on iPhone; the form is shown again the next time the app starts, where consent is required. On iPhone, you can also change whether the app may track you in Settings → Privacy & Security → Tracking.
On-device data. Uninstalling the app, or clearing its data in Android Settings, removes everything listed in section 2, subject to the iPhone keychain note there. To remove only an imported tap sound, tap “REMOVE” under “Tap sound” in the app’s settings.
Access and deletion. Depending on where you live, you may have rights under the GDPR, the UK GDPR, or the CCPA/CPRA to access, correct, or delete personal data we hold, and to object to its processing.
Please note a genuine limitation here: because ONLINE play uses anonymous sign-in, we have no way to connect a request from you to a particular record in our database. There is no email address or account to search on. What we can find is a room, by its code. If you contact us (section 12) with the room code, we will delete that room and every player in it within 30 days, and reply to confirm. If the room has already been deleted, we will tell you so.
The steps for deleting your data are set out in full at https://zerojumpapps.com/legal/tapdash-royale/deletion/.
Legal basis (EEA/UK). We rely on legitimate interests for running the game and for crash diagnostics, and on your consent for personalised advertising.
8. Children
TapDash Royale is intended for a general audience aged 13 and over. It is not directed at children under 13, and we do not knowingly collect personal information from children under 13.
If you believe a child under 13 has provided information through this app, contact us (section 12) and we will delete what we can identify.
9. Security
ONLINE data is transmitted over encrypted connections to Google’s servers and protected by database rules that prevent a player from altering another player’s record or from listing the rooms of other players.
LOCAL play happens over your own Wi-Fi network. Traffic between phones on that network is not encrypted, on the assumption that everyone playing is in the same room as you. Do not use LOCAL play on a network you do not trust if your display name is sensitive.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
10. International transfers
Google processes data on servers that may be located outside your country, including in the United States. Where required, these transfers rely on the safeguards Google maintains, such as the European Commission’s Standard Contractual Clauses.
11. Changes to this policy
We may update this policy as the app changes. The effective date at the top will be revised, and material changes will be announced in the app’s store listing. Continuing to use the app after a change means you accept the revised policy.
12. Contact
Questions, requests or complaints:
- support@zerojumpapps.com
- Zero Jump Apps, LLC
Zero Jump Apps, LLC is established in the Commonwealth of Puerto Rico, United States. This policy is governed by the law of Puerto Rico and by applicable United States federal law.
If you are a resident of Puerto Rico, you may raise a consumer complaint with the Puerto Rico Department of Consumer Affairs (Departamento de Asuntos del Consumidor, DACO).
If you are in the EEA or the UK and are not satisfied with our response, you may lodge a complaint with your local data protection authority.