tbjee App Privacy Policy
All apps ask for data; the question is how clearly this page explains how tbjee App's data is stored, what cookies do, and what your rights are, laid out openly
What data tbjee App stores
Many sites put everything in one line, then trouble begins; tbjee shows data types separately, making it easier to understand; many Dhaka users operate accounts with bKash or Nagad, where verification data and session data are kept separate from each other
Registration, tbjee Login, device identification, and help message sections are used when needed so the user can easily understand spending, limits, and profile; that's the main point
Account information
Name, phone, and login information keep the account secure
Device information
Model and browser information helps keep the session
Support history
If old tickets exist, resolution is faster, typically 2 steps
How data protection works
Most users only hear the word 'secure', but real trust comes from encryption, access control, and limited-view measures; on tbjee App those things work together
The security team from Dhaka also separately reviews support requests, and verification notes related to Rocket, Nagad, and bKash are opened only when needed
Three main security steps
- Encryption in data transfer
- Limited team sees sensitive parts
- Suspicious sessions are identified quickly
Cookies and session data
Cookies can annoy, but not all cookies are the same; some remember language, session, and preferences, so you do not have to adjust settings each time
tbjee cookies are usually small; for example, after tbjee Download, logging in again may remember the previous screen; cookies can also be controlled from the browser settings on device
Session cookie
Keeps login alive; expires when the browser is closed
Preference cookie
Remembers language and interface preferences, so one fewer click is needed
Data retention period
Here there is no quick delete story; some data stays open until the account is closed, and some is kept longer due to legal or security reasons; most retention times depend on data type and need
Active accounts, payment notes, and support records are not kept in one line; when work ends, unnecessary parts are trimmed to avoid extra data
Common retention types
- Session log: Short-term
- Verification notes: required
- Support records: specific period
What happens when account closes
Many think closing an account means everything will be deleted; in reality some parts are restricted immediately, while others remain as records for security, fraud prevention, account auditing, and reconciliation purposes over time
If you register tbjee and later change your mind, you can write to the support team to request account closure; the process is simple
Your rights and controls
The real strength of privacy is user control: what data you want to view, fix, or limit; those rights are yours
You can request access, correction, update, or deletion; providing the same account information when contacting support speeds things up, especially for busy users in Dhaka city
Data access rights
You can see what data exists
Right to rectify
If errors exist, you may request correction
Right to delete
Where applicable, you can request data reduction
Contact and support
If you have privacy questions, don't assume; ask on the tbjee Contact page to speak with support, and if needed tbjee Login related information can be verified
One last word: tbjee App data management is clear, limited, purpose-driven, so users know what is kept, why, and when it can be reduced