ZeroJumpAppsZeroJumpAppsAPP STUDIO
← TapDash Royale

Privacy Policy — TapDash Royale

LAST UPDATED · 26 JULY 2026

This policy explains what TapDash Royale collects, why, who it is shared with, and what you can do about it. It covers the Android application. An iOS version is not currently published; this policy will be updated before one is.

1. Summary

TapDash Royale is a party tap-battler played by up to 100 people at once. It does not ask you to create an account, and it never asks for your real name, email address, phone number or location.

There are two ways to play, and they differ sharply in what leaves your device:

  • LOCAL play — the game runs entirely over your own Wi-Fi network. Your display name and score travel directly between the phones in the room. Nothing is sent to our servers or to any third party for gameplay purposes. LOCAL play works with no internet connection at all.
  • ONLINE play — the game uses Google Firebase. Your display name, score and a randomly generated anonymous identifier are stored on Google’s servers for the duration of the match.

Advertising and crash reporting operate in both modes when the device has an internet connection.

2. What we collect

2.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 six-character code.

In LOCAL play, the name is transmitted only to the other devices on your Wi-Fi network and is never stored by us.

2.2 An anonymous identifier

ONLINE play signs you 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. It is not linked to a Google account, an email address, or any other identity, and we cannot use it to work out who you are.

2.3 Gameplay data

For ONLINE matches we store, for the life of the room: your display name, your score, the room code, the current round number, the number of players, and timestamps recording when you joined and when you were last seen. The last of these is what lets the game notice that a player or the host has left.

2.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.

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.

2.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.

Advertisements are never shown during a round of play or on the winner screen.

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. Where required by law — in the European Economic Area, the United Kingdom and Switzerland — the app presents Google’s consent form before the advertising SDK starts, and your choice there governs whether you are shown personalised ads.

Google’s use of this data is governed by its own policies:

3. What stays on your device

The following are stored only on your phone. They are never uploaded, and we never see them:

  • Your chosen language.
  • A tap sound you import, if you choose to. The audio file is copied into the app’s private storage so it keeps working after you move or delete the original, along with the one-second section you selected. This sound plays only on your own device — the other players in the room never hear it.

All of this is removed when you uninstall the app or clear its data.

3.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.

3.2 Sharing your result

The winner screen can share a screenshot of the final standings. 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.

4. 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.

5. 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.

6. Who it is shared with

Data described in section 2 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.

7. How long it is kept

ONLINE room data is deleted when the host leaves the room or when the match finishes. If you leave a room on your own, your player record is removed at that moment.

One honest exception: if a host force-quits the app rather than leaving the room properly, that room’s data may remain in our database. We are working on automatic cleanup for this case.

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.

8. Your rights and choices

Advertising. If you are in a region where consent is required, you can change your advertising choice at any time from the consent form.

On-device data. Uninstalling the app, or clearing its data in Android Settings, removes your language setting and any imported tap sound.

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. In practice this means room data cannot be looked up on request — but it also means it is short-lived and already anonymous, and it is deleted when the match ends. If you contact us at support@zerojumpapps.com with the room code and display name you used, we will do what we can.

Legal basis (EEA/UK). We rely on legitimate interests for running the game and for crash diagnostics, and on your consent for personalised advertising.

9. 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 at support@zerojumpapps.com and we will delete what we can identify.

10. 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.

11. 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.

12. 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.

13. Contact

Questions, requests or complaints:

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.