Reference

Privacy Policy for Your ktk688 Account

One page holds the whole record of what your ktk688 account stores and why. We collect the fields the cashier desk needs, your name, mobile number and the wallet you link, and we keep deposit history because bKash, Nagad and Rocket transfers have to…

Account walletbKashNagadRocketMobile access
ktk688 Privacy Policy for Your ktk688 Account
CARE OF YOUR RECORD

How We Handle Account Data

Everything in this policy describes a record you can ask to see. Session data comes from your handset, transaction rows come from the payment channel, and both sit under your mobile number. Support opens that record only for a request, and every open is logged. Cookies cover sign-in and language, not advertising profiles. Retention follows local rules, and when you ask, we tell you what is still on file.

What We Store Account fields, linked wallet numbers and bet history sit in one record under your mobile number. Support opens it only for a request, and each open is written to a log.
Cookies We Set A sign-in cookie keeps your session alive and a preference cookie remembers your language. Neither builds an advertising profile of you across other websites, and both clear from your browser settings.
Guarding the Login The one-time code goes to your registered number, so a leaked password alone will not open the account. Change that number through a verified request, never through chat alone.
How Long Records Stay Transaction rows are held for the period local rules set and then leave our live systems. Ask us to confirm what is still on file, and we will tell you plainly.
ASK US DIRECTLY

Where to Send a Privacy Request

A policy question shouldn't need a ticket number first. Message us from the number registered on your account and it reaches the queue that reads account records, the same team that checks a Nagad transfer that hasn't shown up. Ask for a copy, a correction or a deletion; we reply in writing and name the field we acted on. If we can't act, we say which rule stops us.

Privacy Request Send the request from the mobile number registered on your account and put privacy in the subject line, so it reaches the queue that reads account records rather than general wallet help.
Live Chat Desk Chat treats a policy question like a bKash deposit that has not landed: we open the account, read the record and reply with what we actually see there.
Account Correction Wrong spelling, or an old Nagad number still on the record? Tell chat the field and the correct value; we log the change against your account and confirm it back in writing.

Data Questions We Hear Most

These are the questions that land in our inbox most often, answered the way support answers them in chat. If yours is about a specific bKash or Rocket transfer, have the transaction ID ready, since it shortens the conversation. Anything not covered here can go to the same address, and we will answer in writing. None of it changes your rights over the record: a copy, a correction or a deletion request works the same way whatever the question was.

Your name, the date of birth you declare, mobile number and the wallet you link, whether bKash, Nagad, Rocket or Upay, plus session data such as phone model, browser and IP address.

Yes. Send the request from your registered mobile number and we return a written copy of the account record, including deposit history tied to your linked wallet.

Only the payment channel handling that transfer sees it, plus auditors where local rules require a record. We do not sell account details to outside lists.

Tell support which field is wrong and what it should say. We verify the request from your registered number, update the record, then confirm the change back to you in writing.

The sign-in cookie is what keeps you logged in; without it you are sent back to the login page. The language cookie can be cleared from your browser settings.

Access depends on local law and eligible regions where you live. Where those rules differ from ours, your local law sets what we may hold and for how long.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.