PYON GAMES / PRIVACY

Privacy Policy

Effective: October 21, 2026 · Version 1.1

표현 (the “Operator”) operates account and match-history features for PYON Games and Line Rush. This policy explains the data processed, purposes, retention, and your rights. It applies to PYON Games, Line Rush, and the same service at line-rush.pages.dev.

1. Who processes your data?

Operator
표현 / Service brand: PYON Games
Privacy officer and contact
표현
Email
help.pyon.games@gmail.com

2. What data is processed, and why?

You can play against AI without signing in. If you choose account features, the social provider shares information through its consent flow. The Operator does not directly collect your Google or Kakao password.

FeatureDataPurpose
Google/Kakao sign-in and account linkingEmail, social provider and account identifier, service user identifier, registration and latest sign-in times; name, nickname, profile image URL, and other profile data if supplied by the providerIdentify members, maintain sign-in, link social accounts, and respond to account inquiries
Game profileGame nickname, user identifier, profile creation timeDisplay and edit profiles; connect records to accounts
Automatic match uploads (optional)User identifier, match ID, start/end times, hero, map, difficulty, result, game version, play states, events, in-game AI decisions, file size, hash, and upload statusStore and retrieve your matches; analyze gameplay
Technical operations and securityIP address, browser/device request information, request time, URL, response status, authentication and error logsDeliver the service, handle errors, prevent unauthorized access, and maintain security
Email inquiriesSender email, inquiry content, and materials you attachRespond to inquiries and handle account requests requiring identity checks

Data needed for accounts and service delivery is processed to provide the service you request and perform the service contract. Required consent is obtained through the social provider’s information-sharing procedure. Match uploads are a separate optional feature. Declining consent or optional features does not prevent sign-in-free AI play, but may limit accounts or server-side records.

3. How do you choose match uploads?

After signing in, turn on automatic match uploads in the account screen. Only matches newly started and completed in that browser are uploaded. Signing in alone does not enable uploads; settings are managed per account and browser. Turning uploads off cancels pending uploads on that device but does not automatically delete records already stored on the server. Request deletion by email.

If the network is unavailable, pending records are kept temporarily on the device for retry, up to 10 matches, 32 MB, and 7 days. This feature may be limited when local storage is unavailable.

4. How long is data retained, and how is it deleted?

  • Account/profile data and match summaries: Retained while the account exists and deleted following an account-closure/deletion request and identity verification. Unlike detailed replays, summaries do not automatically expire after 30 days.
  • Detailed match replays: Automatically expire and are deleted based on 30 days after storage. Actual deletion may take longer depending on the storage expiration job.
  • Pending uploads: Kept on the device for up to 7 days and removed from the queue after successful upload, expiration, or disabling uploads.
  • General operational logs: Under current plans, ordinarily accessible Cloudflare Workers logs cover up to 3 days and Supabase API/database logs up to 1 day. Separate infrastructure security/audit data and backups may be subject to each provider’s security and deletion policies.
  • Inquiry emails: Retained as needed to resolve the inquiry and deleted when the purpose is fulfilled. Data needed for disputes or legal retention is stored separately for the applicable reason and period.

Data is electronically deleted to make recovery difficult. Legally retained data is restricted to its retention purpose. Deleting your service account does not delete your Google or Kakao account. Records on your device can be removed using your browser’s site-data controls.

5. Which external services process data?

The Operator does not sell personal data or provide it to advertisers. The following services perform tasks needed to deliver the service.

ProviderWork and dataLocations and information
Supabase Pte. Ltd.Authentication and databases for accounts, profiles, and match summaries; emails, account identifiers, profiles, summaries, authentication and technical logsPrimary database/authentication region: Seoul, South Korea. Operational metadata, logs, and support may involve overseas processing. Data locations; subprocessors
Cloudflare, Inc.Website/game delivery, APIs, detailed match-file storage, and network security; request information, IP addresses, and uploaded match recordsGlobal network and APAC storage locations, not limited to one country. Privacy policy; network locations
Google LLC (Gmail)Receiving/storing official inquiries; sender email, messages, and attachmentsMay be processed outside South Korea, including the United States and other countries with Google facilities. Google privacy policy

