khaka88 Privacy Policy: How We Handle Account Details
Your account details, wallet records and support conversations are handled under one written policy, and this page sets it out in plain terms. khaka88 keeps that policy in a single place so you can read what is collected, why it is held and how to ask for a change. Access to any route depends on your local law and eligible regions, so read the terms shown in your signed-in account before you open a wallet step.
Account data explained
Wallet records
Cookies and device data
Contact routes
DATA HANDLING TERMS
What We Hold After a Nagad Deposit
The policy is written for how accounts actually work here: you open an account, you complete the steps shown in it, you move money through Nagad or Bank Transfer, and each of those steps leaves a record. We keep those records so your wallet balance, your transfer history and your support conversations stay consistent when you come back on another device. Nothing on this page overrides your local law. Where local rules ask for something different, the stricter reading applies for your region, and access to any route still depends on your local law and eligible regions. That is why we ask you to read this page alongside the terms shown in your signed-in account rather than treating it as a standalone promise. In practice, the policy covers the details you type in yourself — your name, contact number, email and account credentials — plus the references a local wallet returns when a Nagad transfer or a bank entry is posted. It also covers the technical details a browser sends, such as device type and session identifiers, because those are what let us recognise a sign-in you started and close a session you did not. We do not sell those records. Sharing is limited to the processors that make a wallet transfer or a support reply work, and to any authority that local law requires us to answer. Retention follows the same logic: we hold what a transfer or a dispute needs, then remove the rest on a set schedule.
Nagad
Bank Transfer
bKash
Rocket
Account wallet
WHERE THIS APPLIES
Where This Policy Applies in Bangladesh
Scope is narrower than it looks. The policy follows your account, not your device, so the same rules apply whether you sign in from a phone browser or from a computer at home. It starts when you create an account and continues while that account stays open; a closed account falls under the retention part of the policy rather than dropping out of it. Two things sit outside it. Game content from studios such as Pragmatic Play and PG Soft runs inside our lobby, but this page describes how we handle your details, not how a title is built. And a payment app or bank page you open from the wallet is operated by that provider, under its own policy. The distinction matters when you have a question. If a Nagad transfer shows in your wallet but the wallet app shows nothing, that is our record to check. If the provider blocks the transfer at its end, the answer comes from that provider's support, because we never see the screen you were on. Knowing which side owns the question saves you a day.
Account access
Sign-in details, contact number, email and the device session records that keep your login working sit inside the policy. This is the area most questions touch, because it covers what you type when you open an account and what we hold to recognise you next time.
Wallet transactions
Every Nagad transfer and Bank Transfer posted to your account leaves a reference we keep for matching and disputes. The policy explains what that reference contains, who inside the service can look at it, and how long it stays on file after the transfer settles.
Site content
Lobby pages, game listings and the studio titles shown there are part of the service this policy supports, but the policy does not govern a game's own mechanics. It covers how your details interact with the site, not how a title or its features are built.
Third-party services
A wallet app, a bank page or any service you open from our site runs on that provider's terms, not ours. We decide what to pass to them, and the policy explains that hand-off, but their handling of your details sits outside our control.
YOUR DATA CHOICES
Checking and Correcting Your Account Records
You have four practical moves under the policy, and none of them need a lawyer or a long email. The first is reading: your signed-in account area shows the details we hold, and the policy page you are on tells you why each field is there. The second is correcting, because a mistyped contact number for a Nagad transfer should not sit on the record uncorrected. The third is asking. If a paragraph here does not match what you expected, put the question to us through the contact route published on this site and quote the section you are reading. The fourth is requesting removal where the policy allows it; some records tied to a wallet transfer have to stay for as long as the transaction or a dispute needs them, so removal is a decision we confirm with you rather than a switch you flip. We answer the question first and edit second. If you ask for a correction, we check the record with you before changing anything that affects your wallet.
Read your own record
Open the account area while signed in and the details you gave us are laid out in the profile fields. Matching those fields against this policy is the quickest way to spot something wrong, and it takes a minute rather than a message.
Correct what is wrong
Contact number, email and the name tied to your wallet are editable through the account route. If a field will not change from your side, ask us with the record open and we will examine it against the policy.
Ask about a section
Quote the heading you are reading when you send a privacy question. It shows us which part of the policy you want explained and lets us answer the exact point instead of sending back a paragraph you already have in front of you.
Request removal or a hold
Where the policy lets us delete something, you can ask for it. Records attached to a Nagad transfer or a Bank Transfer stay while the transaction or a dispute needs them, and we will tell you which of the two applies to your request.
PRIVACY CONTACT ROUTES
Reaching Us About a Privacy Question
Privacy questions travel through the same routes as every other account question, which keeps them attached to your record instead of floating loose in an inbox. Use the contact route published on this site, and write from the email or contact number already on your account so we can match the message without asking you to prove who you are twice. Start in the account area when the question is about a specific field. Your profile shows what we hold, and your wallet history shows each Nagad transfer or Bank Transfer with its reference attached. Copy that reference before you write, because it turns a general worry into a question we can check against an actual record. For…ding rather than your own details, say so in the first line and quote the section you are reading. What we will not do is guess: where a request depends on how your local law reads, we say that plainly. Access to any route remains subject to your local law and eligible regions.
Site contact route
The contact route published on this site is where privacy questions land. Write from the email or number already on your account, name the section you are asking about, and keep the message to the point so the reply matches what you actually asked.
Signed-in account area
Your profile fields are the quickest way to confirm what we hold. Compare them against this page yourself before writing; if a detail looks out of date, tell us which field and what it should say, and we will check it.
Wallet history
Each posted deposit carries a reference in your wallet history. Copy that reference into your message when a Nagad or Bank Transfer question is the reason you are writing, and the answer can be tied to the real record rather than described in general terms.
HOW WE PROTECT DATA
How khaka88 Handles Cookies and Access
Data handling here is deliberately uneventful. Access to account records is limited to the people who need it to answer a wallet question or run a support reply, and each look is tied to a signed-in session. We do not read your details to build marketing lists, and we do not pass them to a studio or an advertiser. Cookies do a small, specific job: they keep you signed in between pages, remember your language and region, and tell us when a session has gone stale so it can be closed. Blocking them in your browser is your call — account pages still load, but you will be signed out more often and some wallet views may not hold. Security is a shared habit, not something we can promise for you. Use a password you do not reuse elsewhere, sign out on a shared phone, and check any message asking for your sign-in details with us first. Retention follows a set schedule: transfer references stay while a dispute or local rule needs them, profile details stay while the account is open, and the rest is cleared. When the wording changes, the version published here is the one that applies.
Account details
Profile fields, sign-in credentials and the contact number tied to your wallet sit in one record. Only the people handling your question open it, and each look is attached to a signed-in session rather than a shared login somebody else can borrow.
Cookies and sessions
Small files keep a signed-in session alive between pages, remember your language and region, and flag a session that has gone stale. You can block them in the browser; the site still loads, though you will re-enter your sign-in more often.
Keeping your login safe
Use a password that is not used anywhere else, sign out on a shared phone, and treat any message asking for your sign-in details as something to check with us first. Those three habits prevent most account problems before they start.
Retention and changes
Transfer references stay while a dispute or a local rule needs them, profile details stay while the account is open, and the rest is cleared on a schedule. When the wording changes, the version on this page is the one that applies.
PRIVACY QUESTIONS
Privacy Questions We Get Asked
The questions below come up most often from people opening a wallet step for the first time, so they are answered here in the same plain register as the rest of the page. Each answer points to the part of your account where you can confirm it yourself rather than asking you to take our word for it. If your question is about a specific transfer, the reference in your wallet history is the detail that makes a reply possible; without it we can only speak in general terms. Anything the policy leaves to your local law is marked as such, and nothing on this page should be read as legal advice for your region.
What does the khaka88 privacy policy cover?
It sets out what we hold when you open an account — profile fields, sign-in details, wallet references from Nagad or Bank Transfer, and the browser details a session needs. It also explains why each record is kept, who inside the service can see it, and how you can ask for a change.
Can I see the details held on my account?
Yes. Sign in and your profile fields show the name, contact number and email we hold, while the wallet history lists each posted transfer with its reference. Compare those against this page; if a field looks wrong, tell us which one and what it should say.
Do you share my details with anyone?
Only where a step needs it. A wallet processor sees what a Nagad or Bank Transfer requires, a support route sees the message you send, and an authority sees what local law compels us to hand over. We do not sell records or pass them to studios and advertisers.
How do cookies affect my sign-in?
Cookies keep you signed in between pages, remember your language and region, and let a stale session close rather than linger. Block them and the pages still load, but you will be asked to sign in more often and some wallet views may not hold their state.
What happens to my details if I close my account?
The account closes, but records tied to a transfer or a dispute stay for as long as that transfer or a local rule requires. Everything else is cleared on our retention schedule. Ask us and we will tell you which records would remain in your case.
How do I ask for a correction or removal?
Use the contact route published on this site and quote the section you are reading. Write from the email or number already on your account so we can find the record, and we will confirm what can be corrected or removed under the policy before anything changes.
Sports / Slots