What personal data Snake Temple 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 Snake Temple (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) | When you first start (as a guest or with Google) | Account identity · progress save |
| Google account identifier | Only when you continue with Google or link a Google account in Settings | Sign-in, and continuing the same account on another device (identifier issued by Google) |
| Email address | Only when you continue with Google or link a Google account in Settings | Showing the linked account in Settings · verifying you when you contact us about the account |
| Purchase history and receipts (order number, product, price, time of purchase) | On in-app purchase | Confirming grants · first-purchase bonus · refund and double-grant disputes · recovering what was granted for refunded payments |
| Advertising ID (AAID) | When watching a rewarded ad | Ad delivery · fraud prevention (processed by Google AdMob) |
| Gameplay data (currency, items, skins, stage progress, battle results, coin pusher records) | During play | Progress save · reward grants · fraud prevention · balancing |
| Battle input records (steering and tap inputs) | When a battle ends — kept only for some battles (flagged or randomly sampled) | Detecting cheating by replaying the battle on the server |
| App version, operating system type and a connection identifier (a random value created each time the app starts) | When the app communicates with our server | Preventing one account from being used on two devices at once · version compatibility · fault analysis |
| Mailbox messages — type, content, any attached reward (gold, Snake Coins), when sent and until when it can be claimed, when claimed | When the game sends you mail (currently friend-invite notices and invite rewards) | Delivering notices and rewards, and making sure the same reward is never granted twice |
| Your friend invite code (8 capital letters and digits) | When you first use the invite feature (Mailbox › Invite Friends — generated at random by our server) | Letting you invite friends, and finding who invited a friend from the code they enter |
| Invite relationships — who started with whose code; how the code was entered (typed in, or from the Android install referrer) and when; when the invited player reached stages 2 and 5 of Snake Battle; whether the invited player linked a Google account, and that Google account identifier converted into an irreversible value (a hash); whether the device check (Google Play Integrity) passed when a reward was created | When a friend starts with your code or you start with a friend's code, and afterwards as the invited player progresses | Deciding and granting invite rewards · showing on the inviter's Invite Friends tab only a number, the join date, the stage reached and whether an account is linked — never a name · preventing the same Google account from collecting invite rewards again |
| Invite reward records — when a reward mail was created and claimed, and the Snake Coins granted (also recorded in the currency ledger) | When a player joined through an invite reaches stage 2 or 5, and when the reward is claimed | Granting each invite reward only once · handling disputes about grants · fraud prevention |
| Android install referrer (Google Play Install Referrer) — only the friend invite code in it is sent to our server | Once, when you first open the Android app installed from Google Play | Entering a friend's invite code automatically when you installed through an invite link (not used for advertising or marketing) |
| In-app support messages (Contact Us) — your message (up to 1,000 characters) and when it was sent; the account identifier, app version and operating system type (Android/iOS) stored with it; our answer and when it was given; when you read the answer | Only when you send a message from Settings → Contact Us in the app (or Contact Us on the account suspension or restriction notice) — optional | Customer support — reading and answering your message, and showing the answer under My Questions in the app (not used for advertising, analytics or marketing) |
| Inquiry content and contact | When you contact us by email | Handling and replying |
A support message may contain personal data you write in it yourself, such as an order number or email address. Answers are shown only under My Questions in the app; we do not ask for an email address or other contact details to deliver them.
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 |
|---|---|---|
| Account identifiers (sign-in token, linked Google account, email address) | While the agreement is in force (destroyed immediately on account deletion) | Until the purpose is achieved |
| Gameplay records (currency, skins and progress, currency ledger, battle and coin pusher records, sanction history) | 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 |
| Battle input records (kept for some battles only) | Deleted as soon as a review passes · 100 days if cheating is found · 30 days if the battle cannot be reviewed | Cheat review · handling objections |
| Friend invite records (your invite code, invite relationships, invite reward records, and the hash of the invited player's Google account identifier) | While the agreement is in force · 1 year after account deletion | Deciding and granting invite rewards, preventing the same Google account from being rewarded twice (fraud prevention), handling disputes about reward grants |
| Mailbox (mail sent by the system) | Deleted automatically 30 days after it is claimed or expires (mail can be claimed for 30 days after it is sent; the same applies to mail voided because of fraud) · reward mail that requires a linked account is kept until you link one, then gets a new 30-day deadline from the day you link · after account deletion, destroyed together with the other records within 1 year | Delivering notices and rewards, preventing a reward from being granted twice |
| In-app support messages (the message, the information stored with it, and our answer) | While the agreement is in force · after account deletion, until 1 year after deletion or 3 years after the answer (or the message, if unanswered), whichever is later | Customer support (showing past messages and answers under My Questions) · records of consumer complaints and disputes (Act on Consumer Protection in Electronic Commerce) |
| 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 app has no way to delete individual support messages. When the account is deleted (Home → Settings → Delete account, or as described in Delete Account), they are destroyed automatically once the period in the table above has passed.
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 API server (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 API server (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 and does not collect notification tokens.
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.