Bukangi: North Port Escape

Privacy Policy

This policy explains the personal data processed by Bukangi: North Port Escape, why it is used, how long it is kept, and how to request deletion.

Effective: October 31, 2026

Operator and scope

This policy covers the iPhone and Android game Bukangi: North Port Escape and this support site, operated by Yong jun Lee. Contact lyjfsimonero@gmail.com. The intended audience is ages 13 and older.

Account and game data

  • Authentication: A Firebase anonymous account identifier (UID) and authentication tokens distinguish saved data and manage your account. Registration does not ask for a name, email, telephone number, or password. An anonymous account still has a linkable identifier.
  • Game storage: Cloudflare D1 stores progress, stamps, completion counts and daily results, best times, ghost runs, owned and equipped items, and recent run identifiers. These support continued play and validation of results. Ghost coordinates are positions inside the game, not real-world location.
  • Leaderboards: Other players can see a server-assigned public tag, course results, rank, collisions, collected bubbles, and completed-map count. The tag is linked to the account; the leaderboard does not expose the original UID or authentication tokens.
  • On-device storage: Language and sound settings, unsent runs, an account-owner hash, and deletion status and receipts are stored locally. Unsent runs are cleared after confirmed server saving or confirmed removal of that account’s game data. Deletion status and receipts are cleared when you explicitly start a new journey after deletion completes.

Providers and connection information

Google Firebase Authentication handles authentication, account management, and abuse prevention in the United States. IP addresses support authentication security. The Firebase SDK collects user-agent information by default, including device, OS, app, and development-platform information, to analyze platform and version adoption without linking it to user or device identifiers. See Firebase privacy and security information.

Cloudflare provides the game API, D1 storage, and support site. The game database is currently located in Asia Pacific (APAC); storage is not restricted to a particular country. API and support requests pass through Cloudflare’s global network. IP addresses, routing, system, and traffic information may be processed to provide and secure the service. Stored Workers Logs and Traces are currently disabled for this Worker. This does not mean Cloudflare performs no network or security processing. See the Cloudflare Privacy Policy.

Support emails, including your address, message, and attachments, are received through Gmail and used as needed to resolve the inquiry and verify the account.

Photos and sharing

Selected photos and game pictures are composed in device memory and are not uploaded through the current game API. If you choose to save or share a picture, the selected external app or recipient may receive it under that service’s policy. The dedicated Kakao upload and sharing connection is currently disabled. Account deletion does not recall pictures already saved or shared.

Advertising SDK and purchases

App versions with advertising enabled show Google AdMob banners only on the main and shop screens, never during gameplay. Display depends on the selected age group and Google UMP consent status. The ad SDK is not loaded before an age group is selected or for users under 13. The age-group choice stays on the device; no date of birth is requested or sent to the game server. Required age-treatment signals are passed to the SDK, with publisher ad personalization and first-party identifier use configured as disabled. Google Mobile Ads SDK and UMP may process or share IP addresses (which can estimate general location), device and app identifiers, ad and app interactions, and diagnostics such as crashes and performance for advertising, analytics, and fraud prevention. See the iPhone SDK data disclosure and Android SDK data disclosure. Disabled ad display is not a guarantee that providers process no information.

In app versions with sales enabled, paid items use Apple in-app purchases on iPhone and Google Play billing on Android. RevenueCat checks and restores purchases using a persistent, randomly assigned billing identifier linked to your game account instead of your name or email address. RevenueCat processes store receipt or transaction information to verify item ownership and also uses purchase history for customer-history and purchase-trend analysis in its dashboard. The game server stores verified ownership linked to your account. Payment approval and card information are handled by the store; the game does not ask you to enter a card number.

Retention periods

  • Game account and saved data: Kept to provide the game until account deletion is requested. Identifiers needed to finish deletion are kept until that processing completes.
  • Support inquiries: Kept while the inquiry is handled, then manually deleted by the operator within 90 days after resolution.
  • Firebase authentication: Under the provider’s policy, logged IP addresses are kept for a few weeks. Other authentication information is removed from live and backup systems within 180 days after the operator initiates deletion of the user. This is separate from game-record retention and does not promise immediate deletion of every copy.
  • D1 automatic recovery history: The current Time Travel recovery window is 7 days. Recovery history may include data from before deletion. This window is not a deadline for physical erasure of every internal provider copy. See D1 recovery and backups.
  • Exceptional pre-release operational backups: Separate service-recovery backups have restricted access and are manually discarded within a maximum of 30 days after creation. They are separate from automatic recovery history and do not have a scheduled automatic deletion. Deletion requests must be reapplied before a restored backup is connected to the service.

Cloudflare’s separate network and security information follows its purpose-based and legal retention criteria. Disabled Workers Logs and Traces, or D1’s 7-day recovery window, are not a deletion deadline for all provider data.

Account deletion and limited remaining data

Use “Delete account and journey data” in the app to review the current account’s scope and confirm the request. You can also request deletion outside the app. Uninstalling the app does not delete its server account.

After removing server progress and leaderboard data, we request deletion of the RevenueCat customer if a linked billing identifier exists, then complete Firebase account deletion. Failed stages are retried and are not marked complete beforehand. RevenueCat processes deletion asynchronously: the app’s completed status confirms acceptance of that request and Firebase account deletion, not immediate erasure of every provider copy. After Firebase deletion is confirmed, raw identifiers are erased and minimal work data such as hashed identifiers, receipt hash, status, and timestamps remain temporarily. The receipt is valid for 24 hours after the request, not a deletion deadline. Completed work is cleared during the next deletion-related processing after both receipt expiry and the 70-minute old-token block have ended. There is no scheduled cleanup at an exact time.

Your requests and policy changes

Contact us to request access, correction, or deletion. A name or email alone does not prove ownership of an anonymous account; support will explain the minimum verification required. Requests or account recovery may be limited if ownership cannot be established. Use the same contact for information concerning a player under 13. This policy and its effective date will be updated when processing changes.