TK11 App Privacy Policy
This page clearly explains TK11 App data protection, cookies, and user rights. Many users in Dhaka log in quickly, so see in plain language how the data is captured
Download TK11 APK
Card Data Tokenization
When you open TK11 App at night to view payments, the real card number is not visible; that's the purpose of tokenization
We store sensitive payment data as tokens, so the number, expiry, and verification code stay separate and are not directly visible; if you use bKash, Nagad, or Rocket, the processor's secure records remain, not full details
Parts kept separate
The actual card or wallet number, verification tokens, and session IDs are kept on separate layers, making data matching difficult by mistake
This method works after TK11 Download on first setup, not Lahore; for Bangladeshi users on Dhaka networks, it also works on regular mobile devices
TK11 App PCI Scope
For users with TK11 Register, the minimum data should be exposed, so the PCI scope is kept small
We process payments on a separate path, so card data does not enter the main app layer directly, and verification occurs in a restricted environment, making security controls easier and audits faster
Limited access, clear logs
Only authorized systems access sensitive parts; logs show who viewed what, with small but clear records
This is not just a technical matter; it helps maintain user trust when viewing transactions on Rocket or Nagad
Processors list
When you log in at night to view payments in TK11, it is necessary to know which processor is involved; in Bangladesh we see three known routes: bKash, Nagad, and Rocket
These processors store data under different policies; TK11 App only takes the necessary parts, such as transaction reference and status; many Dhaka users work with small data packets, so a lightweight design is important here
The bKash route quickly pairs with the TK11 App
Nagad-based verification usually happens in fewer steps
Rocket records have timestamps and references kept separate
How chargeback data is captured
When a payment is questioned, chargeback data is needed; then the transaction date, reference, and verification history are viewed
We do not pull the full account history; only the relevant parts are kept, so investigations are quick and unnecessary data is not spread
Small but useful verification records
A single request usually takes 13 business days, allowing the support team, processors, and user to view the same record
For users with TK11 Register, this document is useful later; if needed, the same information can be cross-checked with the TK11 Login history
Crypto wallet data
At the last login of the night, if someone views the wallet, only the balance and reference are needed; we do not store the full wallet contents
If crypto-type wallet data exists, it is also kept as tokens; transfer requests, address components, and verification status are kept in separate records
Storing data this way reduces issues, and Bangladeshi users can easily understand which parts are TK11 App's and which belong to external wallets
Your rights and contact
You can request to view, correct, or delete your data; identity verification may be required for security
If you have questions about privacy, go to the TK11 Contact page, write there if you wish, and you will receive a response according to Dhaka time
Finally, privacy in the TK11 App means clear rules; information about TK11 Download, TK11 Login, and TK11 Register is also covered by this policy
Privacy contact