Dart Rush privacy

Updated 25 October 2026

This privacy notice explains how personal data are processed in Dart Rush for Android and iPhone and how the shared leaderboard is published on lazyshoregames.com.

1. Controller and contact

For game issues, you can also contact support@lazyshoregames.com. This notice covers Dart Rush. The website privacy notice also applies to general website visits and messages.

2. Starting the game, combined acceptance and withdrawal

Dart Rush requires combined acceptance of the terms, Firebase gameplay analytics and Firebase crash reporting before you can play. Without this acceptance, play is blocked, including guest play. Signing in with Google or Apple is separate and optional. Opening this privacy notice is not itself consent. Advertising choices are handled separately.

In “Privacy and choices”, you can open the documents and withdraw the combined acceptance. After you confirm withdrawal, the app removes the decision locally, stops its own analytics and diagnostic events, and requests the SDK-supported disabling of collection and deletion of unsent crash reports. Play ends or is blocked; the startup dialog appears again before you can resume play. This does not delete your local record, settings or sign-in account.

Withdrawal concerns subsequent processing. Previously transmitted data do not automatically disappear. Section 7 explains the technical limits of crash reporting. Signing out, withdrawing acceptance and deleting an account are separate actions.

3. Data on your device

The app stores your local record, language, volume and other game settings, selected designs, and the version and status of your startup decision. Signing in does not automatically turn a local record into an online leaderboard result or transfer it to another device.

Firebase may store a sign-in session on your device so you do not need to sign in at every launch. During account deletion, the app stores information needed to resume the request and check its status safely. Provider access tokens are not stored as part of the app's own saved deletion request. Operating-system backups may contain local app data.

4. Internet connectivity and protection of online services

Dart Rush requires an internet connection, including guest play. At startup, it sends the platform, app version and build number to our version check. During use, it checks connectivity, including through connectivity-check addresses operated by Google and, where applicable, Apple. Technical connection data such as your IP address are processed in these requests.

Sign-in, leaderboards, result validation and deletion requests use Google's Firebase services. To protect certain game requests, the app uses Firebase App Check with Google Play Integrity on Android and Apple App Attest on iPhone. This involves technical app or device integrity evidence and time-limited attestation tokens. These security and operational requests are separate from gameplay analytics and can be necessary without a Google/Apple game sign-in.

5. Optional sign-in and player profile

You can play as a guest without a game account. If you choose Google or Apple sign-in, Firebase Authentication processes the account identifiers and authentication data supplied by the provider and, where available, your email address and profile information. Apple may supply a relay email address. Dart Rush does not require a separate game password. An additional sign-in provider is linked only after your confirmation.

Your public player name is stored separately from the sign-in profile in a private player profile, checked against the naming rules and reserved. Your Google/Apple profile name and email address are not automatically published as your leaderboard name. Freely changing a name after assignment is not a standard feature; you can still make rectification and privacy requests. Your selected country flag is an optional profile choice and does not establish your nationality or actual location.

6. Leaderboards, result validation and name reports

Android and iPhone share all-time and weekly rankings. Entries involve the player name, score, time achieved, record platform, an optional selected country flag and weekly awards. The backend uses an account identifier and derived player identifiers for association. These identifiers are pseudonymous, not equivalent to anonymous data. A derived player identifier is also used by the game's interface.

The leaderboard is public. Other people can see your name, rank, score, selected flag, the Android/iPhone platform used for the record, and your weekly win count or current winner status in the game and on our website. The game additionally displays the record date. The website does not disclose your email address, Firebase account ID or derived player identifier. Your flag is not inferred from your IP address. Other parties may copy public information; we do not fully control their independent processing.

Only signed-in players with an approved name can submit results. Guests can view rankings and an indicative rank preview. Operation and plausibility checks process run identifiers, start and expiry times, hits and misses, rounds, lives, scores, revisions and a possible single continuation after a rewarded video. Technical access information and temporary identifiers derived from IP addresses also help limit abusive requests. A new week resets the current ranking but does not automatically erase all historical results and awards.

If you report a player name, we process associations with the reporting and reported accounts, the name, selected reason, timestamps and handling status. The name and report reason are sent to our SiteGround-hosted support mailbox for handling. The reporter's identity is not displayed in public rankings. Automatic result checks can reject entries; support handles name reports. You can contact us about privacy requests and objections.

7. Gameplay analytics and crash reports

Firebase Analytics

The app activates Firebase Analytics after the combined acceptance is recorded. It processes gameplay and usage events, such as game starts and endings, rounds, scores, lives lost, pauses and advertising continuations, with associated app and device information. The SDK may also process automatic events and app-instance or device identifiers. These data help us evaluate usage and gameplay and improve the game. Our game code does not deliberately supply your Firebase account ID, public player name or email address as an Analytics user identifier.

Firebase Crashlytics

The combined acceptance also enables automatic Crashlytics reporting. Reports may contain error messages, technical stack traces, app and operating-system versions, device state, installation identifiers and gameplay context preceding an error. We use them to investigate and fix errors.

Without acceptance or after withdrawal, the app requests disabling and deletion of unsent reports. However, the native SDK may store errors locally even while sending is disabled. Locally cached reports may be transmitted after collection is enabled again. Some SDK settings take effect on the next app launch, and transmissions already started may still complete. See Crashlytics data collection.

8. Advertising and separate advertising choices

Dart Rush uses Google AdMob for occasional full-screen ads after game over and optional rewarded videos. Completing a rewarded video successfully may allow a single continuation. Ads are requested only when the actual state reported by Google's User Messaging Platform (UMP) permits requests. Where available, “Ad privacy” in the game lets you reopen your choices. Combined startup acceptance does not replace this advertising choice, and a UMP choice does not authorise Firebase gameplay analytics.

