Sudoku Grow Privacy Policy

Effective: August 26, 2026 · Version 1.7 · 한국어

The operator of Sudoku Grow processes only the information needed to provide, protect, advertise, and improve the service. Contact: osm.dev.io@gmail.com.

1. Information and purposes

The service processes account and authentication details, game sessions and progress, Brain Score, Sudoku Coin and upgrade records, streaks, hint records, support inquiries, temporary IP-based abuse-prevention state, and advertising or rewarded-hint records. Optional Google or Apple connection processes the provider identifier, verified email, display name, and connection time. The service stores an account-wide notification preference. If the user allows system notifications, it also processes a random installation identifier linked to the service user, an Expo Push Token, platform, native app environment and language, registration or disable times, and transient ticket or receipt status. A streak reminder send processes a title and body containing the nickname and current streak length, plus a random delivery identifier and daily delivery, provider-confirmation, and analytics-delivery state.

The Production iOS and Android apps use Google Firebase Analytics and PostHog to understand product usage and quality. They may process the service-issued user identifier, a random app-instance or anonymous identifier, app, device and operating-system information, approximate location, and events such as app launches, foreground returns, background transitions, installations, updates, screen changes, authentication paths, game starts, resumes and outcomes, virtual-currency earning or spending, advertising lifecycle, and push delivery confirmation or opening. The service user identifier is set as Google Analytics User-ID and the PostHog user identifier to connect pre-login and account activity. Analytics properties do not contain email, nickname, Google or Apple identifiers, user input, puzzle content, or game, purchase, or ad-transaction identifiers. Push open-rate analysis uses only a random one-time delivery identifier, scheduled date, and notification type separated from the account, installation, and token; it does not send the delivery language, title, or body.

With separate device-level consent, PostHog may also record some app screens and touch positions. Images, input values, and nicknames are masked, and recording stops on authentication, account, Profile, support, and advertising screens. Other ordinary game screens and touch positions may be visible in a replay.

2. Retention and deletion

Account-linked data is retained until the account is deleted and is not automatically removed merely because it is inactive. Deleting the app does not delete a guest account on the server. Use Profile → Delete account before uninstalling, or first connect a social account. An account connected to Google can also be deleted through the public deletion page.

Push installation data is removed or updated after permission denial, logout, account deletion, or token replacement. If the delivery provider returns DeviceNotRegistered, the installation record is disabled so that token is not used again. A disabled record is updated if that installation registers again and remains with the account until it is replaced during token rotation or removed on account deletion. Streak-reminder type, random delivery identifier, scheduled date, account, installation, provider-confirmation state, and analytics-delivery state are retained for no more than 35 days to prevent duplicate daily sends and measure confirmed-delivery open rates. Delivery receipt and error state is retained for no more than 24 hours. Uninstalling alone may not immediately notify the server; the token is disabled after the delivery provider reports it as no longer registered.

Firebase Analytics event- and user-level data is retained for 14 months, PostHog product events for one year, and PostHog session replays for 30 days. Logging out, switching accounts, or completing deletion inside the app resets that device's analytics identity. We do not separately request deletion of events or replays already sent to the analytics providers, so they and aggregate statistics may remain for the applicable retention period. The public deletion page cannot control the user's device and therefore cannot reset its analytics identity.

3. External services

Google supports optional sign-in, Firebase Analytics and limited iOS first-open conversion measurement, AdMob advertising, User Messaging Platform privacy choices, and FCM notification delivery. Apple supports optional sign-in and APNs notification delivery. Expo Push Service registers push tokens and relays notifications and delivery status through infrastructure in the United States to Apple APNs and Google FCM. Apple may process personal data in facilities around the world and generally stores it in the United States. FCM runs on Google's global infrastructure and may process data wherever Google or its processors maintain facilities. Push processing may include a native device token, Expo Push Token, Firebase installation ID, Expo project identifier, network and device information, notification content, and ticket or receipt details. Expo states that notification content is kept only in memory and message queues for delivery, not in a database, and retains information only as reasonably necessary for the service. Firebase states that deletion of a Firebase installation ID from live and backup systems may take up to 180 days after the customer requests deletion. See the Expo Privacy Policy and Expo contact page. PostHog Cloud EU supports product analytics, optional session replay, and Feature Flags. Analytics requests are sent through a PostHog Managed reverse proxy on our own subdomain. Cloudflare processes the TLS connection and forwards the requests to PostHog Cloud EU without caching the request content or retaining request logs at the edge. The Cloudflare edge location is selected near the user and is not restricted to the EU. After forwarding, PostHog processes analytics data in the EU (Frankfurt) and is configured to discard the raw IP address after deriving approximate location. Cloudflare also supports HTTPS, security, and public documents. These providers may process information outside Korea under their own policies. See the Google Privacy Policy and Apple Privacy Policy, and the PostHog Privacy Notice and Cloudflare Privacy Policy. We do not sell personal information. Limited signup notices are sent to an access-controlled operator Telegram group. They include the event time, internal service user ID and signup path, plus the verified email for Google or Apple signup or linking. They do not include OAuth subject values, credentials, or request bodies.

Firebase Analytics advertising storage, ad user data, and ad personalization consent stay denied. Analytics is not connected to Google Signals and is not used for ad personalization. Firebase Analytics is linked to Google Ads only to measure the first open after an iOS app installation. This iOS conversion measurement uses de-identified, temporary event data processed on the device without ATT, IDFA, or user-provided account information. AdMob and UMP may separately process advertising information according to the user's choices and Google's policies.

4. Automatic collection and choices

The public website does not set first-party cookies. The Production iOS and Android apps automatically use Firebase Analytics and PostHog product events without a separate first-run checkbox or an in-app Analytics off switch. Session replay starts only after separate consent following the first completed puzzle and records a remotely selected 20% of consented sessions. If declined, the app does not ask again automatically. The device-only choice can be enabled or disabled at any time under Profile → Help improve the app. Disabling it stops the current recording; existing replays are deleted within 30 days. Development, Preview, and web builds do not send analytics events or session replays. Where required, advertising privacy options remain available separately for AdMob.

After a new account is created, the app directly requests system notification permission on the first Home entry. An existing user whose permission is still undetermined receives the same request once after updating. The app does not automatically ask again after a denial. The attempt is stored only on that device. The single Profile → Notifications switch controls the account-wide preference and appears off when system permission is not granted on the current device. Trying to turn it on requests permission or opens system app settings; after permission is granted and the app resumes, the account preference is enabled. Changing system permission on one device does not change it on another. Refusing notifications does not affect gameplay.

5. Your rights and security

You may request access, correction, deletion, or restriction by using the app, the public deletion page where available, or the contact address above. We apply HTTPS, restricted access, and secret-handling controls. Requests and complaints are handled first through osm.dev.io@gmail.com. This policy may change when law, the service, or processing changes; the published version and effective date will be updated.