This page sets out how 6h886 collects, keeps and uses account and session details when you open the site, sign in and move money through Nagad, Rocket or Upay, and what you can ask us to do with that record. Read it alongside your account page, because the controls you see there follow the same rules you find here, and access always depends on your local law and eligible regions.
Account and session details
Wallet activity records
Cookie and device signals
Support contact routes
PRIVACY POSTURE
Our Privacy Position For Bangladesh
We treat your account record as something you should be able to follow from sign-in to statement. When you register at 6h886, we hold the details you give us, the sessions you start, and the wallet activity that runs through Nagad, Rocket or Upay. What we may collect, how long we keep it, and when we can share it all depend on the law where you live and on the regions we are able to serve, so this page does not pretend there is one global standard. Where local law gives you a particular right over your data, we apply that law to your account. Where it does not, the same internal rules still hold: limited staff access, documented changes, and records kept only as long as we need them for account care and for our own legal duties. Nobody here sells your personal details, and we do not hand them to unrelated companies for their own marketing. If a payment rail, a game category or an account feature is not available in your area, that is a service availability question rather than a change to this policy. Ask us through a published support route and we will explain what we hold about you and why.
Nagad
Rocket
Upay
Bank Transfer
WHAT SITS INSIDE
What This Policy Covers
One page cannot describe every corner of a site, so it helps to know where this policy begins and ends. It follows your account: your sign-in, the profile details you save, your session history and the transaction record behind every Nagad, Rocket or Upay movement on the wallet. It also covers how we log activity on pages we run ourselves, the rooms you open, the tables you sit at, and the device and browser data that keeps a session steady when you switch screens. What it does not do is follow you off our pages. A wallet app, a messaging service or another operator's site keeps its own notice, and that notice governs what it collects about you. If a page here embeds something from a third party, the embedded part sits outside our scope too. When we change what we collect or how long we keep it, we revise this page so the wording you read matches the rules we apply.
Account access and login
This part of the policy follows you from the moment you open an account. We keep the email address and password you set, the session history your account shows, and the preferences saved in your profile. If you change a detail on the account page, the newer entry replaces the older one in our record.
Wallet and transaction records
When money moves to or from your account through Nagad, Rocket or Upay, we hold the matching record: the amount, the rail used and the reference your wallet shows. Those entries back up your own statement checks and our duty to keep accurate records. We do not store your wallet PIN.
Play inside our own pages
Sessions you run in our lobby, whether a round of Crash Skyward, a cricket market or a table at Baccarat Lantern, are logged so we can settle results, spot unusual activity and keep the site stable. What happens after you leave for another operator's site falls under that operator's own rules, not ours.
Services we do not run
Links out to a payment app or a messaging service sit outside this policy. Those companies collect what their own notices describe, and we cannot change or delete what they hold. If a page on our site embeds something from another provider, treat that embedded part as theirs and read the notice it publishes.
YOUR DATA CHOICES
Steps You Can Take On Your Data
You do not need to wait for us to act. Open your account page and you can look through the profile details we hold, fix a spelling or an outdated email address, and change how we reach you. If you want a fuller picture, ask through a published support route and we will tell you what we keep and why. Where the law in your region gives you a stronger right, such as a copy of your record, correction, or deletion once our own record-keeping duties are done, we follow that law for your account. A removal request cannot always be met in full, because transaction entries tied to Nagad, Rocket or Upay may stay on file for as long as the law requires. Say plainly what you want changed; the clearer your message, the fewer rounds it takes. If you believe someone reached your account without you, report it at once so we can secure the account and check the sign-in history.
Check your own record
Sign in and open the account page. Your profile details, saved preferences and recent session history are listed there, and you can read them without writing to anyone. It is the quickest way to confirm what our record says about you before you ask us to change something.
Correct a detail
Names get misspelled and email addresses go out of date. Where a detail on file is wrong, tell us through a published support route and we will correct it against the account you hold. Keep the message short and include the exact field you want changed.
Ask for a copy
You can ask what personal details we hold about your account and why we keep them. We answer such requests through the same support routes shown on the site, and we may need to confirm that the request comes from the account holder before we release anything.
Report an access problem
If a sign-in you did not start shows up, or a message from us looks wrong, report it straight away. Change your password first, then write to us with what you noticed and when. We will check the session record and tell you what we find.
CONTACT ROUTES
Where To Send Privacy Questions
Questions about your data come to the same place as account questions. We list the routes we run on the support page, and each one reaches a person who can see your account record. Tell us which account you mean, what you want changed or explained, and the period you are asking about; that saves a round of messages. If your question is about a payment, keep the wallet reference from Nagad, Rocket or Upay with it so the record can be matched quickly. If it is about a game session, name the title and roughly when you played, and we can look up the log. We do not promise a reply time, and privacy messages go through the same published route as any other account question. Messages you send through a support route are tied to your account, not posted anywhere public, so you can refer back to the thread when you follow up.
Support page
The support page carries the contact routes we run, and it is the first place to look before you write. Pick the route that matches your question, include your account email and the wallet reference where a Nagad, Rocket or Upay payment is involved, and send it in one message rather than several.
Signed-in message
While you are signed in, you can raise a request from the account area so it arrives with your account already attached. That helps when the question is about a detail on your profile, a session log, or a setting you want changed. You keep the thread for later follow-up.
Policy pages
This page and the terms page are written to be read together. Where a question is about what we do with data, the wording here answers it; where it is about your obligations as an account holder, the terms page does. Read both before you send a question that covers data and account rules at the same time.
HOW DATA IS HELD
How 6h886 Holds Account Data
Data handling here follows a few plain rules. We collect what an account needs to work: the details you enter, the sessions you start, and the wallet movements that pass through Nagad, Rocket or Upay. We keep that record under access controls that limit who can open it. Cookies and similar tools do the small jobs: keeping you signed in between pages, remembering a language or layout choice, and letting us see which pages fail so we can fix them. You can clear cookies in your browser settings, though some parts of the account area will ask you to sign in again. Retention is tied to purpose. Records stay while your account is open and for the period our legal duties require afterwards, then they are removed or stripped back. Nobody outside the people handling your account support reads it. If we change how any of this works, we revise this page, and you can always ask through a published support route what applies to your account today.
What we collect
An account needs a working set of details: the email and password you set, the profile fields you fill in, session logs that show when you signed in, and the transaction records behind Nagad, Rocket or Upay movements. We collect what keeps the account running and what the law asks us to keep.
Cookies and device signals
Cookies keep a signed-in session steady while you move between pages, and they remember small choices such as layout. Your browser also passes basic device details that help us spot a broken page or a sign-in that does not match your usual pattern. You can clear cookies any time.
Retention and removal
We hold records only while they serve a purpose. Profile details stay for as long as your account is open; transaction entries may stay longer because financial records need to be kept. When a record no longer has a use, we delete it or remove the parts that identify you.
Access and changes
Staff access to account records is limited to the people who need it to answer your message or finish a step you asked for. If we change what this page describes, we update the wording here rather than leaving an older version in place. Send a question through a published support route.
QUESTIONS WE RECEIVE
Privacy Questions We Hear Often
The questions below are the ones we answer most often about data, access and contact. Each answer points to the route or page where you can act on it, so you are not left with a general statement and no next step. If your situation differs from what you read here, write to us through a published support route and ask directly; a question about your own account record is easier to answer than a broad one about policy in general. Where a matter depends on the law in your region, we will say so rather than give a single rule that may not fit. Where it depends on something on your account, we will tell you what we can see and what we need from you. Keep the two ideas apart: policy wording is the same for everyone, but what it means for your record can differ.
What personal details does this policy cover?
It covers what keeps an account running: the email and password you set, the profile details you save, sign-in and session logs, and the transaction records behind Nagad, Rocket or Upay movements. It also covers basic device and browser signals used to keep pages working.
Do you pass my details to the wallets I pay with?
A payment rail sees what it needs to complete a transfer, and it keeps its own record under its own notice. On our side we hold the matching entry: the amount, the rail and the reference your wallet shows. We do not hand your details to unrelated companies for their marketing.
Can I ask for a copy of what you hold about me?
Yes. Send the request through a published support route and say which account you mean. We may ask you to confirm that the request comes from the account holder before we release anything, which protects the record from anyone writing in under your name.
Can I close my account and remove my details?
You can ask us to close the account and remove what we no longer need. Some entries stay on file, because transaction records tied to Nagad, Rocket or Upay movements must be kept for the period the law sets. We will tell you what can be removed now.
Do cookies change how the site treats my account?
Cookies do not change the policy; they carry a session and remember small choices, such as the layout you last used. Clear them in your browser settings if you prefer, and expect to sign in again on parts of the account area that rely on a live session.
Where do I report access I did not start?
Change your password first, then write through a published support route with the time you noticed and anything unusual about the device. We will look at the sign-in history on your account and tell you what the session log shows.
Casino / Live