개인정보 처리방침

Privacy Policy — English

Effective and last updated: September 30, 2026. The operator is 픽셀포즈 (PixelPaws), a sole proprietorship, represented by 장인규, who also handles privacy inquiries.

NEON SORTIE stores progress, scores, earned credits, and preferences on your device. An active flight cannot be resumed after the app closes. An online ranking submission is separate from cloud backup of progress. Your first connection requires choosing “Use online rankings” after the notice; before that choice, no ranking request is made. If an existing ranking identity remains on your device, the app checks the server and that identity on launch. Connecting transmits your IP address. A successful account creation stores a random installation ID, a SHA-256 hash of the authentication token, a generated Pilot-XXXXXX name, and creation time on the server. The original authentication token remains on your device for subsequent requests. If you separately enable purchase services, an existing normal ranking installation ID is linked to the RevenueCat app user ID for equipment checks. Joining rankings is not required for purchasing or restoring purchases. A build without a configured ranking service does not create that session. Weekly best records contain score, sector, selected gear, submission time, and week. Rank, generated name, score, sector, and gear are public. Input replays are processed in memory for server revalidation and are not stored. Provider processing and countries are described below. Purchase and ad connections are separate choices. The app stores each choice, notice version and selection time locally before starting that connection. On first use without a valid saved choice, the app does not request the corresponding SDK initialization. Choosing Connect purchases starts RevenueCat for real prices and access checks; connecting is not a purchase. A valid saved choice can enable checks on later launches, resumes, purchases and restoration. Store services and RevenueCat process transaction details, subscription status and app user identifiers, including checks without a new purchase. You can purchase and restore without joining rankings. Services without a prepared notice cannot be enabled. PixelPaws does not receive your full payment card details.

Public full-demo credits, research and preferences exist only in memory and disappear when the demo or app closes. The separate demo league also requires an explicit connection. It uses the same disclosed connection and replay-validation information, and publishes the temporary pilot name, score, sector and equipment on its own board. Its identity and token are separate from normal rankings and purchase identity, and are not saved to device storage. Exiting the demo attempts server deletion. Accounts expire 24 hours after creation; cleanup delays and recovery records are described below.

Service-specific processing and overseas transfers

Initial purchase, ad and ranking connections are separate choices. Basic flights and the offline demo work without them. Apple App Store or Google Play processes store payments under its own privacy policy.

Google uses servers in multiple countries. Its published operating data-center locations include the US, Singapore, Taiwan, Japan, Ireland, the Netherlands, Denmark, Finland, Germany, Belgium, the UK, Uruguay and Chile. This describes published infrastructure, not a claim that every ad or email goes to each country or a verified set of AdMob-specific routes. See Google's data-center locations.

Overseas processing and storage necessary for the requested purchase or ranking service use the disclosure route under Article 28-8(1)(3)(a) of Korea's Personal Information Protection Act. Overseas third-party ad disclosure is explained as a separate optional consent; a UMP result does not replace it. Declining or stopping and the affected features are explained below.

To limit abuse and excessive requests, the ranking server combines an IP address with a random value specific to its storage and hashes it with SHA-256. Its database retains the resulting digest, request count, and expiry time; that rate-limit table does not store raw IP addresses. Authenticated request limits also use the account authentication-token hash. Counters survive server restarts. These identifiers are pseudonymous, not anonymous. This describes the app server database and does not mean that Cloudflare or other providers do not process IP addresses or connection logs.

After your explicit ad-connection choice is saved, the app starts Google’s consent-status check, presents required messages and may prepare permitted ads. A valid saved choice can enable this on later launches and resumes. Before the initial choice, the app does not request UMP checks or initialize the ads SDK. An ad is displayed only after you choose its reward button. Google Mobile Ads and UMP may process device and app information, IP address, ad interactions, diagnostics, and consent choices to prepare and provide ads, manage consent, and prevent fraud. The app requests non-personalized ads with teen age treatment and a maximum ad content rating of G for all requests. These settings do not verify a user’s age and may still involve data processing before you choose to watch an ad. The actual processing depends on the SDK configuration and your choices.

