Privacy policy

01

Guest play and local saves

The launch plan uses guest play without game account registration or sign-in. It does not integrate Google Play Games sign-in or Firebase Authentication, and does not obtain player identity information through those services. Google Play distribution and in-app purchases remain part of the plan. Using an account with the store or payment service is separate from game account sign-in.

Progress is saved locally on your current device. The game does not use Google Play Saved Games and does not provide in-game cloud synchronization or cross-device progress recovery. Clearing app data, uninstalling, or changing devices may cause progress to be lost. The behavior of system backups and device transfers still needs verification; these are not progress recovery features provided by the game.

Guest play does not imply consent to optional analytics, crash reporting, or personalized advertising. Saving progress locally also does not mean advertising, analytics, diagnostic, or purchase services process no data over the network.

02

Usage analytics

We plan to use Google Analytics for Firebase to understand game usage and improve the experience. Relevant data includes app instance identifiers, device and app information, sessions, and feature-use events. Default service behavior may also include advertising identifiers, approximate location inferred from network information, and purchase events.

Game analytics is off by default. You can turn it on or off under Settings → Data sharing → Game analytics, and your choice is saved independently. When the service is enabled, it uses the saved choice. Enabling this option in a test version without a configured analytics service does not itself cause uploads. Turning analytics off stops future optional collection; it does not automatically erase past records.

03

Crash reports

We plan to use Firebase Crashlytics for crash and error reports to troubleshoot issues and improve stability. Relevant information includes crash or exception stack traces, runtime context, device and app information, and installation identifiers used to organize reports.

Crash reports are off by default and can be controlled independently under Settings → Data sharing → Crash reports. The current implementation states that disabling takes effect on the next launch; fully close and restart the game. Analytics and crash reporting do not replace each other. Disabling either does not affect basic gameplay or automatically delete past uploads. We do not intentionally write passwords or purchase tokens into diagnostic logs.

04

Advertising

The game plans to use Google AdMob for advertising. Depending on its configuration, the advertising SDK processes IP addresses, device or other identifiers, app and ad interactions, and diagnostic information to deliver and measure ads, operate the service, and prevent invalid traffic. IP addresses can be used to infer approximate location.

Once production advertising is configured, Google’s advertising privacy form will explain available choices where applicable. Settings → Ad privacy lets you adjust options the service requires us to provide. If none are available, the game indicates that no adjustment is currently needed. Refusing personalized advertising does not mean all ad requests stop processing data. Other forms of advertising depend on your choices, applicable requirements, and service configuration.

05

In-app purchases

The game offers optional paid products. Payments are planned to be handled by Google Play. Product identifiers, purchase tokens, transaction status, and related records needed for purchase verification and delivery are used to validate transactions, provide entitlements, and handle support.

The game does not independently collect your full payment card number, security code, or payment password. The payment provider handles payment information under its own policies.

06

Support and third-party services

When you contact us, we process the email address, issue description, and necessary attachments you choose to provide so we can reply and handle your request. Do not provide account passwords, verification codes, or complete payment card details.

We use necessary data only for the functions described. Information may be processed by providers of analytics, diagnostics, advertising, payments, or infrastructure. Where applicable, necessary disclosures may also be made to meet legal obligations or protect users and the service.

Third-party information:

• Google Privacy Policy: https://policies.google.com/privacy?hl=zh-CN
• Firebase privacy and security (analytics and crash reports): https://firebase.google.com/support/privacy
• Google advertising information: https://policies.google.com/technologies/ads?hl=zh-CN

These links supplement the service descriptions and do not replace our explanation of the game’s actual data practices. Providers may process information outside your region. We will take safeguards required by applicable rules.

07

Security and retention

We will limit access and retention according to the purpose of the data and take appropriate measures to protect it. Relevant Google SDKs encrypt their disclosed network transfers. Protection for the game’s own interfaces, support, and other processes must also be implemented individually.

Proposed retention arrangements are listed below. Confirmed arrangements will be stated before the official release:

• Local saves: stored on the current device until the user clears the relevant data. File locations, clearing methods, and system backup behavior will be verified before release.
• Analytics: the configurable user-level/event-level retention period is proposed to be set to two months. This does not cover standard aggregate reports, advertising records, or data held by other services.
• Crashlytics: Google currently states that crash stack traces, extracted minidump data, and related identifiers are kept for 90 days before removal from live and backup systems begins. This does not mean every copy is instantly deleted on day 90. This provider statement does not replace verification of the game’s actual service status and scope. Reference: https://firebase.google.com/support/privacy
• Support records: proposed to be kept for six months after the issue is resolved, followed by removal of unnecessary records.
• Purchase, anti-fraud, and dispute records: final arrangements will be specified before release.
• Backups: final arrangements will be specified before release.

08

Your choices and data deletion

You can request access to, correction of, or deletion of relevant personal data by emailing 362303935@qq.com. We will verify your identity where necessary and process requests under applicable requirements.

Local saves can be cleared through Android Settings → Apps → RPGCoin → Storage → Clear data / Clear storage. Menu names vary by device. Clearing only the cache does not clear progress. This also clears app settings and relevant locally stored state. Email requests do not remotely clear local files, and the game does not offer cloud save recovery.

Contact the developer through this game’s data deletion page, or generate, review, and send a request from Settings → Data & privacy. The email address is 362303935@qq.com. Opening a draft does not send an email or mean data has been deleted. Requests concern linkable and deletable analytics, diagnostic, support, and other personal data. Categories, purposes, and retention periods for transaction, security, or other records that must be kept will be explained. Clearing local saves or uninstalling does not automatically delete data already uploaded or processed by service providers.

A request relating to this game does not delete your Google account, your entire Play Games profile, or data from other games. Appropriate instructions will be provided for data managed through Google’s platforms.

Proposed handling targets: respond within seven days and complete ordinary requests within 30 days after verification, or sooner where applicable requirements demand it. Necessary retention or data that cannot be directly linked to you will be explained with the outcome and limitations.

09

Age requirements and minors

The game is intended for players aged 13 and above, not for children under 13. If your region sets a higher age for using the relevant services or independently consenting to data processing, we will follow that requirement. Guardian involvement or feature restrictions may be needed. Guest play does not establish that a player is an adult; age and data choices still require appropriate handling.

If we learn that a child under 13 or another user who does not meet applicable requirements has provided information that should not have been collected, we will review the situation, restrict the relevant processing, and take applicable actions such as deletion. Parents and guardians can contact 362303935@qq.com.

10

Policy updates

We will update this policy when services or data practices change and state the effective date. Significant changes will be communicated appropriately. Where renewed consent is needed, it will be obtained before the relevant processing begins.

11

This website and contact channels

Website pages do not contain the game’s advertising or Firebase analytics scripts. The email template is edited in your current browser page; this website does not automatically upload, save, or send it. The email button opens your own email app. After you send a message, your email provider and the developer’s mailbox handle it through their email services. The hosting provider may process access requests to deliver and secure the website, so this website should not be described as producing no network records.

12

Contact us

Game: RPGCoin (投币吧！勇士).

Developer display name: HappyPig.

Privacy and support email: 362303935@qq.com.