NEON BLOCK PULSE

Privacy Policy

2026-10-03

1. Operator and scope

Next Studio, based in South Korea, operates Neon Block Pulse (com.osj.neonblockpulse). This policy covers the iOS app and this support website. Privacy contact: dhalska2@gmail.com.

2. Information stored on your device

Your active Marathon board, personal bests, lifetime stats (lines cleared, play time, Tetrises, T-Spins, best combo, games played), solved puzzles, daily-challenge best, weekly-mission progress, your best run's input log used for the ghost score, and your language, sound, music, haptics, control, colour-blind and reminder settings are stored on your device to resume play and show your stats. On iOS your sign-in session is kept in the Keychain, which can remain after you delete the app so you are signed in again after reinstalling.

3. Accounts and progress sync

On launch, the app silently creates an anonymous account (no sign-in screen shown) so your coins, skins, board themes, badges, season progress, stats, personal bests, solved puzzles, daily best, weekly-mission progress and settings sync to our Supabase server. Signing in with Apple links the same identifier and the name and email Apple provides (which may be a private relay address) so progress follows you across devices and you can join the leaderboards. Signing in is optional; the game and coin wallet work without it, but guest scores do not appear on leaderboards.

4. Purchases

Coins and Remove Ads are sold through the App Store. Apple processes payment; our server verifies the transaction identifier and product to credit coins or remove ads and keeps that purchase record. We do not store card details or raw receipts.

5. Advertising

We use Google AdMob and its consent SDK (UMP) to show rewarded and interstitial ads. Google may process device and ad-interaction data and IP addresses (which can suggest an approximate location) to serve ads, verify rewards, prevent fraud and produce diagnostics. We always request non-personalized ads and do not track you across other companies' apps and websites; you can review your consent choice in Settings under Ad privacy options.

6. Crash reports

To find and fix crashes, we use Google Firebase Crashlytics, which collects crash and unhandled-error logs, device model, OS version, app version and a Firebase installation identifier. This is turned off in development builds.

7. Notifications and sharing

If you turn on the daily reminder in Settings, the app asks for notification permission and schedules one local notification at 8 PM on your device. It is not sent from a server and nothing is shared to schedule it. When you tap Share, your device's share sheet sends the text you choose (your score and a challenge code) to the app you pick; we do not receive it.

8. Leaderboards

If you sign in, your score or time, lines cleared, chosen badge and country appear on the public per-mode leaderboards under an automatically generated name such as PLAYER1A2B. Your email and Apple name are not shown. Don't sign in if you'd rather not appear there.

9. Providers and international transfers

We use Supabase (accounts, wallet, progress, leaderboard), Google AdMob/UMP (ads), Google Firebase Crashlytics (crash reports), Apple (sign-in, purchases), Gmail (support) and GitHub Pages (this website). These providers may process data outside South Korea.

10. Retention and deletion

Local data stays on your device until you clear app storage or delete the app (the Keychain sign-in session is removed when you delete your data or sign out in the app). Server-side coins, skins, season progress, stats, solved puzzles, mission claims, settings and leaderboard records can be deleted immediately from the Settings tab, or by emailing us; after deletion the old session can no longer recreate them. Store purchase records needed to prevent fraud, handle refunds and meet legal obligations may be kept separately for a limited period.

11. Your rights

Email us to request access, correction, deletion or withdrawal of consent. We may need to verify your identity to process a request.

12. Children and security

This service is not directed to children under 14 and we do not knowingly collect their personal information. We use reasonable safeguards, including limiting access, but cannot guarantee absolute security.