Reference

Open an Account Knowing What We Hold

One account, one wallet, and a written record of everything we hold about you — that is the short version of this privacy policy.

What we collectWallet references onlyCookie choicesWritten data requests
1666bet Open an Account Knowing What We Hold
GET IN TOUCH

Ask, Change or Delete Your Data

Privacy requests reach the same desk that answers your wallet questions, so nothing gets lost between teams. Open live chat from your account page, or email us from the address on your profile with the word privacy in the subject line. That routes your message to the people who handle data requests rather than general account queries. We reply in writing, in English, and if we need to confirm it is really you before we act, we will say so up front instead of stalling.

Live chat Open chat from your account page and quote the last four digits of your wallet number. That lets the agent pull the right record without asking you to repeat everything twice.
Email the privacy desk Write from your registered address with privacy in the subject. You get a written reply you can keep, and we will say plainly what we can remove and what local rules make us keep.
Wallet verification If a request touches your payment records, we confirm identity with a one-time code sent to your phone before anything is shared. That step protects you, not us.
HOW WE HANDLE IT

How We Handle Cookies and Login Records

Everything tied to your account has a rule behind it. Wallet references sit apart from your play record, so a bKash or Nagad transfer is never mixed into the rounds you played on Aviator or a live baccarat table. Device logs stay only as long as we need them to spot a hijacked login, and the staff who can open a full profile are few and logged when they do. Cookies keep you signed in and remember your language and wallet choice; clear them and the next visit asks for a fresh code to your phone.

What we store

Your name, date of birth, contact details, mobile wallet references from bKash, Nagad or Rocket, and a log of the devices you sign in from. Nothing else is needed to run the account.

Cookies and sign-in

Cookies keep your session open and remember the wallet you last used. Clear them and the browser forgets you, so the next visit starts with a fresh code to your phone.

Account security

Every login can be checked against the device you normally use. If a sign-in comes from somewhere unfamiliar, we ask for a one-time code before the wallet or the lobby opens.

Keeping and removing

Records that local rules require stay for the period those rules set, then go. Everything else is deleted when you close the account and we confirm the request in writing.

Privacy Questions You Ask Us Most

The same handful of things come up again and again, so we have put the answers in one place. Short replies below, written the way we would say them on chat. If your case is not covered, message us and a person will pick it up.

The details you typed when you opened the account, your mobile wallet references from bKash, Nagad or Rocket, and device logs that show where and how you signed in. Nothing beyond that.

Yes. Write from your registered email address and ask for a copy. We confirm it is really you, usually through a code sent to your phone, then send the file.

Only to the partners that make the account work: the payment rail behind your bKash or Nagad transfer, the studio behind the game you opened, and the fraud checks that screen logins. We never sell it.

Send the request from your registered email and say which parts you want gone. We close the account, delete what we are free to delete, and hold only records that local rules oblige us to keep.

We store the transaction reference the wallet returns, not your PIN or your balance. Payments confirm inside the wallet app itself, so your credentials stay with bKash or Nagad throughout.

It can, when the rules we work under shift. When a change affects what we collect or how long we keep it, we post the new wording on this page and flag it inside your account.
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.