Book of Witches · Privacy Policy

HELLO OFFICIAL TEAM · 안녕,쏘잉

Effective: November 6, 2026

Privacy information

HELLO OFFICIAL TEAM provides Book of Witches. This policy covers on-device saves, platform authentication, purchase verification and entitlement recovery, gameplay analytics, ads and support. Test builds with billing features may use Apple or Google test-purchase environments. Test purchasing does not mean production sales have started. Depending on the build, the app uses live or test ad units; both may involve Google advertising SDK network requests and information processing.

1. Information and purposes

Game data stored on the device

Progress, characters, cosmetics, companions, currency, item-grant history, settings, unfinished expeditions and backups are stored on your device to run the game and restore progress. On-device saves and manual save-code transfer are distinct from automatic server backup of all game progress. The paid ledger and outfit information associated with the billing features below are processed on the server.

Platform authentication, purchases and recovery

Billing connection processes Apple Game Center or Google Play Games player identifiers and authentication evidence (signed proof or one-time authorization codes), together with server-session and account-binding information. Product and transaction identifiers, store-verification material, purchase status, grants, entitlements, paid balances, refund adjustments, pass claims and server-stored paid outfits support purchase verification, duplicate-grant prevention, entitlement lookup/recovery and refund handling. The server stores hashes for authentication replay prevention and encrypted purchase-verification material. A hash derived from the connecting IP is used to limit requests; backend and platform providers may also process connection information. The game server does not ask you to send Apple or Google passwords or payment-card information. Enter information requested by a platform authentication interface directly with that platform.

Gameplay statistics

When gameplay-statistics sharing is enabled, the game sends a random installation identifier, session/event/run identifiers and timestamps, operating system and app version, character/stage/difficulty, progression choices, combat duration, damage, kills, currency and expedition results to PostHog for balance, reliability and feature improvement. Builds with Firebase Analytics may also send app events, usage, device/app information and SDK identifiers to Google. The game does not add names or email addresses to these events, record screens or capture keystrokes. Providers may process connection information when receiving network requests.

Advertising information

Google Mobile Ads (AdMob) may process IP addresses, approximate location derived from IP, device/app identifiers including advertising IDs, ad interactions and diagnostics for ad delivery, measurement and fraud prevention. The app currently requests non-personalized ads. Non-personalized and test ads do not imply that no identifiers or device information are processed.

Support requests

If you email us, we use your reply address, message and any device details, screenshots or save codes you choose to attach to handle your request. Do not send passwords, card details or other people's personal information.

2. Providers and international processing

Gameplay analytics is sent over HTTPS to PostHog US Cloud. Builds with Firebase Analytics also process analytics through Google. Ads use Google Mobile Ads and UMP; platform authentication and purchase verification use Apple or Google services. Backend functions are configured in Vercel’s Seoul region (icn1), and the Supabase database is configured in Seoul (ap-northeast-2). This does not confine all network, operational or support processing to Korea. Vercel’s global delivery network and Apple, Google, PostHog and other service infrastructure may process information outside your country. These services support the authentication, purchase handling, storage, analytics, ads and operations described above. Providers’ collection and processing practices are described in the following notices:

3. Choices

Gameplay-statistics sharing is off by default for new installations. Earlier builds may have used a different default; existing saved choices are preserved across updates. Turn it off in game settings to stop game analytics and clear pending local analytics and the local analytics identifier. Builds with Firebase Analytics disable collection according to this choice and reset local analytics data if already initialized. This does not automatically delete events already sent to the server or disable the advertising SDK. Contact us for deletion assistance. Your operating system's advertising privacy controls also apply.

The SDK may preload ads before you press a rewarded-ad button. The advertising integration checks privacy choices through Google UMP and presents a message when the SDK determines one is required. An advertising privacy-options button appears in settings when required. Presentation depends on the SDK’s regional/status determination and service configuration; not every user will see the same screen.

4. Retention and deletion

Local saves and backups remain on your device. Resetting game progress does not erase all settings, item entitlements or backups. Device app-data deletion or uninstall controls may help; copies may remain depending on operating-system backup and restore settings. You must delete exported save codes or files you copied separately yourself.

Uninstalling the app or resetting local progress does not automatically delete server-side platform bindings or purchase and entitlement records. Server information supports platform connection, purchase verification/recovery, duplicate-grant prevention and refund handling. Contact us below about retention, access, correction, deletion or stopping processing. We identify the relevant records and explain the available handling scope and methods after reviewing purchase/recovery history and applicable retention requirements.

The local pending-analytics queue is limited to 256 events / 2 MB; events older than seven days are discarded when reloaded. This is not the server retention period. Uploaded events follow the provider project's retention settings and deletion processing. Contact us about retention, access, correction, deletion or stopping processing. We will identify the subject of the request and advise whether it can be processed. Random app identifiers are not automatically linked to your email, so an email address alone may not identify every event.

Support correspondence is retained as needed to resolve and follow up on the request, subject to applicable retention obligations.

5. Save codes and security

Save-code transfer is a manual export/import feature, not a cloud backup or a secure vault for secrets. Do not post save codes publicly. We use HTTPS and restrict operational access, but cannot recover a lost device or copies you have shared.

6. Children and updates

We do not intentionally ask children for real names or contact details in the game. Check the audience and content rating shown in the app store you use. Contact us with concerns about a child's data. We update this page and its effective date when features, providers or information processing methods change and provide separate notice or consent where required.

7. Contact and exercising your rights

Operations and privacy inquiries: HELLO OFFICIAL TEAM

hello.official.team@gmail.com (mailto:hello.official.team@gmail.com (mailto:hello.official.team@gmail.com) )

Use “Book of Witches privacy request” in the subject and describe your request and app version. Do not initially send identity documents or sensitive information beyond what is needed for a reply.