PavoluneJRYS
简体中文

Data Deletion

Effective date:
2026-11-09
Published:
2026-11-09
Version:
2

Request deletion for this game

This is the deletion contact page for Pavolune, operated by JRYS. It identifies the game and explains how to request deletion even when you no longer have the app installed.

Game
Pavolune
Package name
com.jrys.pavolune
Operator
JRYS
Contact
renzhuo3823@gmail.com

No player account required

The operator declares that this game has no player account system. You can request deletion of analytics associated with an installation without creating an account. This is a game-data deletion request, rather than deletion of a non-existent player account.

How to submit your request

  1. Contact renzhuo3823@gmail.com or use the email button below. Identify the game as Pavolune, package com.jrys.pavolune. You can make the request without reinstalling the app.
  2. If available, include the installation ID displayed by the game and describe which data you want deleted. If you no longer have that ID, explain what information is available so the operator can help identify the relevant records. Do not send passwords or unrelated sensitive information.
  3. The operator may ask for proportionate information to verify that you are entitled to request deletion of the identified data. After verification, the operator processes the request and confirms the outcome or explains any applicable limitation.
Request deletion by email

What the analytics deletion covers

After the operator verifies an installation-level request, deletion covers the matching raw analytics events, installation/first-seen references and related identifiable analysis records. Affected derived results are removed or recalculated. A protected hashed suppression marker prevents old events from being replayed during its retention window.

This analytics process does not automatically delete unrelated game-save files, an external account or records held independently by another provider. Describe those items in your request so the operator can handle the relevant game systems and providers. Platform-only aggregate reports that cannot be linked to an installation are not falsely presented as installation-level records.

Verification, response and retention

The operator will respond through the contact channel, explain the expected timeframe and handle a verified request without undue delay, subject to applicable requirements. The response will confirm completion or explain what further verification is necessary. If a specific record must be retained for a legitimate applicable requirement, the operator will identify the affected data, reason and period when responding.

Raw analytics events use a rolling retention window of 90 days. Expiration follows UTC day boundaries and is applied by periodic processing after the cutoff; removal is not instantaneous at the exact end of that period.

A minimal first-seen reference can remain while the installation still has events inside that window, so an older installation is not incorrectly counted as a new one. References without retained events are cleaned up. Derived analytics are recalculated when the underlying records expire or are deleted; expired history is not represented as complete retained history.

After an installation-level deletion, a protected hashed suppression marker is retained for the configured 90-day window, with periodic expiry cleanup, to prevent old events for that installation from being replayed. It is not the original installation identifier.

Historical backups have a separate rotation lifecycle. Deleting live records does not immediately erase every backup. If a backup is restored, applicable deletion instructions must be reapplied before the affected records are used. Contact the operator about the backup lifecycle and any other specifically disclosed retention.

For purchase deduplication, protected keyed digests of the store transaction and product are retained after event expiration or installation deletion, so a restored purchase cannot become new revenue. The original transaction, product, amount and installation links are removed with the applicable facts; the remaining marker cannot retrieve purchase details.

Local actions and future collection

Turning analytics off stops future collection and clears pending local events. Clearing app data, resetting an installation ID or uninstalling does not itself delete records already uploaded. You can use this request pathway without reinstalling. If analytics is later enabled under a new installation identity, new activity may create new records.

Other game-specific handling

Version scope: the existing 0.2.0/build 2 does not include JianRong gameplay analytics. Version 0.3.0/build 3 uses JianRong Telemetry 0.4.0 to send a random installation ID, session ID, app/build context, event times, foreground engagement and actual round start/end activity to the JianRong production service. Where provided by that service, country is derived from coarse network information; the game does not request precise location or infer country from the device language. Analytics is on by default without a consent prompt. Players can turn it off in Age & privacy > Analytics. OFF is saved for later launches and clears pending local analytics; it does not delete server history. Contact the public support email with the Analytics ID for access or deletion requests. Best score, up to five recent scores, sound and privacy settings are stored on the device. There is no player account or in-app purchase. The audience is aged 16 and over. The skippable age/privacy selection is held in memory and is not identity verification. Google Mobile Ads and Google User Messaging Platform are bundled for interstitial advertising and regional advertising privacy choices. Advertising activation is disabled in 0.2.0 and in the initial analytics update. Bundling an SDK is not a promise of zero SDK processing. Advertising choices are separate from gameplay analytics. Google data practices are listed below.