Privacy Policy

PlayshipStudios Co., Ltd. (the "Company") processes personal data safely and in accordance with the Korean Personal Information Protection Act and other applicable laws. This Policy applies to the Company's website and game services and specifically describes the data practices of Play Sichuan.

1. Information We Process and How We Collect It

On the Play Sichuan overview and guide pages, website statistics record the page category, language, coarse arrival source (such as a search service, AI service, or direct visit), the platform of a download or play link, and event time. These events do not include full URLs, search terms, invitation codes, account identifiers, or IP addresses, and are not sent to a separate analytics provider. One coarse source label is kept in sessionStorage for navigation within the tab. These statistics count visits and link clicks, not installs or users. Hosting access and security logs are described separately below.

We process the following information as necessary to provide the Services. It may be provided by you or collected automatically through gameplay, platform SDKs, and server communications. The information actually processed depends on your platform and the features you use.

• Account and authentication data: Company-issued user UUID, login provider (toss/google/apple/guest), Toss userKey, Google or Apple account identifier (providerSubject), guest identifier, nickname, authentication token, and token expiry data
• Data processed temporarily during social sign-in: Google profile name and Google or Apple email address and email verification status. We inspect these fields in the identity token for verification and initial nickname generation, but do not store the email address in our game database.
• Game progress and virtual assets: coins, hint, shuffle and wand balances, owned and equipped skins, ad-free status, tutorial reward status, first purchase and starter pack timestamps, check-in dates, streaks and rewards, and rewarded-ad claim dates and counts
• Gameplay and ranking data: difficulty, best score and play time, games played and cleared, time-attack score and season, leaderboard entries, battle rating, match ID, opponent user ID, board seed, both players' scores, times and clear status, result, RP change, and whether a battle was a friend, random, or Ghost match
• Human replay data: server-validated tile matches, item uses and shuffle sequence with action timestamps from Human vs Human battles; board seed and configuration; final score and time; rating band; and a pseudonymous key used to honor deletion requests. Validated records may be used in Ghost matches for other players without exposing the original player's nickname or direct account identifier.
• Reports, blocks, and moderation-review data: internal identifiers of the reporting and reported users; nickname as displayed when reported; source (Human battle or leaderboard); reason (inappropriate nickname, cheating, or other); the 1–200-character details entered for an other reason; whether blocking was selected; status; and review time. To verify context, we may also process the Human-battle match ID or leaderboard kind, score, entry ID, mode, season, and a pseudonymous incident key used to prevent duplicate reports.
• Block-relationship identifiers: internal identifier of the blocking user, current identifier of the blocked user, and an irreversible HMAC hash derived from the blocked account's sign-in provider identifier. The original sign-in identifier cannot be recovered from the hash. We use it to preserve random Human-match blocking after a guest account is upgraded to Apple or Google or the same social account signs up again.
• Purchase data: order ID, product ID, payment platform, amount and currency, raw receipt or signed receipt data, Google Play purchaseToken, Apple transactionId, purchase, refund and acknowledgment status, and processing timestamps. We do not directly collect or store payment card or bank-account details.
• Apple refund-review data (optional): current consent status and opt-in timestamp for sharing purchase usage information with Apple. Only when you separately opt in, this may also include the transactionId, product ID, delivery status, whether sample content was provided, and usage information we can verifiably attribute to the purchase
• App analytics: depending on the platform, internal user ID or Toss userKey, Firebase app-instance ID and similar installation identifiers, and app-launch and session data. Where supported by the platform SDK, this may also include screens viewed, mode and difficulty choices, game outcomes and score buckets, item and skin use, ad and purchase events, time spent in the background, sharing, and review-request events
• Notification and device/app activity data (optional): when you allow notifications on Android or iOS, FCM registration token, Firebase installation ID, platform, notification-permission status, locale, time zone, app version, token registration, refresh and disable times, and most recent app-open time. We also process notification delivery ID, recipient internal user ID, campaign ID and target date, title, body and destination screen, delivery, failure and open status and timestamps, provider message ID, and failure reason to prevent duplicate sends and measure delivery.
• Advertising and device data: advertising identifier (Android AAID or iOS IDFA, depending on device settings and consent), app set ID and other device or app identifiers, coarse location inferred from IP address, app launches, taps, video views, ad views, clicks and rewards, and ad SDK performance and diagnostics
• Error and technical data: Firebase installation ID, Crashlytics installation UUID, internal user ID, app version and bundle ID, device model, OS, CPU, memory and storage information, crash or abnormal-termination time, error message, and stack trace
• Access and security logs: IP address, request time, HTTP method and API path, response status and duration, request ID, platform, authentication, App Check, and abuse-detection records
• Support inquiries: name, email address, message, and response history that you provide when contacting us by email

