Privacy Policy
1. Scope and operator
This policy describes JRYS’s handling of information for Mallow Tether. It applies to the game identified below.
- Game
- Mallow Tether
- Package name
com.jrys.mallowtether- Operator
- JRYS
- Contact
- renzhuo3823@gmail.com
2. Analytics information and purposes
The game uses analytics to understand foreground use, gameplay flow, retention and data quality. The collection mode and player controls are described in the next section. Depending on the features actually used, the analytics records can include:
| Category | Information and use |
|---|---|
| Installation and session identifiers | Random installation ID within this game, session ID, event ID and sequence. They support session grouping, deduplication and analysis; the installation ID is not a name, an account or a count of physical people. |
| App and build context | App identifier, production environment, app version, build number, analytics SDK and event-schema version. Any additional platform or device data handled by the game or other SDKs is described in the operator’s additional practices or provider notices. |
| Gameplay and activity | First opening while analytics is enabled, foreground sessions, positive foreground duration increments, event occurrence/receipt times, and applicable tutorial and round identifiers, modes, levels, outcomes and active durations. These help understand use, retention and gameplay flow. |
| First-known network country | A coarse ISO country code supplied by the hosting edge for an enabled analytics request. It is retained as the installation’s first-known network country for comparison; VPNs and proxies can affect it. The analytics database does not store an IP address, city or coordinates for this purpose. |
| Advertising and actual rewards | Where available from real callbacks: ad request/load results, errors, format and placement, impression/request associations, revenue in integer micro-units with currency, precision and source, and the identifier/type/quantity of a reward actually granted by the game. A displayed ad or a reward is not itself proof of revenue. |
The analytics protocol uses an event-specific field allowlist. Any registered game-specific event and any information collected outside that protocol must also be reflected in the operator’s additional practices below.
3. Collection mode, local queues and your choices
Gameplay analytics is enabled by default when the game starts, without first asking for analysis consent. This default is recorded as consent not requested, not as a player consent decision. You can turn analytics off in the game settings; the game preserves that choice across restarts. Advertising permissions are handled separately and are not enabled by the analytics default.
While analytics is enabled, events can temporarily remain in a bounded on-device queue for offline retry. Turning analytics off stops further collection and clears pending local events. Actions while collection is off are not buffered for later upload. A request already committed by the server cannot be recalled by that local action; use the deletion process for information already uploaded.
Resetting local analytics state, clearing app data or uninstalling the game does not by itself delete previously uploaded information. See Data Deletion for a request pathway.
4. Advertising services
The operator declares that this game includes advertising. The game’s analytics of ad callbacks is distinct from data processed by advertising SDKs. Depending on the integrated service, version and configuration, an advertising provider may process network/device identifiers, interactions and diagnostics under its own consent settings and notice. Review the declared providers below for the actual game-specific handling.
Network processing and security
Analytics is sent over HTTPS and access to the backend is restricted. Network connections necessarily expose connection information such as an IP address to receiving servers and network/hosting providers. Access or security logs can be processed under those infrastructure settings; an IP address not being an analytics event field does not mean it is absent from all infrastructure processing.
The operator’s additional practices below describe game-specific handling beyond these analytics facts. Questions about infrastructure logs, storage location or access should be directed to the operator.
Retention and deletion
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.
Additional data practices declared by the operator
Game progress, stage results and preferences are saved on the device; gameplay does not upload save files or provide a game account, chat or in-app purchases. In version 1.0.1 (4) and later, gameplay analytics is enabled by default to understand use and improve the game. Earlier versions collect gameplay analytics only after a player enables it. A player who has already turned analytics off keeps that choice when updating. Players can turn gameplay analytics off or on in Settings at any time. Collection includes a random per-installation identifier, session identifiers, app version and build, event times, foreground engagement, page and button actions, and actual stage starts and results. It does not collect names, email addresses, precise location, or saved progress files, and gameplay analytics is not used to personalize advertising. Turning analytics off stops new game analytics collection and clears pending local analytics; server-side deletion requests use the contact email. From version 1.0.3 (6), the Android game may show occasional full-screen Google AdMob ads after a stage for players who indicate they are 18 or older, when Google’s advertising privacy requirements allow an ad request. Earlier Android releases do not show production ads. Where available, advertising privacy choices can be managed in Settings. Google Mobile Ads Unity 11.6.0 / Android 25.5.0 and Google User Messaging Platform remain present and may process IP-derived approximate location, device or advertising identifiers, app interactions and diagnostics under their own policies and applicable settings, independently of the game-controlled ad request gate. Turning game analytics off does not itself stop Google SDK processing. No precise-location permission is requested. Advertising privacy choices and gameplay analytics are managed separately.
Requests and contact
For privacy questions, or requests about access, correction or deletion, contact renzhuo3823@gmail.com. Available rights, verification and any required exceptions depend on the circumstances and applicable requirements. The request pathway below is also available after uninstalling the game.
- Contact renzhuo3823@gmail.com or use the email button below. Identify the game as Mallow Tether, package com.jrys.mallowtether. You can make the request without reinstalling the app.
- 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.
- 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.
Updates to this policy
The operator can publish an updated notice when the game’s practices change. The effective date and version at the top identify this published notice. Any choice or consent required for changed processing must be handled in the game separately from merely publishing a notice.