Sharing your personal information with 6kdb doesn't mean it goes anywhere it shouldn't. This page clearly explains what data we collect, why we collect it, and how we keep it secure.
We believe your data belongs to you — 6kdb retains only what is necessary to deliver its services.
When you use 6kdb, we collect two types of data — what you provide directly and what is generated automatically through your use of the platform. Details are outlined below.
| Data Type | What data | Why It's Needed |
|---|---|---|
| Identity information | Name, date of birth, national ID number | For age verification and KYC completion |
| Contact Information | Mobile number, email address | For sending OTPs, support communications, and notifications |
| Financial information | Mobile banking number, bank account name | For deposit and withdrawal verification |
| Usage Data | Betting history, login times, device information | For security monitoring and service improvement |
| Technical information | IP address, browser type, app version | For fraud detection and prevention of multiple accounts |
6kdb uses your information solely for the purposes listed below. It is never used for any other purpose.
6kdb does not sell your data. However, limited information may be shared in specific circumstances in order to deliver our services.
6kdb uses a multi-layered security approach to protect your data — not just a single measure, but protection built layer upon layer.
The 6kdb website and app use certain cookies and technical tracking tools. The purpose of each is clearly outlined below.
| Cookie type | Purpose | Duration |
|---|---|---|
| Essential Cookies | Maintaining login sessions, security tokens | Until end of session |
| Functional cookies | Remembering language preference and odds format | 30 Days |
| Analytics cookies | Understanding which pages are visited most (not linked to individuals) | 90 days |
| Security Cookies | CSRF protection, bot detection | Until end of session |
You can disable cookies through your browser settings, though some features may not work properly as a result. 6kdb does not use third-party advertising tracking cookies.
6kdb does not retain data unnecessarily. Every piece of information is stored only for as long as it is needed.
Upon a request to close your account, all data held beyond legal requirements will be deleted within 30 days.
You have certain rights regarding your data that 6kdb respects. To exercise these rights, support@6kdb.xyzto send us an email.
6kdb strictly does not serve users under 18 years of age and does not collect any data from minors.
6kdb may update this Privacy Policy from time to time as needed. Any changes will follow the process outlined below.
To exercise any of these rights, please contact our support team — you can expect a response within 7 business days.
Even if one layer is compromised, the others hold — that is the principle behind multi-layered security.
When creating an account on any online platform, one question almost always comes to mind — "Will my information be safe?" In Bangladesh, this concern is especially relevant given how frequently online fraud is reported. 6kdb takes this seriously — and backs it up with action, not just words.
First and foremost, 6kdb will never ask for your bKash PIN, Nagad PIN, or bank password. This is fundamental — 6kdb simply does not need that information to provide its services. If anyone claims to be from 6kdb and asks for these details, it is unquestionably a scam. Keep this distinction in mind: 6kdb only asks for your mobile number (for transactions) and your transaction reference number (to verify payments).
Let us explain what SSL encryption means in simple terms. When you log in to the 6kdb website, your password is not sent directly — it is first converted into a complex code and then transmitted. Even if someone intercepts that code along the way, they cannot extract your actual password. That is SSL in a nutshell. 6kdb uses the strongest available 256-bit SSL encryption.
It's worth explaining why OTP verification matters so much. Suppose your password somehow ends up in the wrong hands. If someone tries to log in, 6kdb will send an OTP to your phone — without it, login is blocked. So even knowing your password, no one can access your account without your phone. That's why keeping your mobile number secure is so important — if your SIM is lost or changed, inform 6kdb support right away.
There are many misconceptions about cookies. Cookies do not mean your data is being secretly stolen. 6kdb uses cookies for three main purposes — to remember that you are logged in, to save your preferred language and settings, and to understand overall platform usage patterns. 6kdb does not use advertising tracking cookies — meaning using 6kdb will not cause 6kdb ads to follow you around other websites.
Data retention is a nuanced matter — it requires balancing legal obligations with practical reality. Closing your account does not mean all data is immediately deleted, as financial transaction records must be retained for 5 years by law. However, your personal information — such as your name, address, and phone number — is deleted within 30 days beyond that legal minimum. 6kdb does not hold on to any data unnecessarily.
In the event of a data breach, what will 6kdb do? Affected members will be notified within 72 hours, clearly informed of what data was impacted, and given guidance on next steps. To date, no significant data breach has occurred at 6kdb — but this commitment is shared here as part of our transparency.
One final piece of advice — stay vigilant yourself. No matter how robust 6kdb's protections are, your cooperation is essential for complete security. Never share your account password with anyone, never provide OTP details over the phone to unknown callers, and report anything suspicious to 6kdb support immediately.
Questions members commonly ask about account security and platform features.
You've read the Privacy Policy and know how your data is protected — go ahead and get started with confidence.
For ages 18 and above only. Please game responsibly.