Your nickname, score, rating, equipped skin, and rank may be visible on leaderboards or to battle opponents. Do not include your real name, contact details, or other unnecessary personal information in your nickname.

2. Purposes of Processing

• Creating and authenticating accounts and linking platforms
• Saving progress and delivering assets, rewards, rankings, and battles
• Live matchmaking, Ghost matches using Human replays, replay validation, and anti-cheat
• Receiving and reviewing inappropriate-nickname and cheating reports, preventing duplicate or abusive reports, handling enforcement and appeals, and preventing blocked users from being randomly matched again
• Purchase verification, fulfillment, refunds, and dispute handling
• Sharing purchase usage information to assist Apple with refund reviews when you have separately opted in
• Rewarded ads, consent management, measurement, and ad-fraud prevention
• Usage analytics, quality improvement, diagnostics, and security
• Sending return reminders you have allowed, managing tokens and permissions, preventing duplicate sends, and measuring delivery, opens, and failures
• Support, legal compliance, and handling privacy requests

3. Retention

• Account, progress, ranking, and battle data: until account deletion or fulfillment of the processing purpose
• Human replays: until account deletion, a verified deletion request, or fulfillment of the operational purpose
• Report and moderation-review ledger: until the purposes of review, enforcement, appeals, legal disputes, and service safety are fulfilled. If either user deletes an account, we replace the active account link with a pseudonymous deleted-account tombstone and retain the reported nickname, reason, details, and verified context evidence with restricted access only as long as needed for those purposes, then delete it.
• Block relationship and irreversible identity hash: until the blocking user deletes the account or the operational purpose of the block ends. Deletion or re-registration by the blocked user alone does not end the random Human-rematching prevention purpose, so we may remove the current account link and retain the irreversible hash.
• Notification device and delivery ledger: until account deletion. We disable a token from future sends when notification permission is withdrawn, the user logs out, or the token is invalid, and delete device registrations and delivery/open records when the account is deleted.
• Purchase, contract, cancellation, payment, and delivery records: five years from the transaction. After account deletion, these are separated from the regular account and linked to a substitute identifier for legally required retention.
• Consumer complaint or dispute records: three years after resolution
• Consent to share Apple refund-review information: the current opt-in timestamp is retained until you withdraw consent or delete your account, and is deleted upon withdrawal
• Server operational logs: 14 days. IP-based rate-limit records expire with the applicable limit window and are retained for no more than one hour.
• Firebase Crashlytics data: Google begins deletion after 90 days under its published policy
• Google Analytics user- and event-level data: up to 14 months under the configured retention setting. Aggregated statistics that do not directly identify a person may be retained longer.
• Ad SDK data: according to your consent choices, device settings, and Google's applicable policies

We may restrict and retain information for a longer period when required by law or necessary for an investigation or dispute. Data deleted from active systems is removed as encrypted database backups rotate, within up to seven days.

4. Service Providers, External Services, and International Transfers

We use the services below to provide the Services. Depending on the contract and feature, a provider may process data as our service provider or as an independent controller.

• Amazon Web Services, Inc. / AWS Korea: ECS, RDS, ElastiCache, and CloudWatch for hosting, databases, cache, and logs. Game-server customer data is stored in the Seoul, Republic of Korea region (ap-northeast-2).
• Google LLC: Google Sign-In, Google Play Billing and receipt verification, Firebase App Check, Google Analytics for Firebase, Firebase Crashlytics, Firebase Cloud Messaging, and Google AdMob. Account authentication data, purchase tokens, FCM registration token, Firebase installation ID, notification recipient internal user ID, notification payload including title, body, delivery ID and campaign ID, app, installation and device identifiers, usage, advertising, and diagnostic data may be transferred over the network when a feature is used and processed in the United States and countries where Google or its processors operate facilities, for the periods in Section 3 or under Google's policies. See the Google Privacy Policy and Firebase Privacy and Security documentation.
• Apple Inc.: Sign in with Apple, StoreKit, App Store Server API, and Apple Push Notification service (APNs) for authentication, purchases, refunds, and iOS remote-notification delivery. Apple account identifier, identity token, email-verification data, receipt, transactionId, APNs device token, notification payload, and delivery information may be transferred over the network when a feature is used and processed in the United States and countries where Apple or its processors operate facilities, under Apple's retention policies. Only if you separately opt in as described in Section 6 may we provide Apple with the transactionId, product ID, delivery status, whether sample content was provided, and usage information we can verifiably attribute to that purchase to assist Apple with a refund review. See the Apple Privacy Policy.
• Viva Republica Inc. (Toss): Apps-in-Toss account identification, Game Center, Analytics, and Apps-in-Toss purchases. Toss userKey, nickname, score, and app-usage and purchase events may be processed where applicable. See the Toss Privacy Policy.

