Privacy policy
Version 2026-11-07-v2 · 7 November 2026 · Development and test versions
This policy explains how Enciu Cezar (the developer and data controller) handles information in Emberbound, including Android test versions. Privacy questions and rights requests: czryourbro@gmail.com.
1. Information used by the game
- Age setup and terms: a neutral birth-date entry derives a coarse age profile on the device. The full birth date is discarded and is not sent to our server or advertisers. The device stores the profile, agreement version, acknowledgement and review timestamps. The profile is reviewed after one year or a material policy change. Eligible online accounts also have a server-timestamped record of the terms version and any guardian acknowledgement. These are self-declarations, not identity verification or verified parental consent.
- On your device: progress, equipment, currency balances, settings, language, sound preferences and timestamps needed for saving, daily rewards and offline progress. An offline game can run without an online account.
- Online accounts: when you sign in through Google Play Games, Google authentication identifiers/tokens are used to authenticate you. Our game server stores an internal account ID, linked Google identity, cloud save and account/session information. The game does not receive your Google password.
- Online play: we use your chosen player name and progress to provide cloud saves and rewards. Guilds, chat, world bosses, leaderboards and raids are disabled in this release. Older accounts may still have historical social records associated with them. We handle those records when deleting an account.
- Rewarded game ads: some test builds use a curated player that displays only manually approved game campaigns hosted on our HTTPS service. When the game downloads an approved image, our hosting provider processes ordinary connection information such as IP address and technical request data. The campaign is bound to an internal account and a one-time server intent. We do not send that identity to the advertiser and do not use an ad auction, personalized ad network or third-party ad-consent form for this player. An empty or unavailable catalog fails closed without substituting another ad provider.
- Network advertising in the Play Alpha: when rewarded advertising is enabled, Google AdMob runs an auction that can include Unity Ads. Their SDKs may process IP addresses (including approximate location inferred from IP), device and advertising identifiers, app and ad interactions, and diagnostic or crash information for ad delivery, measurement, troubleshooting and fraud prevention. Unity may process purchase history where available. The game requests non-personalized, general-audience ads. The networks receive technical information when their SDKs run, even if you do not click an advertisement. For network rewards the game sends Google a game-account identifier and one-time reward identifier. Google returns them in a signed completion callback so our server can grant the reward once.
- Reward verification: the curated player reports completion or early dismissal to our own server using its one-time intent. Our server validates the account/campaign binding, completion record, anti-replay record and daily limits before granting a reward. These first-party records do not independently prove human attention and are not represented as third-party verification.
- Purchases, when enabled: Google Play handles prices and payment details. To verify and restore purchases, the game sends Google purchase receipts/tokens and obfuscated game-account/purchase-intent identifiers to our server for verification with Google. We retain product/entitlement records and transaction hashes to deliver rewards, prevent duplicate redemption and adjust entitlements after a Google-reported refund or revocation. We do not receive your card or bank-account details through checkout.
- Support and service operation: emails and information you voluntarily send to support, and technical connection/security information processed by hosting and game services, including IP addresses and error information.
- Ad service diagnostics: eligible signed-in profiles submit bounded first-party counters for ad lifecycle events, placement, source and timing. In network builds, an impression may also produce an estimated ad-value event. Hosted campaigns do not produce that event. Payloads exclude birth dates, age profiles, Google IDs, ad response IDs and reward tokens. Counters are private account-owned operational records, not audited financial statements, third-party verification or independent proof of a human view; no third-party analytics service receives them. We retain a bounded rolling window of up to 30 daily aggregates, pruning older days on a subsequent submission; inactive records are removed with account deletion.
- Optional local playtest journal: if you enable it in settings, gameplay/UI events are recorded locally. It is not automatically sent to us. You can choose to export it and share the file yourself.
The game does not request your home address, contacts, microphone, camera or precise GPS location. In-game balances are game data, not a bank account. Google services process payment information for purchases handled through their services; do not send bank details to our support email.
2. Why we use information
We use account and game data to provide requested sign-in, cloud saves and online features; award earned rewards; diagnose advertising delivery and reward failures using bounded counters; maintain agreement records; respond to support and deletion requests; reconcile refunded purchases; and protect the service from fraud and abuse. These purposes rely on providing the service you request and our legitimate interests in operating and securing it. Where consent is required for network advertising, the consent form explains the choices and providers before ads can be requested.
3. Providers and sharing
We use Google Play Games for Google sign-in and Google Play for purchases and optional, user-initiated store links. Firebase App Distribution distributes invited test builds and processes tester/account and distribution information. Our online game services and curated campaign images run on Oracle-hosted infrastructure using Nakama, a database and our HTTPS service. Information necessary to operate these features is processed by those services. Other players see only information exposed by the online features described above, not your authentication tokens or private cloud save. The curated player does not share your game identity with the advertised game's developer; if you open its Google Play listing, Google and that listing's provider handle their own processing.
For the mediated Alpha, Google and its bidding partner Unity process advertising information as described above. See Unity’s game player privacy policy. First-party ad delivery still involves ordinary hosting and connection processing. Providers may process information in countries other than yours under their applicable arrangements and safeguards. See Google's privacy policy, Firebase privacy information and Oracle privacy information.
4. Storage and retention
Device data remains until removed through app data controls, uninstalling the app, or the game's applicable reset controls. Deleting local data does not by itself delete an online account. Online account/private save data is kept while needed for the account and removed when the account is deleted, subject to information reasonably needed for legal obligations, resolving disputes and security.
Deleting the account removes its historical Nakama chat messages in the tested server version. Copies inside reports submitted by another account may remain, including the original author identifier and text. Information already seen or copied by other players cannot be withdrawn automatically. Contact us to request review of that content. Minimal anti-replay transaction hashes and operational/security records may be retained for abuse prevention; they are not a reusable reward and do not contain your Google password. We review retention according to these purposes and applicable obligations. This development service does not promise a specific backup recovery period or continuous availability.
5. Children and privacy choices
The current development service uses a neutral age setup before online or advertising initialization. Profiles declared under 16 use offline play without online features, purchases or advertising. For eligible profiles, network builds request non-personalized, general-audience inventory and send the applicable age flags. Category controls favour games. The networks choose the ads they deliver. Minor profiles require a parent/guardian acknowledgement of the terms; this acknowledgement is not used as verified parental consent to enable under-16 data collection. Unknown, invalid or expired setup cannot start online, purchase or ad services. Avoid including personal contact details in your chosen player name. A parent or guardian may contact us about a child's information or request deletion.
Ads are optional. Network builds use Google’s consent flow before requesting ads and show Ad privacy options in Settings where required. Hosted-campaign builds use a separate first-party player. You can use the account deletion controls and device/app controls described here. Store age/content classifications are determined separately by the relevant store.
6. Your rights and requests
Depending on the law that applies, you may request access, correction, deletion, restriction, portability or object to relevant processing; you may withdraw consent where processing relies on it. Contact czryourbro@gmail.com. We may ask for proportionate information to verify account ownership, such as your player/account ID and a request from the account-associated address. Do not send passwords, payment credentials or identity documents unless a specific lawful process has been explained. We respond without undue delay, ordinarily within one month. Any necessary lawful extension due to complexity or number of requests is explained within the first month. Withdrawing consent does not affect the lawfulness of earlier processing. You may also contact your local data protection authority, including Romania's ANSPDCP where applicable.
7. Security and changes
Public game connections use HTTPS. Access controls, private server completion records and anti-replay controls protect relevant operations. No service can guarantee absolute security. The game is in development, and features or providers can change. Material changes to the processing described here will be reflected in an updated policy and, where required, appropriate notice or choices.