Murder Drones Endless Way 2D Privacy Policy
Effective date: 2026-04-11
This Privacy Policy explains how RimuruDev ("we", "us", or "our") processes data in connection with the mobile game Murder Drones Endless Way 2D (the "Game").
It describes what data we process, why we process it, when we may share it with service providers, how long we keep it, and how you can request access, correction, or deletion of your Cloud Save data.
1. Controller and Contact
Data controller: RimuruDev
Contact email: rimuru.dev@gmail.com
2. Scope of This Policy
This Privacy Policy applies to the Game and related backend functionality that supports features such as Cloud Save, account linking, leaderboard, crash diagnostics, and service security.
Certain third-party SDKs, platforms, or external services used by the Game may process data under their own privacy policies.
3. What Data We Process
Depending on the features you use, we may process the following categories of data.
3.1 Account and identity data
We may process:
• accountId in the format guest:<guid> or google:<sub>
• a guest GUID generated by the Game
• the Google subject identifier (sub) when you link or sign in with Google
• account link state information required to connect guest progress with a Google-linked account
We do not store your Google account password.
Your Google account email may be shown or used during the sign-in or linking flow by Google services. Unless a specific feature requires otherwise, it is not stored persistently by us.
3.2 Cloud Save data
When Cloud Save is used, we may process and store gameplay progress data, including for example:
• currencies
• skins or cosmetic unlocks
• best score
• profile values such as display name and icon ID
• event currencies or similar limited-time progress values
• save metadata such as revision, schema version, and timestamps
3.3 Leaderboard data
When the leaderboard feature is used, we may process:
• best score submitted for ranking
• rank position and related ranking display values
• profile display data required for the leaderboard interface, such as display name and icon ID
3.4 Technical and diagnostics data
For security, reliability, and troubleshooting, we may process technical data such as:
• app version
• operating system version
• device model
• install identifier
• hashed device identifier, when available
• IP address
• request timestamps and related metadata
• crash logs, error logs, and diagnostics
• rate-limit, anti-abuse, and service integrity events
3.5 Google authentication flow data
If you use Google sign-in or account linking, we may process technical data required to complete the authentication flow securely, including the Google subject identifier (sub) and temporary OAuth-related state data.
If Google account email is involved in the sign-in user experience, it is handled only to the extent necessary for that flow and is not stored persistently by us unless explicitly required for a support or account function.
4. Why We Process Data
We process data for the following purposes:
• to synchronize player progress between installations or devices
• to restore saved progress after reinstall, device change, or data loss
• to operate, maintain, and display the leaderboard
• to link guest progress with a Google-linked account when requested by the player
• to protect the Game and backend infrastructure through rate-limiting, anti-abuse controls, and security monitoring
• to diagnose crashes, errors, and technical failures
• to maintain backend stability, compatibility, and service performance
• to comply with applicable legal obligations
5. Legal Basis for Processing
We process data based on one or more of the following legal grounds, as applicable:
• your consent, where consent is required
• your request to use specific Game functionality, including Cloud Save, account linking, and leaderboard
• performance of functionality you intentionally use within the Game
• compliance with obligations applicable under relevant personal data laws, including the legislation of the Russian Federation, such as Federal Law No. 152-FZ "On Personal Data"
We do not provide legal analysis in this Privacy Policy, but we aim to process data only to the extent reasonably necessary for the Game features described here.
6. How Long We Keep Data
We keep data only for as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer retention period is required by law or necessary for security, dispute resolution, or abuse prevention.
6.1 Cloud Save retention
• Cloud Save data linked to an active account may be retained while the account remains in use.
• Guest Cloud Save data may be removed after prolonged inactivity under our retention policy.
• Our current target retention policy for inactive guest Cloud Save data is up to 24 months of inactivity, after which it may be deleted or anonymized.
• If you request deletion and we can verify account ownership, we will delete or anonymize the relevant Cloud Save data unless retention is required by law or necessary for legitimate security or fraud-prevention reasons.
6.2 Leaderboard retention
Leaderboard-related data may be retained while the leaderboard feature remains active and the associated records remain relevant for operation, integrity, ranking display, anti-abuse review, or dispute handling.
6.3 Logs and diagnostics retention
Technical logs, crash reports, and diagnostic data are generally kept for a limited period, typically 30 to 90 days, unless a longer period is reasonably required for security investigation, abuse prevention, or legal compliance.
7. How to Request Deletion of Cloud Save Data
If you want us to delete your Cloud Save data, you can request deletion by email.
Step-by-step request process
1. Send an email to rimuru.dev@gmail.com.
2. Use the subject line: Cloud Save Data Request.
3. In the message, include your accountId in the format guest:... or google:....
4. Clearly state that you want deletion, access, or correction of your data.
5. If available, include helpful verification details such as device model, approximate last play date, screenshots, or other identifying context.
For security reasons, we may request additional confirmation to verify that you control the account before we process deletion or other account-related requests.
Initial response target: up to 10 business days.
Full request handling timeline: as required by applicable law.
8. Access, Correction, and Deletion Rights
Subject to applicable law and our ability to verify account ownership, you may request:
• access to the data associated with your account
• correction of inaccurate account-related data
• deletion of eligible Cloud Save data and related account data
In some cases, we may be unable to fulfill a request fully, for example if we cannot verify ownership, if deletion would interfere with fraud prevention or security review, or if retention is required by law.
9. Third-Party Services and Recipients
Depending on the Game build, platform, and enabled features, data may be processed by the following categories of third parties:
• Timeweb Cloud — server hosting infrastructure located in Russia
• Google Play Services — platform and related service functionality
• Google OAuth / Google Identity services — sign-in and account linking functionality
• Firebase — for example Crashlytics or Remote Config, if used in the Game build
• Unity services — if used for Game operation, diagnostics, or platform-related functionality
• CAS.AI mediation and connected advertising network partners — if advertising is enabled in the relevant Game build
• Telegram — only when the player taps an external link that opens Telegram or a Telegram page outside the Game
These third parties may process data under their own privacy terms and policies when their SDKs, services, or platforms are used.
10. International Data Processing
Some third-party service providers, including providers such as Google, Unity, and certain advertising or analytics partners, may process data outside the Russian Federation or outside your country of residence, according to their own legal frameworks, transfer mechanisms, and privacy policies.
Where such services are used, cross-border processing may occur as part of providing authentication, diagnostics, analytics, infrastructure support, or advertising functionality.
11. Security
We use reasonable technical and organizational measures designed to protect personal data and service data, including measures such as transport security, access controls, service isolation, and operational monitoring.
However, no method of internet transmission, cloud storage, or electronic processing can be guaranteed to be completely secure. For that reason, we cannot promise absolute security.
12. External Links and Telegram
The Game may contain buttons or links that open external services, such as Telegram.
If you tap such a button, you leave the Game environment and interact with the external platform directly. We do not process your Telegram account data merely because the Game contains a Telegram link button. Any processing that happens after you open Telegram or another external service is governed by that external service's own privacy policy.
13. Children's Privacy
The Game is not intended for children under the age of 13 without parent or guardian involvement.
If you believe that a child under 13 has provided personal data improperly through the Game, please contact us at rimuru.dev@gmail.com. We will review the situation and take appropriate action where reasonably possible.
14. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect Game changes, backend changes, legal requirements, or service provider updates.
When we make changes, we will publish the updated version at the policy URL and update the Effective date shown at the top of this page. Material changes may also be communicated through an in-Game notice, store page update, or other reasonably appropriate method where practical.
15. Contact
If you have privacy questions, want to submit a data request, or need support related to Cloud Save data, contact:
rimuru.dev@gmail.com