Privacy policy

1. Information on your device

Echo does not ask you to create an Echo account. Game preferences, personal bests, Daily Echo progress and streaks, saved game state, completed-game advertising counters and your age classification are stored locally. We do not receive your scores or game sequences.

The age screen stores only the selected age band or unknown-age choice. Echo does not request or store your full birth date. Verified purchase ownership and the information needed to restore it are also cached in the app’s private local storage.

Sound is generated on the device. Echo does not use the microphone, camera, contacts or precise device location to play the game. The game and Daily Echo work offline; advertising, purchases and restoration use network services.

2. Younger players and shared devices

Echo is intended for ages six and older. Unanswered age choices receive no advertising. Players classified as under 18, below the intended minimum age, or of unknown age use the protected advertising path: child-directed treatment, an under-age-of-consent signal and a maximum ad content rating of G. Interstitial ads are disabled on this path.

Age choices do not unlock game modes or rewards. Parent controls allow the age classification to be changed for a shared device and protect access to purchase and external-link controls. A parent gate is a product safeguard; it does not replace any legal parental consent or Google Play approval.

Protected settings restrict advertising data practices, but they do not make every network request anonymous. Advertising services may still process technical information such as an IP address. If you believe a child has sent personal information to Geniosity, contact us.

3. Advertising and privacy choices

Echo uses Google AdMob and Google’s User Messaging Platform (UMP). Ads can appear in a reserved area while the game is idle or finished. Eligible adult players can also receive an interstitial at a natural break after every fifth completed game. Ads do not appear during an active round.

Google’s Mobile Ads SDK can collect and share IP addresses and approximate location inferred from them, app/ad interactions, diagnostic information, and device or account identifiers for advertising, analytics and fraud prevention. What is processed depends on age treatment, consent choices, Android controls, serving configuration and Google’s policies.

For eligible players, UMP checks whether advertising consent is needed and presents choices where required. Privacy options is available in Settings when required by Google’s consent system. Refusal or an unavailable ad does not prevent gameplay. Android also provides advertising-ID controls.

The permanent Remove ads purchase blocks new ad requests and display and clears cached ads after verified ownership. Previously verified owners skip advertising startup on subsequent launches. Removing ads and managing consent are separate choices.

Read Google’s privacy policy and Google Mobile Ads data disclosures.

4. Google Play purchases and verification

Google Play processes the optional one-time Remove ads purchase and manages your payment information. Geniosity does not receive your payment-card details. Use the purchasing Play account to restore the purchase; there is no separate Echo login.

Echo sends the purchase token, fixed app package and product identifier over HTTPS to Geniosity’s purchase-verification service. The service checks Google Play’s authoritative purchase state, acknowledges completed purchases, retries when needed and reconciles refunds or revocations. Purchase tokens are sensitive: do not send them in support messages.

The service stores a SHA-256 token hash, entitlement status, acknowledgement state, verification time and retry timing. While an owned purchase still needs acknowledgement, it retains an AES-256-GCM encrypted token using an externally managed encryption key. The encrypted token is removed from the active purchase record after acknowledgement or revocation.

The entitlement records do not include your age, name, email, Play-account identity, scores, order identifier, price or region. Google Cloud hosts the service, storage and purchase-notification queue. Unprocessed Google Play purchase notifications can include purchase tokens and are retained in Pub/Sub for up to seven days under Google’s encryption at rest. Google Play and Google Cloud process information to operate their services, including technical request metadata.

A purchase token acts as a limited capability for verification, rather than proof of a person’s identity. The service restricts access to verification and uses rate limits; it cannot establish who you are solely from token possession.

5. Retention, deletion and your choices

Local data: preferences, scores, age classification and purchase cache remain until you clear Echo’s storage or uninstall it. Clearing local data does not delete Google Play’s purchase records or cancel your permanent purchase.

Purchase service: active permanent-entitlement records and revoked token-hash records are retained while the product and verification service are supported, so purchases can be restored and revoked tokens cannot be reused. Pending and not-owned records are deleted after 30 days. Purchase-notification deduplication metadata is retained for seven days. Global and hashed-purchase-token rate-limit counters expire after ten minutes. Rate limiting uses no IP-derived source keys; raw IP addresses are not stored in the app’s purchase database.

Infrastructure: Google Cloud may keep request metadata such as IP addresses in platform logs. In Echo’s dedicated Google Cloud project, operational logs are retained for 30 days and required audit logs for 400 days. These platform logs are separate from purchase-database records and their deletion rules.

Support email: we use your email address, correspondence and any details or attachments you choose to send to respond to your request. Support may ask privately for a Google Play order number or redacted receipt to locate a purchase record and check a request; do not send raw purchase tokens or payment-card details.

Support email retention: our support address uses Google Workspace. We keep support correspondence, replies and attachments for two years after an enquiry is closed, then delete Echo support copies during the next monthly review. This period applies to support email, separately from permanent-entitlement records. A documented legal obligation or unresolved dispute may require limited longer retention. Deleted mail may remain temporarily in Google’s recovery systems. This is a manual review process, not automatic email deletion.

You may contact Geniosity to ask about access, correction or deletion of information we hold. Requests are handled individually. Some limited purchase or revoked-token records may need to remain for restoration, fraud prevention or legal obligations. There is no automated Echo-account deletion flow because Echo does not create accounts.

Google Play purchases, Google advertising data and Android settings are subject to Google’s own controls and retention policies. See Google Play support and Google’s ad privacy controls.

6. Security, sharing and international services

Echo uses HTTPS for purchase verification. The purchase service avoids logging raw tokens, request bodies and purchase-error objects, limits its runtime access and uses encrypted token storage only when acknowledgement requires it. No security measure can guarantee absolute protection.

Information is shared with Google AdMob/UMP, Google Play, Google Cloud and the chosen support-email provider as needed for the functions described above. These providers may process information in other countries. Geniosity does not sell the local game information or purchase-service records.

7. This website

This static website uses no optional analytics, advertising cookies or marketing forms. Its hosting provider, Firebase Hosting, processes network request information to deliver and protect the website. Following a link to another service brings you to that service’s privacy practices.

8. Changes to this policy

We will update this page when Echo’s data practices change and revise the policy date. Material changes that require notice or a new choice will be communicated through the app or another suitable channel.