Advertising requests may involve Google and the advertising partners actually used processing your IP address, approximate location derived from it, device and advertising identifiers, app/SDK diagnostics, and ad or video interactions. The ads and identifiers used depend on matters including platform, region, system settings and your advertising choice. Non-personalised or limited ads can still process technical data. Any required iOS tracking permission is an additional requirement. See Google's advertising information.

9. Shop and in-app purchases

You can buy optional designs and “Remove ads” through the App Store or Google Play. The technical integration uses Unity In-App Purchasing. It processes product and pricing information, purchase status, transaction or receipt information and purchase entitlements to associate purchases, unlock content and restore purchases using the same store account. The relevant store processes payments. Our app does not request complete credit-card details or operate its own payment server.

A Google/Apple game sign-in does not automatically transfer purchases between stores. Deleting the Firebase game account does not automatically delete or refund store purchases. The store's processing is also covered by the information provided by Apple or Google.

Depending on the features used, the Unity purchase integration may also process technical identifier, device, installation and session information and purchase-processing data. See the Unity In-App Purchasing privacy information. You can contact our privacy address about attributable purchase and SDK data.

10. Purposes and legal bases

We process data for necessary game, account, ranking and purchase operations under Article 6(1)(b) GDPR insofar as processing is needed to provide the service you request. Necessary processing for security, abuse prevention, moderation and general enquiries is based on legitimate interests under Article 6(1)(f) GDPR: reliable game operation, fair rankings and handling enquiries. Legal obligations are fulfilled under Article 6(1)(c) GDPR.

Where processing or access to a device requires consent, valid consent is necessary, in particular under Article 6(1)(a) GDPR and section 25(1) of Germany's TDDDG. The exception in section 25(2) TDDDG applies to storage and access strictly necessary to provide a service expressly requested by you. An interest in improving a game does not replace a requirement for consent.

11. Recipients and processing outside the EEA

Recipients include Google for Firebase, Analytics and AdMob, your selected Google/Apple sign-in provider, Apple or Google for store purchases, the Unity services responsible for the active purchase integration, and SiteGround for support email and website hosting. Providers may use affiliates and subprocessors. Their privacy information also applies to processing for their own purposes.

The game's Firestore database and our Cloud Functions are configured in Frankfurt, Germany. This does not mean all authentication, analytics, crash, advertising, SDK or support data are processed exclusively there. Access and processing outside the European Economic Area, including the United States, are possible. Where required, an appropriate transfer mechanism, such as an applicable adequacy decision or standard contractual clauses, must be used. You can ask our privacy contact for information about the safeguards applicable to your data and copies of them.

Further information: Firebase, Google, Apple, Unity and SiteGround.

12. Retention

We retain personal data only while needed for the purpose or a legal retention requirement. For the individual data categories:

• Local records and settings: until you reset app data or the operating system removes them; device backups may have a separate retention cycle.
• Game account, profile, names, rankings and awards: generally for use of your game account and until associated deletion. A weekly reset does not erase the full history.
• Online runs: a run ticket is valid for up to four hours. Automatic deletion is configured for seven days after expiry.
• Name reports and moderation actions: automatic deletion is configured for 90 days after creation. Handling links expire after seven days. Email copies also follow support retention.
• Account-deletion completion receipt: minimal status and hash data with a deletion marker 24 hours after completion. Incomplete requests remain available for recovery.
• Cloud logs: the default log bucket is configured for 30 days; mandatory cloud audit logs for 400 days. These periods cover the data recorded in the respective log buckets.
• Crashlytics: Google specifies 90 days for crash reports and associated identifiers before removal from live and backup systems begins. For authentication data, Google specifies a separate cleanup process of up to 180 days after account deletion is initiated. See Firebase retention information.
• Support: while necessary to handle the request and reasonable follow-up; legally required records and evidence necessary for legal claims are handled under the applicable requirements.

The configured deletion times do not guarantee removal at an exact time. Automatic database cleanup is asynchronous. Provider, backup and log data may follow other cycles.

Analytics, advertising and purchase services: User- and event-level Analytics data follow the retention settings of the Google Analytics property used. The affected data are automatically deleted after the applicable period; settings for renewed user activity may affect when that period starts. Aggregated reporting may follow different retention rules. For advertising and purchase services, their processing purposes and statutory retention requirements also apply. See Google Analytics data retention and the provider information linked above.

13. Deleting your game account

You can request deletion in the game or on our Dart Rush deletion page. This requires a fresh account check and explicit confirmation. For a linked Apple account, revocation of Apple sign-in authorisation is also handled. Completion is displayed only after server processing is confirmed.

Our deletion process removes the Firebase game account, profile and name reservations, associated current and historical leaderboard entries, online runs, and attributable reporting, moderation and protection data. It does not delete your Google/Apple provider account, store purchases or local records and settings. Deleting the Firebase account does not automatically remove all previously sent Analytics, Crashlytics, advertising or any Unity data. Contact our privacy address for further requests. We check the association and available deletion methods; an account email address alone does not always identify every SDK identifier.

14. Your rights

Where the legal requirements are met, you have rights of access, rectification, erasure, restriction and data portability. You can object to processing based on legitimate interests on grounds relating to your particular situation. You may withdraw consent for the future without affecting the lawfulness of processing based on it before withdrawal.

Contact info@lazyshoregames.com. Proportionate identity verification may be necessary to associate the request safely. You can complain to a data protection supervisory authority, including the State Commissioner for Data Protection and Freedom of Information North Rhine-Westphalia.

15. Minors and changes

Where processing requires a minor player's consent, applicable age and parental-authorisation requirements must be observed. A store age rating does not replace required data protection consent.

We update this notice when processing changes. New or changed purposes requiring consent need corresponding information and a valid choice.