Privacy Policy

Last updated: November 11, 2026

This Privacy Policy covers the Google Play Android version of 沉默大陆 (package com.legend.cm), its game services, support and policy pages. The operator is 沉默大陆, an individual developer (“we”). Other distribution channels may use different accounts, payments or SDKs and are outside this version-specific description.

1. Login and scope

The game uses its own accounts and passwords. Starting with Google Play version 1.0.23, the app uses Google Firebase Analytics to measure game usage and Meta App Events to measure ad performance. The game also processes account, device and progress data to provide the service.

In-app purchases are available in the Google Play version. When you make a purchase, we process transaction data as described below for verification, delivery, refunds and reconciliation.

2. Data and purposes

• Accounts and authentication: account names, passwords, and security questions and answers requested during registration or account recovery, for registration, authentication, recovery and security. The current registration screen does not require a linked email address or phone number.
• Gameplay and social data: servers, character names and identifiers, levels, equipment, items, currency, progress, transactions and actions; and information supplied through chat, friends or guild features. This supports saved progress, interaction, dispute handling and fair play. Names, rankings, chat and guild information may be visible to other players according to the feature.
• Devices and connections: Android version, manufacturer and model, app version, an identifier derived from Android ID, connection IP addresses, times and necessary technical logs, for compatibility, login, security and troubleshooting. Hashing an identifier does not make it impossible to associate with a device.
• Optional usage statistics. Google Firebase Analytics measures launches, engagement, registration, login, character creation, entry into the game and level-ups. Meta App Events measures installs, launches, completed registrations and Google Play purchases for ad attribution. Analytics may process an app-instance identifier, device and app versions, approximate region, event times and purchase information. Firebase game events may include character level and class. Meta's automatic purchase events may include product ID, amount, currency, purchase time and purchase token. Our custom events omit game account names, passwords, character names and chat content. The app disables advertising ID collection and sets Firebase consent for ad storage, ad user data and ad personalization to denied. Usage statistics are on by default. You can turn them off under Account & Privacy → Usage Statistics and continue playing. Turning statistics off stops logging new usage events and resets local Firebase analytics identifiers and cached data. Contact us to request deletion of data already processed.
• Transaction data: Google Play product IDs, order IDs, purchase tokens and purchase or refund status, with associated account, server and character identifiers. These support verification, delivery, duplicate prevention, refunds and reconciliation. Processed account and character identifiers are submitted to Google Play to verify ownership. Google handles payment instruments; we do not directly receive full payment-card numbers or payment passwords.
• Support and deletion requests: contact email, account or character identifiers, order IDs, descriptions and necessary evidence that you provide, for support, ownership verification, refunds or deletion. Do not send passwords, security-question answers or full card information.
• Policy-page access: the hosting server or CDN may process IP addresses, browser information, request times and access logs to serve and cache pages, protect services and diagnose faults. These static policy pages embed no advertising, analytics scripts or non-essential cookies.

3. Recipients and third-party services

We do not sell personal data. Data is provided only to the extent needed:

• Google Play / Google: for payment processing, verification, consumption confirmation and refunds. Google processes data it holds under its own policy: Google Privacy Policy.
• Google Firebase Analytics and Google Ads. When usage statistics are on, Google processes the Firebase analytics data described above. We have linked Google Analytics and Google Ads and enabled audience import and app metrics. Analytics or conversion information may be used to measure promotion performance according to applicable consent and Google product settings. See the Google Privacy Policy.
• Meta Platforms. When usage statistics are on, Meta receives the Meta App Events data described above for ad attribution and performance measurement. See the Meta Privacy Policy.
• Infrastructure providers: cloud hosting, CDN and email providers used for game services, payment interfaces, policy pages or support, to operate those services. We do not authorize independent marketing use of game account data.
• Other players: content made public or visible through characters, chat, guilds, rankings and similar features, within each feature’s visibility.
• Lawful requests and legitimate rights: necessary disclosures to respond to legally required requests or address security incidents, fraud and disputes.

Game, payment, analytics and page-hosting services may process data outside your region. Applicable requirements for cross-border processing apply. Contact us for details of the hosting services and processing regions used.

4. Local storage, retention and security

The app stores the latest account, login credentials and game settings on your device for convenient login. Clearing app data removes local copies, but does not delete the server account. Protect your account and device, especially on shared devices.

Account and progress data is retained while needed to operate the account. Technical logs are retained only while needed for troubleshooting or security. After ownership verification, deletion requests are normally processed within 30 calendar days; see Account and data deletion.

Minimum transaction, refund, fraud or unresolved-dispute records may be retained for a legally required period or while needed to resolve a dispute. They are deleted or irreversibly anonymized when that purpose and any legal retention period end. If retention applies, our response explains its reason, scope and applicable period. Residual backup data is removed through the normal backup replacement cycle and is not restored for ordinary use; disaster recovery is followed by reapplying completed deletions.

We use access controls and operational safeguards appropriate to the data. Existing account login, registration and password changes use payload encryption in the game's TCP protocol. Some other game messages are protocol-encoded without full encryption. The client communicates with the public payment backend over HTTPS. This does not represent that locally stored credentials are encrypted or promise absolute security or encryption of every transmission.

5. Choices and rights

Contact us to request access, correction or deletion, close your account, or withdraw consent where applicable. Ownership checks are limited to what the request requires and do not require your password. Stopping use or uninstalling does not delete the server account. The deletion web resource can be used without reinstalling the app.

6. Children and teens

The game is intended for users aged 13 or older. If local law requires a higher minimum age, that requirement applies. Users under 13 must not use the game or make purchases.

Users aged 13 to 17, and any other users who are minors under local law, must have a parent or other legal guardian review and agree to this policy and the Terms of Service, and use the service with their guardian's guidance. Minors must obtain their guardian's consent before making purchases.

If an account or data does not meet the applicable age requirements, we take appropriate restriction or deletion measures. Guardians may use the contact details on this page to request access, correction or deletion of related data.

7. Changes

This policy is updated when functionality or data handling changes. New purposes or changes requiring fresh consent will be notified appropriately, and required consent will be obtained. Continued use alone will not be treated as consent to new sensitive-data uses.

8. Contact