Google and Kakao sign-in use the authentication process of the provider you choose. Provider policies apply separately to their accounts and consent screens. No unrelated third-party disclosure is made except where required by law or separately consented to.

6. Is data processed overseas?

Using the Seoul region does not mean all processing stays in South Korea. Requests, authentication, uploads, and inquiries are transmitted over encrypted networks to the providers above. Necessary processing, storage, security, and support may involve overseas locations.

  • Supabase: Primary account database/authentication data is stored in Seoul. The contracting primary processor is Supabase Pte. Ltd. in Singapore; support by a US affiliate and log processing in Europe may be involved as needed. Refer to the current public lists above for countries and subprocessors.
  • Cloudflare: Uses the global network of US-based Cloudflare, Inc. Network/file processing depends on access location, routing, and storage location. APAC is not a single country. See the network information above for possible locations.
  • Google: Inquiry emails may be processed in Google’s global facilities. Refer to Google’s policy for locations and contact information.

Transferred data, purposes, and retention periods are those stated above. Necessary entrusted processing and storage for concluding or performing the service contract are disclosed under Article 28-8(1)(3) of South Korea’s Personal Information Protection Act. Additional processing requiring separate consent will follow that procedure first. You may email questions, objections to overseas processing, or account-deletion requests. Refusing necessary entrusted processing may limit the relevant account or server-record features.

7. Device storage and tracking

Sign-in sessions/tokens, temporary account-linking information, self-declaration of being at least 14, upload preferences, game settings, and pending match uploads may be stored in localStorage, sessionStorage, IndexedDB, or similar browser storage. You may clear site data, sign out, or disable uploads. Clearing data may reset sign-in or preferences.

No separate advertising or analytics tools have been installed to track users for advertising. Infrastructure providers may process request information for service delivery and attack protection.

8. Google data and AI use

Google information is used for sign-in, account linking, and related member features. The service does not request additional Google API data such as Gmail messages, Drive files, or contacts. Google user information is not used for advertising or external generative-AI training. Use and transfer of information received from Google APIs follow the Google API Services User Data Policy, including applicable Limited Use requirements.

“AI battles” and “AI decision records” in Line Rush refer to the actions and decisions of the in-game opponent. This service currently does not provide a feature that sends match records to external generative-AI services for training.

9. Users under 14

Registration and social sign-in are for users aged 14 or older. When social sign-in is first started in a browser, users confirm that they are at least 14. The confirmation is stored in that browser and is requested again after site data is cleared. This is a self-declaration, not identity verification using a date of birth or ID document. If the Operator learns that registration has collected data from a child under 14, the account data will be deleted after necessary checks and member access restricted. Guardians may report this by email.

10. Access, correction, deletion, and suspension requests

You may request access to, correction or deletion of your personal data, suspension of processing, and account closure. Nickname changes, sign-out, and disabling uploads are available in the account screen. Send other requests to help.pyon.games@gmail.com. The Operator will verify the requester or authorized representative as necessary, process the request under applicable law, and communicate the result. Do not send passwords, one-time authentication codes, or national identification numbers.

11. Security measures

Measures include HTTPS transmission, account authentication, user-specific database access controls, private detailed-record storage, and restricted administrator access. Record viewing/downloads are limited to your own account, and upload sizes and frequency are limited.

12. Changes and contact

Changes to processing are reflected in this page’s effective date, version, and change information. Material changes to rights or obligations will be announced before or when they take effect, with consent obtained where required. Contact privacy officer 표현 at help.pyon.games@gmail.com for privacy questions or complaints.

For privacy-rights consultation or dispute mediation in South Korea, contact the Personal Information Infringement Report Center or the Personal Information Dispute Mediation Committee.