At registration
When registering for tbajl, name, phone number, and basic identity information are provided.
Effective date: July 2026
This page shows tbajl App's privacy policy, data protection, cookies, and user rights together; for Dhaka and Bangladesh users, what data is kept, for how long, and how it can be deleted is written in plain language.
If interested tbajl App Also view the page that includes steps to start the mobile app, APK, and login.
Personal data is kept separate, and Dhaka users' account history is kept with restricted access.
Cookies are used to remember sessions, language, and device settings; you can also disable them from the browser.
You can view, correct, or request deletion of your data; once verification is complete, the team responds quickly.
Inactive accounts are archived first after long inactivity, then moved for permanent deletion if needed.
When registering for tbajl, name, phone number, and basic identity information are provided.
Your device type, browser, and login time are automatically recorded.
Failed login attempts on tbajl are detected to quickly identify unusual access.
Country-based settings use city signals to understand region, such as the Dhaka area for quick session matching.
Most of this information is used for service operations; for example, to keep the session when going to banking tabs with bKash or Nagad.
If an account has no activity for more than 90 days, it is considered inactive; then data is not deleted immediately, it goes to the archive first.
This step isn't lax; the system first checks the last login, device, and session history, then sets the archive flag.
Sometimes a user only watches matches for weeks and does not deposit anything; still, before archiving, extra warning messages are sent.
The system first checks inactivity time, then matches the linked phone and the device's recent logs.
Archiving does not close the main account, but old sessions, cookies, and temporary cache are cleared.
Only the minimum necessary information is kept to maintain data protection, and future complaints are easier to review.
Rocket or Nagad-linked users also follow the same rules; even if the payment method is different, the archive policy does not change.
After tbajl login, usually a verification code is required; often the account opens if the old number is correct.
If the number changes, the support team verifies identity to help; this usually ends in two steps, and no form needs to be filled in midway.
Many users complete the task on mobile; in busy areas like Dhaka, it’s faster because session verification usually takes only a few minutes.
You can request data deletion, but some minimum logs may be kept for legal or security reasons for a few days.
A user's rights here are threefold: viewing, correcting, and deleting; if an old email or number is wrong, there is also an option to update it.
If you need more tbajl Help Center See separate answers there about login, verification, and account archiving
If you have questions about privacy tbajl Contact Page When contacting support, you may typically be asked for your account number, last login time, and a brief description of the problem.
Bottom line: tbajl App privacy policy, cookies and data protection rules are clear; your rights are also open, so if needed you can take the next step yourself.