Hankan Studio ("the studio") processes information for the mobile game Cennet ("the game"), including accounts, progress backups, the combat power leaderboard, gameplay analytics and rewarded ads, as described below. Effective date: October 21, 2026.
You can play without signing in with Google or Apple. When server features are enabled and an internet connection is available, the game automatically creates a random account number and sends progress backups and gameplay analytics. Records linked to that number are managed as the same player's data even though it is not a real name. Linking Google or Apple is optional and lets you restore progress after reinstalling or changing devices.
| Information | Purpose | Kept for |
|---|---|---|
| Player equipment trades (game account number, owned item identifiers and frozen properties, seller-set gold prices, listing status and time, operation identifiers, transfer receipts and processing order) | Browsing, listing, buying and cancelling equipment, ownership checks and preventing duplicate delivery. Other players see only listed equipment properties, prices and status; owned item identifiers, account numbers and credentials are private | Active listings until sold, cancelled or account deletion; completed or cancelled listing history for 30 days. Personal receipts, operation identifiers and processing order until account deletion. Deletion removes your records and account links in the ownership registry while preserving other players' equipment and receipts. Item identifier markers without account links remain to prevent duplicate registration |
| Cennet combat power record (game account number, power, model revision, UTC monthly season, selected character, submission time and worn equipment models, slots, rarity, values, options, sets and enhancement levels) | The combat power leaderboard, personal rank and registered equipment inspection. Other players see your nickname, public code, power, character, submission time and that record's worn equipment. Storage, bag contents and unique owned item identifiers are not public | Model revisions 1–5 keep the latest record. Revision 6+ keeps the latest record per UTC monthly season and revision for 365 days; all are removed on account deletion |
| A randomly generated account number, hashes of authentication and recovery values, and account creation and access times | Authentication, progress backup and recovery, and linking leaderboard and analytics records | Until the account is deleted |
| Nickname (if you choose one) | Shown on the rankings | Until the account is deleted |
| Cennet telemetry (play time and version, departure, continuation, first loot, death and committed run outcome; difficulty, character, starting gear model, slot, rarity and reference value; region, enemy, combat duration and lost gear reference value; gold changes by committed action, balance and shared growth level; observed balance changes; request failure categories, fixed API routes, request methods, HTTP status codes and predefined server error and transport failure codes) | First-play drop-off, retention, difficulty, growth, currency and equipment analysis, and operational error monitoring | 180 days; removed immediately with account deletion |
| Cennet first-play time and version, and first departure, loot, return, second departure and first death times | Deduplicated first-play and retention statistics | Until the account is deleted |
| Latest reported Cennet gold balance, report time and version per account | Aggregate unspent gold and balances held by recently active or dormant accounts | One row per account, replaced by a newer report or removed on account deletion |
| Nickname reports (reporting account, target public code and nickname, reason and review status) | Reviewing leaderboard nickname reports and preventing abuse | 90 days; removed with the related account |
| Google or Apple account link (only if you choose to link: the provider and its user identifier) | Linking your existing game account and restoring it after reinstalling or changing phones | Until you disconnect the link or delete the account |
| Login request information (temporary request identifiers, proof hashes and encrypted authorization and restore preparation/completion values) | Preventing requests from being taken over, confirming sign-in and safely finishing a restore after a lost response | Requests are valid for 10 minutes. Expired data is deleted at the next cleanup, within 24 hours |
| Encrypted Apple authorization token (only if you link an Apple account) | Revoking the Apple connection when you disconnect it or delete your account | Until disconnection or account deletion. Failed revocations retain only encrypted revocation material for retries for up to 7 days; expired work is deleted at the next cleanup, within 24 hours |
| Disconnection check information (login provider, a hash of its user identifier and the disconnection time) | Preventing authentication requests started before disconnection or during Apple revocation from restoring the link | Valid for 10 minutes after disconnection or processing an Apple revocation request. Expired data is deleted at the next cleanup, within 24 hours |
| Game save backup | Restoring progress on a new phone with the recovery code or a linked account | Until the account is deleted |
| Existing purchase entitlements in progress backups (product IDs, grant verification hashes, ad-removal status and first offer-view time) | Preserving existing entitlements and progress across devices | With the backup until account deletion |
| Daily hashes derived from IP addresses and request counts | Limiting requests such as registration, recovery and reports | 2 days |
| Game version, build, device model and language sent to the feedback form, and submitted feedback and optional game nickname | Support, fixing bugs and improving the game | Feedback is kept until handled, with deletion available on request. The form provider's policy applies to its connection data |
Gameplay analytics includes sessions and exploration outcomes, equipment and gold changes, growth levels, request failure categories and diagnostic codes. Request diagnostics retain only predefined API routes and error codes; URL query values, authentication tokens, request or response bodies and arbitrary error messages are not recorded. Account-linked records help us understand first-play progress, return visits and game balance. We do not sell personal information or pass game account numbers, backups, combat power or gameplay analytics to the advertising SDK as user identifiers.
Nicknames on the rankings can be reported. Each ranking entry also carries a public code tied to the account, which is used to point at the player being reported; it cannot be used to work out anyone's account number or sign-in token. If three different players report a nickname within 7 days, every ranking shows it as a code like "#a1b2" until we have reviewed it.
We do not store your real name, email address, phone number or precise location for game accounts. Google and Apple account linking is optional; names and email addresses that may appear in a login token are neither used for account linking nor stored. Your nickname is whatever you choose. Google AdMob, which shows the ads, may estimate your approximate location from your IP address (see 2. Ads). All connections are encrypted (HTTPS).
The game uses Google AdMob for rewarded ads that you choose to watch. Google Mobile Ads SDK may collect IP addresses and estimated approximate location, device identifiers such as advertising IDs, ad impressions, views and clicks, app and ad interactions, crash logs and performance information such as launch time, hangs and energy usage. Uses include serving and measuring ads, analytics, advertising fraud prevention and SDK improvements. Google's retention and deletion follow the Google Privacy Policy. See Google's iOS SDK data disclosure for details.
On iOS, access to the advertising identifier (IDFA) requires system tracking authorization. You can play without allowing tracking. Ad personalization and availability depend on your region, consent and advertising settings. Where Ad privacy settings appears in game settings, you can change your consent choices. You can also change app tracking permissions in iOS system settings.
The advertising SDK's collection declaration includes third-party advertising, developer advertising or marketing, and analytics. Google's consent SDK (UMP) uses approximate location, interaction and performance information for consent functionality.
If you choose to link Google or Apple, the provider (Google LLC or Apple Inc.) processes login authentication. The app and server exchange authorization codes and login tokens with the provider to verify the connection. See the privacy policies of Google and Apple.
Cloudflare, Inc. (USA) provides Workers and D1 for our server and database. They process authentication, backups, leaderboard and analytics requests, and may process request metadata and errors for security and service diagnostics. The game database stores daily IP hashes rather than raw IP addresses for rate limits. Infrastructure connection data is handled under the Cloudflare Privacy Policy.
Send feedback in settings opens a Tally (tally.so) form. The form URL sends the game version, build, device model and language when opened; submitted feedback is stored by Tally. This URL does not include your game account number or authentication token. The Tally Privacy Policy applies to the form service.
The current Cennet iOS app has no in-app paid purchase feature. Existing entitlements in progress restored from another device are nevertheless included in subsequent progress backup uploads. We do not store payment card information.
You can disconnect a Google or Apple link in Settings → Account link. Your current game account, progress, existing purchases and recovery code remain. Link the sign-in again to restore your progress with it. Apple revocation requests are processed in a separate queue; if Apple is unavailable, they are retried for the period described below.
Deleting server records also deletes Google and Apple account links and login requests. Apple token revocation is requested; if Apple is unavailable, game account deletion still completes and only encrypted revocation material remains in a separate queue for retries for up to 7 days. This queue contains no game account number, progress or nickname. Expired work is deleted at the next cleanup, within 24 hours.
Confirming Settings → Account → Delete server records deletes your server account, nickname, progress backup, combat power, analytics events, first-play milestones, latest gold balance, your listings, trade receipts, processing order and ownership registry account links, reports you made or received, and existing purchase verification records. Local progress stays on the device; the deleted recovery code and server backup can no longer be used. Backup and gameplay analytics uploads for that account stop after deletion. You can delete the app to remove its local progress.
If you have already removed the game or cannot request deletion in the app, contact us below. We will explain how to verify ownership using your public account code or nickname to locate the account. Do not email authentication tokens, passwords or recovery codes. Statistics that cannot be linked to individuals, daily IP rate-limit hashes (2 days) and disconnection-check hashes (valid for 10 minutes, then cleaned within 24 hours) follow their own retention rules.
Deleting server records also deletes purchase verification, grant and offer records, so purchases can no longer be restored to that game account. Requests to delete Google Play payment records or refund a payment must be made separately through Google Play.
The game is not directed at children under 13, and we do not knowingly collect personal information from children.
Privacy questions: rhfu3697@gmail.com
If this policy changes, this page will show the new effective date.