HAYO
Privacy notice · free lives and ad removal
Privacy information for free starts, ads between lives, ad-removal purchases and optional usage sharing.
Prepared: 16 October 2026. This notice applies to the configuration offering Google, Apple or email account connection, free random lives, full-screen ads between lives and a one-time ad-removal purchase. The earlier configuration with Gems and optional rewarded ads is covered by the v39 notice. The configuration without ads, accounts or purchases is covered by the earlier notice.
Life records and online features
Your current life, choices and archive are saved on your device. We do not upload the full gameplay history or save contents. Random lives are free to start; a full-screen ad may appear after one life ends and before the next begins. You can start a new life for free even if you decline ads or an ad cannot be loaded. Names, countries, health and wealth in the game describe fictional characters; we do not ask for your real identity, health or wealth.
At startup, the app attempts online authentication to check account and purchase status. It connects to hayo.dev over HTTPS to check for updates without adding your full play history or account identifier to that update request. Providers such as Firebase Hosting may process IP addresses and connection information when handling requests.
Accounts and security
Firebase Authentication processes a guest account identifier (UID) and connection information. When you link or sign in with Google or Apple, the provider account identifier, any supplied email address and profile display name are used for Firebase Authentication and account management. If Apple provides a private relay address, that address is used. Email sign-in uses your email address and password. Adding a sign-in method to the current game account preserves its UID. Signing in to a different existing game account requires a separate confirmation and does not automatically merge purchases. The same UID is used as the RevenueCat app user identifier to check purchases. We do not separately send your email as a RevenueCat profile attribute. Passwords and authentication tokens are not saved in life records or the app’s own logs.
Firebase App Check and Google or Apple verification services check app and device integrity. App/device verification material, tokens and connection information may be processed to prevent misuse. Purchases or earlier Gem balances from different accounts are not automatically merged.
Game usage analytics
Game usage analytics is off by default. There is no separate consent pop-up. In supported public mobile apps, Firebase Analytics collection starts only after you explicitly turn on “Share usage statistics to improve the app” in Settings. You can turn it off there at any time. Free gameplay and purchases remain available without sharing analytics. Earlier refusals are respected, and consent in an older setting is not automatically treated as consent to the new setting. Collection remains disabled in internal QA packages and desktop tests regardless of this setting. Advertising consent and your game usage analytics choice are separate.
Events sent directly by the app cover screen navigation, time spent on a screen while the app is active, ranges of the fictional character’s age and choice count, completed/cancelled/failed feature steps, and types of save errors. These analytics events exclude names you type, email addresses, stories, country-search terms and complete choice histories. We do not set an analytics user ID or user profile.
The Analytics SDK may process an app-instance identifier distinguishing installations, device/OS/app information and automatic events such as sessions. Google states that Analytics 4 uses IP addresses at collection time to derive general location, such as country and city, and then discards the IP addresses before data is logged in any data center or server. Store-purchase events may include product identifiers, names and prices. The app disables advertising-identifier collection for Analytics and denies advertising storage, advertising user data and ad personalization. This does not mean that all data, including app-instance identifiers, is absent or fully anonymous. Analytics retention and deletion follow the applicable Analytics configuration and provider policies.
Ads and privacy choices
We do not ask for a separate advertising age. Protective settings for an unspecified age are sent to Google AdMob and the UMP consent SDK. Ad content is limited to rating G, and we do not request personalized ads. These settings and the ad content rating do not make the game or purchases adults-only.
Advertising SDKs may process IP addresses, device/app identifiers, ad impressions and interactions, and diagnostic/performance information. IP addresses may be used to estimate general location. Google screens explain required consent, and ads are requested only when the SDK permits requests. When a privacy-choice entry point is required, a button appears in Settings. Opening and closing that privacy form alone does not request an ad.
Verified ad-removal ownership prevents full-screen ads between lives. If ownership has not yet been checked, the app also holds back these ads and repeat purchases. Ad removal removes the ad placements; it does not remove account/purchase verification or game usage analytics.
Ad-removal purchases and restoration
Ad removal is a one-time purchase. Apple or Google Play processes payment; the app does not receive card numbers. The actual price displayed by the app comes from the store. Purchases and restoration require linking Google, Apple or an email account. Sign in with the same game account to restore purchases. Signing in alone does not grant ad removal; a purchase or verification of existing purchase rights is required.
RevenueCat may process purchase status linked to your account identifier, product/transaction identifiers, prices, currencies, status, receipts or purchase tokens, and technical information such as device, OS, app and language. Ad-removal access is applied after purchase status is checked; verified refunds, cancellations or revocations remove the entitlement. Purchase restoration does not transfer your full on-device life archive to another device.
Earlier Gems and transaction records
This configuration does not expose Gem sales or birth-condition selection. Existing Gem balances, purchases, ad rewards and country-selection transactions remain with their existing account and may be processed to verify, recover or delete earlier transactions. Earlier country-selection records may include the fictional game country, transaction identifiers, generation information, processing times and a verification hash of the first save. The full save contents are not sent. Hiding these features does not delete existing balances or transactions.
Providers, processing locations and retention
Google and Apple provide your selected social sign-in and authentication information. Google Firebase/Google Cloud provides authentication, app verification, servers and earlier transaction storage, web delivery and usage analytics. Google AdMob/UMP provides advertising and consent management. RevenueCat verifies purchases, entitlements and earlier Gem transactions. Apple or Google Play handles payments, orders and refunds. Firestore and functions run in Seoul, but Firebase Authentication operates in the United States and other providers may process information abroad.
Account and earlier transaction records are handled in response to account-deletion requests. Firebase documents authentication IP-log retention for weeks, Hosting IP retention for months, and removal of authentication information from live and backup systems within 180 days after user deletion. Providers’ backups, security, advertising, transaction and analytics records remain subject to their retention policies and legal obligations. We do not promise to shorten all provider retention periods or immediately erase every provider record.
Sharing, account deletion and refunds
Images, text and HTML books are created when you choose to save or share them. They are not published to other people before you choose a sharing destination. Copies exported to another app or storage location, and operating-system backups, are subject to those services’ policies. Review any personal information you put in a record before sharing it.
You can request deletion under Account connection in Settings. You authenticate again using a linked sign-in method. For Apple-linked accounts, server deletion is requested only after Apple reauthentication and token revocation succeed. The Apple procedure takes priority when Google is also linked. Cancelled or failed reauthentication or revocation does not continue to a deletion request. The server account and earlier Gem/country-selection records are handled according to the deletion request; deleted balances cannot be recovered. Delete local life records, exported files and operating-system backups separately. Account deletion does not erase Apple/Google order records or automatically issue refunds, and it does not waive statutory refund rights. We do not guarantee purchase restoration to a deleted game account.
See account deletion instructions for requests, including when you cannot access the app.
Your rights and contact
Contact contact@hayo.dev to request access, correction, deletion or other rights available under applicable law. We use support requests and reply addresses to answer and handle requests. We may ask for the minimum account information needed to do so safely. Do not send passwords, authentication tokens or card numbers. If practices change, we will update the applicable configuration/version and notice and communicate changes where required.
Operator: HAYO · Contact: contact@hayo.dev
Provider information: Firebase · Analytics collection · Google advertising · RevenueCat · Apple