If you do not want an international transfer, you may avoid the relevant optional feature or contact Support to request restriction or deletion. Refusing processing required for account authentication or payment verification may make that feature unavailable.

5. Advertising and Privacy Choices

The Google Play and App Store versions of Play Sichuan may use Google AdMob for rewarded ads. For advertising, analytics, and fraud prevention, the Google Mobile Ads SDK may automatically process IP address; product interactions such as app launches, taps and video views; SDK performance and diagnostic data; and device or account identifiers such as advertising ID and app set ID.

Where consent is required, we present the Google UMP consent interface before loading ads and request an ad only when the SDK reports that it is permitted. You can change your choice through "Ad privacy choices" in game settings, when available, or delete or reset the advertising identifier in device settings.

6. Sharing Purchase Usage Information for Apple Refund Reviews (Optional)

If a refund is requested on iOS, and only when you have separately opted in, we may provide Apple with the transaction ID, product ID, delivery status, whether sample content was provided, and usage information that we can verifiably attribute to that purchase. This information is used only to assist Apple in reviewing the refund request.

Opting out does not affect purchases, restoration, or gameplay, and the setting is off by default. You can opt in or withdraw consent at any time under "Settings → Legal & privacy → Share purchase usage with Apple." We do not provide this information for requests received after consent is withdrawn. This choice is separate from ad privacy choices and App Tracking Transparency consent.

7. On-Device Storage

For continuity, the app stores authentication tokens, a local copy of nickname and game state, BGM, SFX, haptic and language preferences, tutorial status, and limited local progress in secure storage, localStorage, or similar technology. On notification-enabled devices, it may also store a limited queue used to retry unsent notification-open and token-disable operations safely as the original account. You can remove it by clearing app data or uninstalling the app, and the app clears related local data after account deletion succeeds. The website may use cookies necessary for language selection and basic operation.

8. Deletion

We delete personal data without undue delay when retention expires or the purpose is fulfilled. Electronic records are deleted using methods designed to prevent recovery, and paper records, if any, are shredded or incinerated. Purchase records retained by law are segregated from normal account data and access-restricted.

9. Your Rights and Rights of Guardians

You may request access, portability, correction, deletion, restriction, or withdrawal of consent. In game settings, you can change your nickname and delete your account, and manage ad privacy choices on supported platforms. You can withdraw notification permission in device settings. To ask about or appeal a report outcome, or to exercise your rights regarding Human replays, block relationships, or other information about you, contact Support at help@playshipstudios.com. We will verify your identity and respond within the period required by applicable law.

We do not currently collect dates of birth or legal guardian information, and Play Sichuan is not designed primarily for children under 14. Before introducing a feature that requires legal guardian consent to process a child's personal data, we will provide a separate consent and verification process. The advertising features in Play Sichuan are not configured as child-directed.

10. Security

We use safeguards including encryption in transit, encryption of databases and backups, least-privilege access, masking of tokens, receipts, and other sensitive logs, network access controls, abnormal request limiting, and periodic vulnerability review.

11. EEA and UK Users

We process data as necessary to perform our contract by providing the game, account, and payment features; to comply with legal obligations; for legitimate interests in service security and quality; or with consent where required. You may exercise rights of access, correction, deletion, portability, restriction, objection, and withdrawal of consent, and lodge a complaint with your supervisory authority. We use applicable contractual safeguards, including standard contractual clauses where required, for international transfers.

12. U.S. State Privacy Rights

Residents of California and other applicable states may have rights to notice of the categories, sources, purposes, and recipients of personal information; access, correction, deletion, and a copy; opt-out of sale, sharing, or targeted advertising; and non-discrimination for exercising those rights. We do not sell personal information for money. However, sharing advertising identifiers and ad events with advertising providers such as AdMob may be considered a "sale," "sharing," or targeted advertising under certain laws.

Exercise an opt-out through the ad privacy interface or device settings, or email Support with "Do Not Sell or Share My Personal Information."

13. Privacy Officer

• Name: Minseong Kim
• Title: Director
• Email: nova@playshipstudios.com

14. Remedies

For privacy complaints in Korea, you may contact the KISA Privacy Infringement Report Center (118), the Personal Information Dispute Mediation Committee (1833-6972), or the Personal Information Protection Commission.

15. Changes and Effective Date

We will announce changes and their effective date on the website or in the game. This Policy is effective from 2026-10-06.