Privacy Policy for Hitori BLACKOUT
Hitori BLACKOUT ("the App", "we", "us") is a logic-puzzle game for Android and iOS. This policy explains what information may be processed when you use the App, why it is processed, and the choices available to you.
1. Information stored on your device
The App stores the game information needed to provide its features, including puzzle progress, marks, notes, settings, statistics, Daily progress, Journey progress, and a locally cached Remove Ads entitlement. This information is stored in the App's local storage and is not an account or cloud save.
Uninstalling the App or clearing its app data removes locally stored game data. A store purchase may remain restorable through the Google Play or Apple Account and the corresponding store purchase record used to make it.
2. Advertising and consent
The App may show interstitial advertisements through Google Mobile Ads (AdMob) at selected non-solving boundaries. AdMob may process technical and advertising information such as your device and app information, IP address, advertising identifier, approximate location inferred from an IP address, consent signals, and ad interaction or measurement information. Whether ads are personalized depends on your consent, device settings, applicable law, and Google's processing choices.
Google's User Messaging Platform (UMP) is used where required to request and manage advertising consent. You can review available advertising privacy choices from More → Privacy → Privacy choices in the App when that option is provided, and through your device or Google advertising settings. On iOS, if a release uses the advertising identifier (IDFA) for cross-company tracking and has a corresponding AdMob UMP message configured, UMP presents the explanation and manages the App Tracking Transparency (ATT) request. If you do not allow tracking, gameplay remains available and ads may still be requested without IDFA where permitted. The App does not issue a second, separate ATT prompt.
A one-time Remove Ads purchase disables interstitial advertisements after the purchase is verified by Google Play on Android or Apple StoreKit on iOS.
3. Analytics, crash reports, and remote configuration
Releases that enable Firebase may use the following services:
- Firebase Analytics: may process limited app and gameplay events, such as screens viewed, puzzle starts and completions, hint usage, settings changes, and purchase-flow outcomes, together with app version, device model, operating-system version, language, and pseudonymous app or installation identifiers.
- Firebase Crashlytics: may process crash traces, timestamps, app version, operating-system and device information, installation identifiers, and diagnostic context needed to find and fix stability problems.
- Firebase Remote Config: may process technical app and device information needed to deliver feature and operational settings, such as ad or content flags. It is not used to store accounts, puzzle boards, notes, or cloud saves.
We do not require sign-in, set a real-name profile, or send puzzle boards, solutions, notes, or other free-text content to Firebase. The App does not request contacts, photos, microphone access, or precise GPS location.
In releases with Firebase Analytics, usage analytics is enabled by default. You can turn it off or back on at any time in More → Privacy; the choice is saved on your device and applies independently of advertising consent and ATT. Analytics events are not sent while collection is disabled. Other Firebase services, such as Crashlytics or Remote Config, may have separate release configuration and collection behavior. If a release does not include a configured Firebase project, the App's Firebase adapters fail safely and local gameplay continues.
4. Purchases
The App offers one optional non-consumable purchase, Remove Ads. Android purchases use Google Play Billing and iOS purchases use Apple StoreKit. The applicable store processes the payment and keeps the transaction record. We do not receive or store your payment-card number. The App receives only the store information needed to verify, restore, and apply the Remove Ads entitlement on the store account used for the purchase.
5. How we use information
- to save and restore local gameplay and settings;
- to provide, measure, and protect advertising when consent and configuration allow it;
- to verify and restore the optional Remove Ads purchase;
- to understand app usage in aggregate and diagnose crashes or technical failures when the relevant Firebase services are enabled; and
- to operate and improve the App.
We do not sell personal information, require an account, or use the App to collect a user's contacts, photos, messages, or precise location.
6. Third-party providers
The App may use the following providers:
- Google Mobile Ads / AdMob and UMP: Google partner privacy information
- Firebase Analytics, Crashlytics, and Remote Config: Firebase privacy and security
- Google Play Billing: Google Privacy Policy
- Apple StoreKit and App Tracking Transparency: Apple Privacy Policy
These providers process information under their own privacy policies and terms. Their processing may occur in countries other than your own.
7. Retention and deletion
Local game data remains on your device until you uninstall the App or clear its app data. Store purchase records remain subject to the applicable store's retention policies. Google, AdMob, and Firebase retain provider-side data according to their applicable policies and retention settings. Because Hitori BLACKOUT has no user account and does not collect your name or email address in the App, we generally cannot identify a particular anonymous analytics or crash record on request. For questions about a privacy request, contact us using the address below.
8. Children's privacy
Hitori BLACKOUT is a general-audience logic game and is not directed to children under 13, or the higher minimum age required by local law. We do not knowingly collect personal information directly from children.
9. Security
Data sent to the listed providers is transmitted using the security mechanisms provided by those services, including encrypted connections where supported. No method of transmission or storage is completely secure.
10. Changes to this policy
We may update this policy when the App, its SDKs, or its data practices change. The revised policy will be posted on this page with a new “Last updated” date.
11. Contact
For privacy questions, contact:
Mladen Stojanovic
mladenstojanovicpo@gmail.com