About TABANJA and age limits
This policy covers guest play, accounts and game services at tabanja.io. An independent developer based in Jordan operates TABANJA and decides how player data is used. TABANJA is not a registered company.
You must be at least 18 years old to use TABANJA, or meet a higher minimum age where applicable law requires. Anyone under 18 must not use the service. TABANJA does not verify age; Google sign-in is not an age check.
Google sign-in
Guest play does not need Google sign-in. For accounts, TABANJA requests openid, email and profile to verify your identity and set up your profile. The server receives your Google identifier and issuer, plus your email, verification status and name when provided.
Your identifier, issuer and optional email metadata are stored with your account. Your Google name can suggest a Player Name; you can change it before confirming registration. Email is not used to match or merge accounts. Eligible guest statistics, progress, wallet and base appearance transfer to a new account, but do not merge into an existing one.
Google data is used for sign-in and profile setup, not advertising. TABANJA does not receive your Google password, use your profile photo, or request Gmail, contacts or Drive access. Google tokens are used for server-side verification, not saved in browser storage or the database; no offline access or refresh tokens are requested. Google operates under its own Privacy Policy.
Player data and saved progress
TABANJA handles the following to run accounts, matches, reconnection, statistics, rewards and checks against unauthorized actions:
- Account identifiers, Player Number, internal username, chosen Player Name, appearance, owned items, loadout and profile timestamps.
- Room participation, match and round results, scores, wins/losses, forfeits, ratings, level progress, rewards and timestamps.
- Coin and Diamond balances, conversions, item exchanges and private Coin Challenge records. There are no real-money purchases or payment-card collection.
- Temporary guest identifiers, session credentials, gameplay inputs, live state and connection status.
- Network information, such as IP addresses and request headers, needed to deliver the service, and operational error logs. Production infrastructure logging still needs confirmation.
Data is collected when you load the site, connect, sign in or use a feature. A Google identifier is needed for an account; email and a suggested Google name are optional. You can choose another Player Name.
What other players can see
Opponents can see your Player Name, appearance, displayed level and match activity. The public leaderboard API provides names, Player Numbers, levels, qualified wins/losses, Rank Points and ranks, plus equipped cosmetic appearance for the Top 3; its interface hides Player Numbers. It does not expose your Google email, Google identifier or session credentials. Avoid private information in your Player Name.
Storage, sharing and security
Accounts, sessions, profiles, match history, progress, wallet and ownership records use the backend's PostgreSQL database. Live rooms, matches, guest progress and pending sign-in flows also use server memory. Google handles sign-in; hosting and database services process information needed to provide TABANJA, including stored Google identity metadata. There is no implemented data-sale integration.
Server-side identity checks, hashed stored session credentials, secure production cookies, origin checks and server validation help protect data. No system guarantees complete security. Production providers, storage countries, international-transfer safeguards, backups, log retention and encryption at rest remain unconfirmed.
Retention and account deletion
Account and game records remain after logout. No automatic retention or deletion period is configured for persistent records. Temporary guest progress expires after 24 hours or 30 minutes of disconnected inactivity, and is lost on a backend restart. Persistent guest match history and completed account transfers are separate and may remain.
There is no self-service account deletion or data export, and no published privacy-request channel yet. Retention rules, backup deletion and a working request process must be finalized before production publication. This limitation does not remove applicable legal obligations.
You can remove TABANJA from your Google Account connections. This may prevent future Google sign-in; it does not delete TABANJA records or end an existing TABANJA session. Use Logout to end the current session.
Privacy rights and contact
Depending on applicable law, you may have rights to access, correct, delete or receive a copy of your data, restrict or object to processing, withdraw consent, or complain to a data-protection authority. Conditions and exceptions may apply. You can edit your Player Name subject to its cooldown and change supported appearance settings in the game.
The operator's legal name and verified contact details are not yet published. A channel and identity-checking process for privacy and account requests are pending; applicable rights and response deadlines still apply. No unverified email or deletion process is offered here.
Google authorization and reading this policy do not replace any separate consent required by law. Updates appear with the date above; any legally required notice or consent still applies. See the Terms of Service.