Provided by: Omer Hodzic
Privacy and deletion contact: omerhodzic123@gmail.com
The Deception Box is a multiplayer social deduction game.
Information the app uses
The app creates a Firebase guest identifier when it needs one for multiplayer. You do not have to provide an email address or password. This identifier lets the app recognize your player, connect you to a room, and associate your game activity. It is a stable app identifier, not an anonymous identifier.
When you host or join a game, the app uses your chosen display name, room membership and presence, game setup, role and role changes, actions and choices, votes, and game results. Room codes and records needed to synchronize the game are also processed. People in your room can see the information needed to play, such as player names and game progress. A technical player ID is also included in room records that other players' apps can read, even though the game shows them your chosen name instead of that ID. Private roles and choices are restricted to the relevant player and game service unless the game rules reveal them.
If you choose to use the store features to purchase or restore an expansion, the app sends your Firebase guest identifier to RevenueCat so that it can associate purchase and entitlement information with your game account. RevenueCat and Apple or Google process product, transaction, receipt or purchase-token, and entitlement information for purchase and restore services. RevenueCat may also use purchase information and a broad country inferred from network or transaction information for analytics and reporting. Its customer profile may include a last-seen country derived from an IP address when transaction country is unavailable. The app does not receive your store payment-card details and does not request GPS or device-location permission.
Firebase and Google Cloud provide authentication, multiplayer storage, and server processing. These services, RevenueCat, Apple, and Google may process network, request, authentication, purchase, security, and service-diagnostic information needed to provide their services, including analytics and reporting about service use and performance. For example, network connections can expose an IP address, and Firebase services may use installation or request identifiers. Each provider also handles information under its own privacy terms.
How information is used and shared
We use this information to create and synchronize multiplayer games, reconnect players, authorize game actions, provide purchases and restores, protect service integrity, troubleshoot service operation, and handle support and deletion requests.
Game information that is needed by your room is shared with the other people playing that game. Firebase and Google Cloud store or process data for us as service providers. RevenueCat processes information for purchase and entitlement services. Apple App Store or Google Play processes payments and store transactions under the store you use. Service-provider processing is separate from information intentionally shown to other players.
Retention and security
Room data becomes eligible for cleanup after a game reaches Results, after every player has been offline for five minutes, or when the room reaches its 24-hour limit. Cleanup may still take longer because of retries, outages, or a processing backlog. An active game may remain while players finish or until the room reaches that limit. These room-cleanup points are not a fixed account-deletion deadline.
After a deletion request completes, its status can be checked for seven days. The minimal status and related deletion metadata then become eligible for scheduled cleanup; outages, backlogs or cleanup failures can delay removal. Firebase, Google Cloud, RevenueCat, Apple, and Google may retain service records, logs, transaction records, or backups under their own processes and retention periods. Deleting an app record does not mean that every provider backup or log is immediately erased. Firebase says some authentication and installation data can take up to 180 days to be removed from live and backup systems after deletion. RevenueCat may process an accepted deletion request asynchronously.
We use access controls and service security features to protect information. No online service can guarantee absolute security.
Requesting account and data deletion
If your app version provides Settings → ACCOUNT AND DATA → DELETE ACCOUNT AND DATA, you can use that option to submit a request and check its progress. If that option is unavailable or you cannot use the app, email omerhodzic123@gmail.com with the subject “The Deception Box account/data deletion request.” You do not need to reinstall the app just to contact us. We may ask for limited information to locate the account and verify that you control it. A display name or Firebase identifier by itself does not prove account ownership.
Do not email a password, payment details, Firebase UID, or private deletion-status receipt. Keep the status receipt private; it can be used to check the request after sign-in has ended. A request can remain pending while an active game is safely resolved or while a service-provider or operational check is required. If we cannot verify control of the account, we will not delete an account based only on a name or identifier.
A completed request removes the account and associated app data that the controlled deletion process can identify and verify. RevenueCat may acknowledge a deletion request before its processing is finished. Deleting your app account does not cancel a subscription, issue a refund, or erase Apple or Google store transaction records. Contact the relevant store about subscriptions, billing, or refunds.
Uninstalling the app removes it from your device but does not itself request deletion of your server account or game data.
Contact and updates
For privacy questions or deletion requests, contact omerhodzic123@gmail.com. We will update this policy when our information practices or service providers change.