Privacy Policy

1. Scope and data minimization

• The source proposes minimal processing for gameplay, account and ownership verification, abuse prevention, inquiries, and opt-in crash reports. Claims that ads, ad identifiers, phone numbers, addresses, payment instruments, contacts, photos, and location are never processed require launch-build and server verification.

  Operational, code, or legal Gate

2. Data, purpose, retention, and basis

The source table lost its columns. No missing cell has been guessed; every unknown remains an explicit Gate.

• Store account identifier and ownership status — purpose: linkage and ownership verification; retention, legal basis, actual store, and response fields: [legal/operational review required].

  Operational, code, or legal Gate

• Game account ID and sanction history — purpose: identification and abuse prevention; retention, legal basis, storage schema, and access process: [review required].

  Operational, code, or legal Gate

• Device identifier and refresh-token hashes — a user-provided claim; hash inputs, algorithm, retention, deletion, and implementation are [code/security Gates].

  Operational, code, or legal Gate

• Opt-in crash reports — proposed fields are crash location, game version, content hash, run mode, OS/architecture, and a note up to 500 characters; recipient, retention, UI consent, and payload are [configuration Gates].

  Operational, code, or legal Gate

• Inquiry email — even if email is not a game-account field, sending an email processes the sender address, subject, message, and reply history. Mail provider, location, retention, and deletion remain unresolved.

  Operational, code, or legal Gate

• Portal locale preference — the current portal stores only samkingdom.locale in browser localStorage, not a cookie; users can delete it in their browser.

  Current repository evidence

3. Chat, connection IP, and logs

• The claim that each room keeps only the latest 50 chat messages in memory, applies a send-time filter, and discards them on room closure requires runtime verification. Database non-storage and transient memory processing are distinct.

  Review analysis · not legal advice

• A claim that IP is absent from the game database does not address Nginx, WAF, rate-limit, or security logs. This repository contains only planned OCI/Nginx/WAF documentation, not production log or retention evidence.

  Current repository evidence

• Friend multiplayer is direct-first, so direct peers may see one another's IP. Relay is non-authoritative byte forwarding used only after all direct candidates fail while the service operates. It is designed not to retain payloads, raw IPs, or credentials; public status is region-aggregate only and excludes connection, lease, participant, and account identifiers. Production logging and retention remain launch Gates.

  Operational, code, or legal Gate

4. Sharing, processors, and international transfers

• No personal-data processor or international recipient is confirmed by repository configuration. OCI/Nginx is a deployment draft and Cloudflare is undecided.

  Current repository evidence

• Steam, STOVE, Epic Games, and other ownership queries appear only in the user source. Actual stores, APIs, contracts, countries, fields, transfer method, and retention are unresolved Gates.

  Operational, code, or legal Gate

• Any consent-based or legally required disclosure must be limited to the verified basis and scope at that time.

  Operational, code, or legal Gate

5. Retention and deletion

• Data should be deleted beyond recovery when its purpose or verified retention expires; a legal hold must disclose its basis, data, and period.

  Operational, code, or legal Gate

• Retention for accounts, ownership, sanctions, crash reports, inquiries, security logs, backups, and the deletion approver is unresolved.

  Operational, code, or legal Gate

6. Data-subject rights and inquiries

• Users may request access, correction, deletion, suspension, or withdrawal, subject to lawful limitations and identity or representative verification.

  Operational, code, or legal Gate

• The proposed channel is dnwn85@gmail.com. Sending mail processes the sender address and message; handling time, identity evidence, owner, and mail retention are unresolved.

  Operational, code, or legal Gate

7. Safeguards

• Data-handler minimization, access grant/change/revocation, collection minimization, and secure deletion are proposed safeguards.

  Operational, code, or legal Gate

• Hash-only storage, no-log promises, and incident handling are not final without implementation and operational evidence.

  Operational, code, or legal Gate

8. Children

• The source says data from children under 14 will not knowingly be processed without guardian consent and will be deleted when discovered. Age assurance, consent flow, and regional rules remain product/legal Gates.

  Operational, code, or legal Gate

9. External remedies

• Personal Information Dispute Mediation Committee: 1833-6972 · https://www.kopico.go.kr/

  Operational, code, or legal Gate

• KISA Privacy Infringement Report Center: 118 · https://privacy.kisa.or.kr/

  Operational, code, or legal Gate

• Supreme Prosecutors’ Office: 1301 · https://www.spo.go.kr/ / Korean National Police: 182 · https://ecrm.police.go.kr/

  Operational, code, or legal Gate

10. Effective-date and revision state

• The user-provided target date is September 1, 2026. The approved-effective-date slot is empty, so this structured draft is not effective; approval, notice method, and version history remain unresolved.

  Operational, code, or legal Gate