Privacy Policy — The Hangman Is Coming
Draft — release verification pending. This review describes the current Android internal test and the consent and purchase updates prepared locally. Those updates still need Google Play phone testing and store/consent-message setup. This page has not yet been approved as the final Android release policy.
Review date: October 25, 2026 · Operated by: TANYELW · Contact: thehangman07@gmail.com
This policy covers The Hangman Is Coming Android application ("the Game"). Gameplay and character/session data run locally. The Android source integrates Google AdMob for advertising, so a claim that the application collects no data would be inaccurate. A separate browser demo is described in section 3.
1. Gameplay and Data Processed by the Application
The Game does not require an account or login. Its story, character name, chosen trait, dice results, and session Graveyard are processed on your device; the reviewed gameplay source contains no code that sends these to the developer. These session values are kept in memory and are lost when the application session ends. The reviewed project contains no developer-operated backend, separate analytics service, or separate crash reporting integration. Advertising is processed by Google AdMob as described below.
2. Advertising Data Summary
Google's Mobile Ads SDK disclosure describes the following data processing. Actual collection depends on the released SDK, settings, consent, and any ad partners. This summary is not a verified copy of a submitted Google Play Data safety form.
| Data type | Processing by Google AdMob | Purpose |
|---|---|---|
| IP address and approximate location inferred from it | Collected and shared by the advertising SDK | Advertising, measurement, analytics, fraud prevention |
| App interactions, such as launches, taps and ad views | Collected and shared by the advertising SDK | Advertising, measurement, analytics, fraud prevention |
| Diagnostics, including app/SDK performance | Collected and shared by the advertising SDK | Advertising, measurement, analytics, fraud prevention |
| Device and account identifiers, including Android advertising ID and app set ID where applicable | Collected and shared depending on SDK settings and available identifiers | Advertising, measurement, analytics, fraud prevention |
3. Third-Party Services
- Google AdMob (Android advertising). The Android Game includes interstitial advertising at breaks in play. The current internal-test configuration uses Google's test ads; the production advertising configuration remains to be verified. Google processes advertising data under Google's Privacy Policy and information about apps using Google services. No separate analytics service, crash-reporting service or mediation adapter was found in the reviewed project.
- Consent and advertising choices. The next Android test build uses Google's User Messaging Platform to check consent information before initializing or requesting ads and to display a Google consent form when required. A Privacy choices menu control reopens Google's privacy-options form when Google requires that option. If the app cannot establish that ad requests are permitted, ads stay off and gameplay remains available. This follows Google's UMP guidance; the local implementation still needs end-to-end phone verification with a published AdMob message. The current Play internal-test release predates this change. Android advertising ID controls are also available in device settings and are separate from in-app consent choices.
- Purchases. A one-time "Sever the Strings" remove-ads purchase is planned for the full Android release. The current published internal-test build predates billing integration and does not complete purchases. The next build has a locally prepared Google Play Billing integration that still requires store setup and phone testing. Google Play handles the purchase and payment process under Google's Privacy Policy. The prepared app code checks product ownership, purchase state and acknowledgement using purchase tokens supplied by Google Play; it does not receive card details or send these tokens to a developer-operated server. Purchase restoration uses the Google Play account on the device. The browser demo has no purchases.
- Browser demo and hosting. The browser demo does not load the native ads or purchase script, set cookies, or add analytics. Its fonts, artwork, and scripts are served with the site. The website is hosted on Cloudflare Pages. Cloudflare processes visitor connection data, such as IP addresses and HTTP request information, to deliver and protect the website under Cloudflare's Privacy Policy. The private GitHub repository holds development files. Playing the browser demo does not create an Android account or upload the character name.
4. Permissions & Device Capabilities Used
| Capability | Purpose | Data involved |
|---|---|---|
| Vibration / haptics | Dice-roll and scare feedback | None |
| Screen wake lock | Prevent sleep during play | None |
| Fullscreen / orientation lock | Immersive presentation | None |
| Network access | Advertising services; story gameplay runs locally | Handled by AdMob (see §3) |
5. Local Storage
The Android source reads a local hangman_noads flag for the remove-ads feature; it is an on-device entitlement flag. The prepared purchase update saves that flag only after a completed purchase has been acknowledged, keeps a cached entitlement when Google Play cannot be reached, and rechecks ownership on startup or return to the app. A successful store query with no owned purchase clears a stale flag. The current published internal test predates this update (see section 3). Google Play maintains its purchase records; advertising and consent SDKs may maintain their own device data. The browser demo does not read or restore Android game progress or purchase flags.
Character and Graveyard data are kept only for the current session. Clearing application storage or uninstalling removes app-local data, subject to any Android backup/restore settings. Google controls retention and deletion of advertising and purchase data under its policies. Any additional release retention practices must be verified before this draft is finalized.
6. Children's Privacy
The Game contains horror themes, jump scares, and flashing imagery. TANYELW intends the Game for players aged 16 and older. It is not designed for children. This intended audience is separate from any store-assigned content rating. The release AdMob audience/under-age settings and consent handling must still be verified; the presence of advertising means the application cannot claim that no data is processed about its users.
7. Your Rights (GDPR / CCPA)
Depending on your location and applicable law, you may have rights concerning access, correction, deletion, or restrictions on processing of personal data. Session gameplay data can be cleared by ending the session; app-local data can be cleared in Android settings. For advertising data, see Google's privacy information and controls. Contact the developer using the privacy contact in section 10 for app-specific questions. The developer will use the privacy contact below for app-specific inquiries; release retention and deletion procedures still require confirmation.
8. Data Security
Gameplay session data stays on the device in the reviewed source. Google states that user data collected by the Mobile Ads SDK is encrypted in transit using TLS. No method of storage or transmission provides an absolute guarantee of security.
9. Changes to This Policy
If this policy changes, the updated version will be posted on this page with an updated effective date. The published policy and Google Play Data safety declarations must reflect the actual released Android application.
10. Contact
Developer/operator: TANYELW
Questions about this policy: thehangman07@gmail.com
The intended audience is 16+. The Android app uses AdMob; a one-time remove-ads purchase is planned. Production consent and advertising behavior still require verification. Keep the finished policy publicly accessible at a stable HTTPS URL.