What personal data Shadow Shuriken processes, and how it is used, kept and destroyed.
A17s (the "Company") complies with the Korean Personal Information Protection Act and related law. This policy applies to Shadow Shuriken (the "Service").
The Service can be started without any sign-up procedure. Identity data such as name, date of birth, phone number and address is not collected.
| Item | When collected | Purpose |
|---|---|---|
| Account identifier (a random value issued by our server) and sign-in token (stored on our server only as an irreversible value) | When you first start (New game or Continue with Google) | Account identity · progress save |
| Google account identifier | Only when you choose Continue with Google (on the title screen or in Settings) | Sign-in, and continuing the same account after changing devices or reinstalling (identifier issued by Google) |
| Email address (of the linked Google account) | Only when you choose Continue with Google (on the title screen or in Settings) | Showing the linked account in Settings (partly masked) · verifying you when you contact us about the account or request deletion on the web |
| Purchase history and receipts (order number, product, price, time of purchase, refund outcome) | On in-app purchase | Confirming grants · first-purchase bonus · monthly pass grants · refund and double-grant disputes · recovering what was granted for refunded payments · tying the payment to this account (the purchase screen receives only an irreversible value derived from the account identifier) |
| Advertising ID (AAID) and app set ID, IP address (used to estimate approximate location), ad interactions and diagnostic information | When a rewarded ad is loaded and watched | Ad delivery · fraud prevention · ad measurement (collected and processed directly by Google AdMob) |
| Ad view and reward records (the reward request, Google's confirmation of the view and the ad transaction number, whether the reward was granted, impression revenue) | When watching a rewarded ad | Granting the reward (only after Google's signed confirmation of the view) · daily limit · fraud prevention · ad revenue totals |
| Gameplay data (currency, characters and their stars, shards, upgrades, stage progress, the ninja village, ninja mission points and chests, mailbox, claimed achievements, tutorial progress, run results, currency ledger, screen settings) | During play | Progress save · reward grants · fraud prevention · balancing |
| Run input records (movement and skill inputs) | When a run ends — kept only for some runs (flagged runs, high-value runs such as first clears, and random samples) | Detecting cheating by replaying the run on our server |
| App session identifier (a random value created each time the app starts) and the app's battle engine version | When the app communicates with our server | Preventing one account from being used on two devices at once · version compatibility |
| Device and app integrity results (Google Play Integrity verdicts — whether the app is the genuine Google Play version, whether the device is unmodified, licensing, and the app version, signing certificate and the device's Android version) | When the app starts | Fraud prevention (Google makes the verdict; runs from a launch that failed the check are reviewed) |
| Inquiry content and contact | When you contact us by email | Handling and replying (including verifying account deletion requests) |
The following is not collected:
Access times, device information and error logs may be generated and stored automatically during use.
Personal data is destroyed without delay once its purpose is achieved. The following is kept for the periods required by law.
| Data | Period | Basis |
|---|---|---|
| Sign-in tokens and the linked Google account (Google account identifier and email address) | While the agreement is in force · on account deletion the linked Google account is destroyed at once, and sign-in tokens are invalidated at once and destroyed 30 days later (only the 5 most recent tokens per account stay valid — older devices are signed out first) | Until the purpose is achieved |
| Gameplay records (currency, characters, progress, currency ledger, run records, ninja village, mailbox, claimed achievements, tutorial progress, sanction history, latest device check result) | While the agreement is in force | Until the purpose is achieved |
| Gameplay records remaining after account deletion (separated from the identifiers above) | 1 year after account deletion | Fraud prevention · payment disputes, including refunds that arrive after deletion |
| Run input records (kept for some runs only) | Deleted as soon as a review passes · 100 days on a mismatch or review error | Cheat review · handling objections |
| Ninja mission (time-slot event) points and chest grant records | 180 days | Granting rewards · recovering them when a run is found fraudulent |
| Finished mail in the mailbox (claimed, voided or expired) | 30 days from when it finished | Confirming mail reward grants · handling questions about grants |
| Service processing records (currency operation history, slow-request and error logs, device check records) | 30 days | Preventing a request from being processed twice · fault analysis · fraud prevention |
| Ad records that did not earn a reward (not watched to the end, refused, expired) | 30 days | Handling questions about ad rewards · fraud prevention |
| Rewarded ad records (ad transaction number, reward, time) | 1 year from creation (when the ad was watched) — destroyed after 1 year even while the account exists | Record that the reward was granted · handling questions about grants |
| Payment and receipt records, and refund and cancellation records | While the agreement is in force (first-purchase bonus, restoring purchases) · after account deletion, 5 years from the payment date (refund and cancellation records: from when they were processed) | Act on Consumer Protection in Electronic Commerce · refund disputes |
| Hash of the Google account identifier of an account deleted while banned | For the length of the restriction (until lifted, for a permanent restriction) | Fraud prevention (stopping a restricted user from starting over) |
| Records of staff actions such as web deletion requests (account number, action, request number, operator — no email address) | 5 years | Confirming what staff did · handling disputes |
| Guest account left behind after using Switch to that account (그 계정으로 바꾸기) | 60 days from the switch — then deleted in the same way as an account deletion (what remains afterwards follows the rows above) | Answering questions about the guest progress from before the switch |
| Guest accounts that never loaded the game after being created | Deleted 30 days after creation | Clearing out unused accounts |
| Account number and dates remaining after deletion (only the random account number and the dates it was created, deleted and cleared) | No time limit | Keeping the account slot that remaining payment and restriction records point to |
| Records of contracts and withdrawal of purchase | 5 years | Act on Consumer Protection in Electronic Commerce |
| Records of payment and supply of goods | 5 years | Act on Consumer Protection in Electronic Commerce |
| Records of consumer complaints and disputes | 3 years | Act on Consumer Protection in Electronic Commerce |
| Service access logs | 3 months | Protection of Communications Secrets Act |
Deleting an account does not delete payment and receipt records; they are kept for the statutory period above. They are also the only basis on which a refund or double-grant dispute can be resolved. Those records are stored separately from account identifiers.
The Company does not sell personal data or provide it for advertising purposes. Exceptions are limited to cases where the user has consented in advance, or where a law or a lawful request from an investigative authority requires it.
| Processor | Entrusted work |
|---|---|
| Google LLC (Google Play) | In-app purchase processing and receipt verification |
| Google LLC (AdMob) | Serving rewarded ads and preventing fraudulent views |
| The social login provider chosen by the user | Account linking and identity matching |
| Railway Corporation | Running the game server — API, batch jobs and replay inspection (Singapore region) |
| Supabase Pte. Ltd. | Running the game database and storing data (AWS Singapore region) |
Service data is stored and processed on cloud infrastructure in Singapore (Railway · Supabase). This is entrusted processing and storage needed to provide the Service to you, and involves the following transfers abroad.
| Recipient | Contact | Country | Purpose (entrusted work) |
|---|---|---|---|
| Railway Corporation | privacy@railway.com | Singapore | Running the game server — API, batch jobs and replay inspection (Singapore region) |
| Supabase Pte. Ltd. | privacy@supabase.com | Singapore | Running the game database and storing data (AWS Singapore region) |
The Service is not directed at children under 14; where the Company learns that a user is under 14, the data is destroyed without delay.
The Service offers rewarded ads. When an ad is watched, the advertising identifier (Android Advertising ID) is passed to the ad provider (Google AdMob) to serve the ad and prevent fraudulent views. Users can reset the advertising ID or opt out of personalised ads in their device settings (Android: Settings → Privacy → Ads).
The Service does not send push notifications from a server and does not collect notification tokens. Ninja village updates (construction finished, vault full) notifications are local notifications scheduled on the device itself; they contain no personal information and send nothing to our server. They can be turned off with Settings (설정) → Village notifications (마을 알림) in the app or in device settings.
Send inquiries to this address. We review them on business days and reply by email.
Users may seek help from the following bodies in Korea:
This English text is provided for convenience. In the event of any discrepancy, the Korean version prevails.