Stella AtelierJRYS
简体中文

Privacy Policy

Effective date:
2026-11-10
Published:
2026-11-10
Version:
1

1. Scope and operator

This policy describes JRYS’s handling of information for Stella Atelier. It applies to the game identified below.

Game
Stella Atelier
Package name
com.xingyugames.stellaatelier
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:

CategoryInformation and use
Installation and session identifiersRandom 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 contextApp 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 activityFirst 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 countryA 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 rewardsWhere 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.

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.

Service providers and sharing

The operator and the providers used to host, operate and protect its backend can process information needed for those services. The game-specific third-party services declared by the operator are listed below, with their own notices. Their practices are distinct from the game analytics described here.

ServicePurposeData described by the operatorPrivacy notice
Google AdMob and User Messaging PlatformOptional rewarded advertising, ad measurement, fraud prevention and Google consent/privacy messages.Google may process IP-derived general location, product interactions, diagnostics and device/account identifiers (including advertising/app-set identifiers where applicable), as described in its SDK disclosures and user privacy choices.Read provider notice

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

Progress and settings are stored on your device; the game has no player account, purchase flow, user-photo upload or developer-operated cloud save. Android/device backup may include app data according to operating-system and device settings. Unified gameplay analytics is enabled by default and has a persistent Analytics switch. It sends per-game random installation, session and round identifiers, app/build/platform metadata, event times and sequence, foreground play duration, tutorial and gameplay outcomes, and actual advertising events. It does not send game artwork, full saves, contact lists, account credentials or precise GPS location. Turning Analytics off stops new analytics and clears its unsent queue; it does not delete data already accepted by the server. Network infrastructure receives IP addresses; server-side retention and deletion are governed by the published policy and support process. Google User Messaging Platform may contact Google to refresh consent status, and optional rewarded ads use Google Mobile Ads. Analytics choice and Google advertising/privacy choices are separate. Google may process IP-derived general location, product interactions, diagnostics and device/account identifiers, including advertising or app-set identifiers where applicable, for advertising, measurement and fraud prevention. Optional advertising requests require the player's actual choice and the Google consent state. Advertising SDK and consent processing are not disabled by the Analytics switch.

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.

  1. Contact renzhuo3823@gmail.com or use the email button below. Identify the game as Stella Atelier, package com.xingyugames.stellaatelier. 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

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.