Hosting of this information site

This static information and policy site is delivered through Cloudflare Pages' global network. Visits can transmit an IP address, requested URL, time and browser/connection details for content delivery, security and troubleshooting. PixelPaws adds no analytics scripts, enquiry forms or its own cookies and does not link site visitors to ranking or purchase accounts. Site traffic and provider security records are separate from the ranking database's US jurisdiction setting. Cloudflare's retention, security and legal processing follow its privacy policy; game-record retention is not a fixed deletion deadline for site connections. Contact: privacyquestions@cloudflare.com.

If you email support, your address, message, and attachments are processed to respond. Reset local flight record in app settings removes progress such as scores, credits, research, and earned liveries while retaining sound, haptics, and language preferences. Device app-data controls or uninstalling can remove local data. We manually delete ordinary support messages, attachments and replies and empty Trash within 30 days after resolution and follow-up are complete. This is an operator procedure, not an automatic deletion feature. Necessary records subject to statutory retention are separated and retained for the applicable period. Google’s recovery, security and legal retention may differ; this is not a promise that every provider copy disappears within 30 days. The ranking server removes attempt records (seed, gear, creation time, and validation result) older than two days and weekly score records whose week-start date is earlier than the date 56 days (eight weeks) before cleanup. Request counters use one-minute or one-hour windows and expiry times. Expired rows are eligible for cleanup, scheduled at hourly intervals; deletion is not guaranteed at the exact expiry time. Free-plan quota exhaustion or service failures can delay cleanup. Installation accounts may remain until deletion. A successful authenticated in-app ranking deletion removes the account, scores, attempts, and that account’s rate-limit records. IP-derived rate-limit records expire and are cleaned up separately from account deletion. Uninstalling alone does not remove server records. Demo accounts expire 24 hours after creation; their scores, attempts and account counters are removed together. Requests and hourly cleanup enforce expiry; outages or exhausted free quotas can delay cleanup. Normal league accounts do not acquire this demo TTL.

Server deletion removes live database rows and associated records. Cloudflare documents point-in-time recovery of SQLite Durable Objects for the previous 30 days. No operator-managed scheduled exports are currently configured, but this does not mean provider recovery copies disappear immediately. Recovery is managed to avoid republishing previously deleted accounts. This policy site has no analytics scripts or its own cookies; the hosting provider may still process connection information.

Choosing not to connect to rankings does not prevent normal offline flights. In Settings, “Delete ranking account” removes the current normal account; the demo has a separate “Delete demo ranking account” action. After successful deletion, the app does not automatically rejoin. A failed or offline deletion is not reported as completed; retry or contact support. You may also request deletion by email from the web instructions without reinstalling or opening the app. Basic flights and the offline demo work without purchase/ad connections or ranking signup. Declining or closing a service notice does not start that connection. Without purchase access, price queries, purchases, restoration and online access checks are unavailable; without ad access, ad rewards are unavailable. Settings → Stop new requests stops new app requests for that service. Already-started SDK work may continue until it finishes. A saved stop prevents connection on the next launch; a failed save is reported because the previous choice may return after restart. Stopping is not deletion, a refund or subscription cancellation. Stopping preserves store purchases and the saved livery choice, but paid gear and club benefits remain inactive until you reconnect and access is verified again. Restore purchases if needed. While ads are connected, Google’s privacy choices can be changed if the relevant message or option is available. Stopping new app requests is a separate setting. Email nonogram.zoo@gmail.com to request access, correction, deletion, or other applicable privacy rights. We may request minimal verification. Deleting ranking data does not delete RevenueCat purchase records or cancel a store subscription. Contact privacy support about purchase-record requests and manage subscriptions through the store. The initial launch is planned for Korea and the United States, intended for teens aged 16 and older and adults. This intended audience is separate from the store content rating or verified age. The app does not ask for a birth date or verify age. Contact support if you believe a younger user’s information has been handled inappropriately. Ad requests use teen protection; required Google privacy choices are provided separately. Changes and their effective dates are shown here.