Privacy Policy

1. Who is responsible

Monkey Beat is provided by np, the developer responsible for the processing described in this policy. This policy covers the Android application com.np.monkeybeat, its hosted Monkey Beat game and this privacy page.

For support or privacy requests, contact pasnikvld@gmail.com.

2. Information we use

Local game and application data

The game stores your personal best and sound preference in local WebView storage. The Android app stores settings, notification and diagnostic choices and the selected game experience. Navigation state is kept to support Back and screen restoration. These records are not a player account or a cloud leaderboard; the current game does not send your score to our server.

The app and game read device language settings to choose available text. The game also respects the device's reduced-motion preference. Supported app data may be backed up or transferred by Android according to your device settings; notification registration and consent settings are excluded from the app's backup rules.

Game delivery

Firebase Hosting delivers the game over HTTPS. Hosting and other network services process connection information such as IP address and user-agent information to deliver content, operate the service and prevent abuse.

To deliver the game and display appropriate content, Google Firebase processes an installation identifier and technical information such as country and language codes, time zone, app version, operating-system version and SDK information. This basic service processing is separate from optional notifications and crash reports.

If you open a supported app link, a limited experience code from that link may be saved locally and sent to Firebase to select suitable content. The app does not send the complete incoming link or arbitrary extra query parameters for this purpose.

Optional notifications

When you enable notifications and allow the necessary Android permission, Firebase Cloud Messaging registers the installation for game updates. Google processes an installation identifier, an FCM registration token and relevant app/device metadata to deliver those messages. The app keeps the token privately on your device and subscribes to a public game-update topic. It also stores the last received message identifier and time locally.

Optional crash and error reports

Crash reporting is off by default. If you enable Crash and error reports, Firebase Crashlytics processes crash traces, app/session and installation identifiers, timestamps, relevant app state and device/OS information to help diagnose reliability issues.

Our manually generated WebView reports contain an error category, source type, numeric error code where available and WebView version. They do not include page URLs, query strings, raw console messages, selected file names or notification tokens. The Firebase crash SDK can collect broader technical crash context when reporting is enabled.

Files and support messages

The Android wrapper can pass a document you explicitly choose in the Android system picker to the current web page if a page presents a file input. It does not grant the page access to all your files. The current Monkey Beat game has no file-upload feature and does not upload documents.

If you email us, we receive your email address and the information you include so that we can answer your request. Please do not send passwords, payment details or identity documents.

3. Choices and purposes

Open the Android app's Back → App settings menu to manage notifications and crash reporting independently. You can play without enabling either option. Android's own notification settings can also block notifications immediately.

Turning off notifications removes the locally stored token, cancels displayed notifications and requests topic unsubscription and token deletion. Remote cleanup requires a network connection and is retried if necessary. Already queued or SDK-displayed background notifications may still arrive during that cleanup; the Android notification switch remains an immediate device control.

Turning off crash reporting stops our manual reports immediately and discards unsent reports. Restart the app for the Firebase SDK's automatic reporting setting to apply fully. This does not retroactively remove reports already sent.

Where a legal basis is required, we rely on your consent for optional notifications and diagnostic uploads; legitimate interests in operating, securing and delivering the app for necessary game-delivery and service data; and applicable legal obligations where relevant. Support information is used to respond to your request. You may withdraw optional consent at any time without affecting the lawfulness of earlier processing.

4. Service providers and disclosures

We use Google Firebase for game delivery, necessary app services, notifications and optional crash reporting. Google processes the relevant data as a service provider under its applicable terms, including through subprocessors. We do not sell personal data or use the current app's data for personalized advertising.

Data may also be disclosed where legally required, to respond to a valid legal request or to protect users and the security of the service. If you follow an external link, that service handles its own data under its own policy.

More information: Firebase privacy and security and Google Privacy Policy.

5. Security and international processing

The app uses HTTPS for Firebase requests and hosted game delivery. Private Android settings are kept in the app's storage area; selected documents require a user action and a read-access grant. No method of storage or transmission is completely secure.

Google and its service providers may process information in countries other than your own. Applicable contractual and transfer safeguards used by Google are described in Firebase's Data Processing and Security Terms.

6. Retention and deletion

• Local progress and settings: retained until overwritten or removed through Android's clear-app-storage function or uninstall. Android-managed backups may have their own retention and restoration settings.
• Notification registration: retained while needed for enabled updates. Disabling notifications requests remote token deletion when online. The Firebase installation identifier is also used by necessary app services; turning off notifications does not delete that separate identifier.
• Crash reports: Firebase documents a 90-day retention period for crash traces and associated identifiers before removal from live and backup systems begins.
• Firebase service data: installation identifiers are subject to Firebase's deletion process. Hosting IP data is retained by Firebase for a few months. Provider retention is described in the linked Firebase privacy information.
• Support correspondence: retained as needed to resolve the request and meet applicable obligations, then removed when no longer needed.

Clearing app storage or uninstalling removes local app data but does not automatically erase reports or service records already held by Google. Contact us to request deletion of data for which we are responsible. We will assess and carry out requests as required by applicable law and the provider's available deletion mechanisms. We do not promise immediate deletion of every provider record or backup.

7. Your privacy rights

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, receive portable data, and withdraw consent. If you are in the EEA or UK, you may also complain to your local data-protection authority.

Send a request to pasnikvld@gmail.com and identify Monkey Beat. We may ask for information reasonably necessary to verify and locate relevant records. We do not maintain named player accounts, so some installation-level data cannot be associated with a person from an email address alone.

8. Younger users

The game does not ask for a birth date or create child profiles. We do not knowingly request names or contact details from children through the game. A parent or guardian who believes a child has provided personal information can contact us so that we can investigate and take appropriate action.

9. Policy changes

We will update this page when our data practices change. The date above identifies the current policy. If a future game or feature introduces materially different collection, we will update the disclosures and request any additional consent required before that processing starts.

10. Contact