Privacy Policy

Effective / revised: October 17, 2026

1. Operator and scope

Next Studio (South Korea) operates NumberLink Pulse. The iOS and Android app identifier is com.osj.numberlink. This policy covers the app and this support website. Privacy contact: dhalska2@gmail.com.

2. On-device game data

The device stores number boards, removal/add-number moves, elapsed time, notes, hint-use records, completed stages, personal bests, daily puzzle/mission/calendar records, and language, sound, haptics and theme preferences by account. Pending save, ad and hint requests are retained for recovery. We do not use push notifications or a separate behavioral analytics SDK. See the crash diagnostics section below.

3. Sign-in and server storage (Supabase)

Supabase issues an anonymous user ID and stores game progress, preferences and completed activity. Apple/Google sign-in links a new identity or merges this game’s anonymous records and server-verified balances/entitlements into an existing account. Initial free grants and duplicate mission rewards are not transferred twice. Conflicting in-progress boards are retained for recovery. Cross-device restoration requires the same linked Apple/Google account. If an anonymous session is lost, you may be unable to recover its records yourself.

4. Ads and your choices

The mobile app shows Google AdMob interstitial ads and optional rewarded ads (for hints or one extra number addition per stage). The ad SDK may process your IP address and the approximate location derived from it, device/advertising identifiers, ad interactions such as views and clicks, diagnostic data, and consent status, to serve, measure, and protect against fraud in ads. We do not request precise location access. A consent message is shown depending on your region and choices; on iOS, tracking via the advertising identifier only occurs if you agree to the App Tracking Transparency (ATT) permission request.

5. Account and purchases

Signing in with Apple or Google causes your email, account ID, and authentication/access records to be processed in Supabase for authentication and to link progress across devices. Using an in-app purchase (remove ads, hint packs, theme pack, starter bundle) causes the product/transaction ID, purchase environment, purchase entitlements, and hint balance to be verified and credited via Supabase. We do not collect payment card details; the store handles them directly. iOS uses App Store billing and Android uses Google Play billing. Android purchase tokens are verified on our server through the Google Play API before crediting, then consumed/acknowledged; Google Play real-time notifications and the voided-purchases API revoke entitlements for refunded or canceled purchases. We store only a hash of the purchase token and the transaction state, not the token itself. Ranked entry tickets are also consumables. We process selected country, ranked attempts, scores, times and masked account labels for rankings. Hint-spend requests and account-merge proofs prevent duplicate grants and abuse.

6. Server data retention and cross-border processing

Account, purchase entitlement, and hint balance records are kept while we provide and can restore the service, and unnecessary information is deleted on request. Items subject to a transaction dispute or a legal retention obligation are kept only as required. Deleting your account does not delete the store's own transaction records. Servers operated by sub-processors such as Apple, Google, Supabase, and GitHub may be located outside South Korea.

7. Contact and website providers

If you email us, we use your email address, the content of your message, and any attachments you choose to send to respond and resolve the issue. Do not send passwords, authentication codes, or card details. We use Gmail for inquiries and GitHub Pages for website hosting. This page carries no ad or analytics scripts and no input forms. GitHub may process your IP address and access logs for hosting and security.

8. Retention and deletion

Local information remains until the app's storage is cleared. On iOS, use Delete App (Offload App can leave data behind); on Android, use Clear Storage for this app in system settings. Device and cloud backups are managed separately. We keep inquiry information only as long as needed to handle the request, then delete it. A secure-storage login session may survive app removal; use in-app data deletion for account data. Minimal token/session markers may be retained to prevent duplicate rewards, repeated merges and uploads from deleted sessions.

9. Your rights and legal basis

Subject to applicable law, you may request access, correction, deletion, a portable copy, restriction of processing, objection, withdrawal of consent, or review of a decision. You can contact us without discrimination for exercising these rights, and you may file a complaint with your local data protection authority. We may ask for identity verification within a reasonable scope.

10. Children, safeguards, and changes

The game does not require entering personal information. We do not knowingly request personal information from children; if a child sends information through an inquiry, a guardian may contact us to review or delete it. We take reasonable safeguards such as limiting access to inquiry data, but we cannot guarantee absolute security. For material changes we update the date and content here and provide any notice/consent process required by law.

11. Crash diagnostics (Firebase Crashlytics)

Release builds use Google Firebase Crashlytics to improve stability. It processes crash stacks, app and OS versions, device information and installation identifiers; development/debug builds do not collect. We do not add sign-in emails, names or purchase tokens as user identifiers or custom logs.