PLAYUS Privacy Policy
Draft — to be finalized after legal review; contents may change.
PLAYUS processes only the minimum information needed to run the games and data rewards. We do not collect real names; an email address from social login is used only for support and identity checks (never to find or merge accounts), and phone numbers are stored only as one-way hashes.
1. Information we process and why
| Category | Information | Purpose |
|---|---|---|
| Guest play | Device identifier (a random ID created by the browser or app) | Keep game and reward records without signing in |
| Phone verification (existing phone accounts, data coupon exchange check) | A one-way hash (HMAC) of your phone number and a masked number (e.g. 010-****-1234). The original number is not stored | Identity check, one account per person, data coupon exchange, preventing repeated welcome bonuses |
| Toss login (Toss users) | Anonymous key and user key (userKey) provided by Toss | Toss mini app sign-in and account linking |
| Social login (Kakao, NAVER, Apple, Google, LINE — web and app) | Provider account identifier (Kakao member number, NAVER ID, Apple/Google/LINE sub), email and whether it is verified (when the provider shares it and you agree), link and last-use times, a refresh token used only to revoke access when you disconnect or delete your account (Apple web, NAVER; stored encrypted). We do not receive names, profile photos or friend lists | Sign-in and account linking, identity checks for support. Accounts are never merged automatically by email |
| Profile | Nickname, chosen character, ranking and live feed display settings | Rankings, Together and live feed |
| Service records | Play and round records, data (MB) and heart wallet and ledger, data coupon exchange and payment records, inbox | Rewards, exchanges and payments; detecting abuse |
| Notifications | Push device tokens (FCM, web push subscriptions), consent and withdrawal history for promotional and night-time notifications | Sending notifications, proof of consent |
| Inquiries | Reply contact (email or mobile number) and message | Answering inquiries |
| Connection data | IP address, country, app version and device type (browser, OS), sign-up source (referrer, UTM) | Security and abuse prevention, country rankings, service improvement |
| Analytics and errors | Screen and feature usage events, error (crash) reports | Improving service quality |
2. Retention and deletion
When you delete your account, your account information and records are deleted right away, except for the following.
- Data coupon exchange and payment records: kept for the period required by law in a form that does not identify you
- Phone and device hashes (cannot be reversed): kept for 30 days after deletion to prevent repeated sign-up bonuses, then deleted
- Inbox messages: deleted 90 days after they are received
- IP addresses: the original is deleted after 90 days; only a one-way hash and the country remain
- Social login links (identifier, email, token): deleted as soon as you disconnect them or delete your account, and we ask the provider to unlink or revoke access (Kakao, Apple, NAVER).
- Data coupon codes already issued remain usable on Triptok after you leave.
3. Processors and third-party services
We use the services below to provide PLAYUS. Some may process data outside Korea (e.g. in the United States).
| Company | Service | Information |
|---|---|---|
| Google LLC | Firebase (Cloud Messaging, Analytics), AdMob, AdSense, H5 Games Ads | Push device tokens, analytics events, advertising ID (with consent) |
| NAVER Cloud | SENS (SMS), Outbound Mailer (email) | Mobile number or email that receives verification texts and inquiry replies |
| Viva Republica (Toss) | Apps in Toss login, notifications and payments | Toss user key, notification and payment data |
| Triptok | Data coupon issuance | Exchange request data (public ID reference, amount). Phone numbers and names are not shared |
| Anthropic | Claude API (operator tools for sorting inquiries and reviews) | Inquiry and review text with contact details and other personal data masked |
| Apple / Google | Social login (Sign in with Apple, Google sign-in), app push delivery | Account identifier (sub), email (with consent), device tokens |
| Kakao | Kakao Login | Kakao member number, email (with consent) |
| NAVER | NAVER Login | NAVER member identifier, email (with consent) |
| LY Corporation (LINE) | LINE Login | LINE user identifier (sub), email (when permitted and agreed) |
4. Ads and analytics
- To keep rewards free, we show Google AdMob (app), AdSense and H5 Games Ads (web).
- Your advertising ID is used for personalized ads only with consent — App Tracking Transparency on iOS, and the consent message (UMP) in the EEA and similar regions. Otherwise non-personalized ads are shown.
- Usage statistics and error reports are collected by the PLAYUS server and Google Firebase Analytics.
5. Your rights
-
My info: view and change your nickname, character and records in Settings → My info.
-
Delete account: delete your account right away in Settings → Delete account. See the account deletion guide for details.
-
Withdraw notification consent: turn off promotional and night-time notifications any time in Settings, or revoke notification permission in your device settings.
-
For access, correction or restriction requests, or deletion when you cannot use the app, send a 1:1 inquiry through support.
6. Security measures
- Phone numbers, device identifiers and IP addresses are compared using keyed one-way hashes, and only masked values are shown in the app and operator tools.
- Only text with contact details and other personal data masked is sent to the operator AI tools.
- Sign-in tokens are revoked immediately when an account is deleted or suspended.
7. Contact
For privacy questions, send a 1:1 inquiry through support. We will reply to the contact you leave.
8. Changes to this policy
When we change this policy, we announce the changes and the effective date in the Service and on this page at least 7 days in advance (30 days for changes that significantly affect your rights). Previous versions are available under "Previous versions" at the bottom of this page.
Previous versions
- Version 1 · Effective 2026-10-05 · Current — First version
