Mobile / App
This privacy policy sets out what k8666 keeps when you register, fund the account wallet through bKash, Nagad or Upay, and move between lobby categories — plus the choices you have over it. Everything below is written as we would say it to you directly, and the routes for asking us to change something are listed further down.
One idea sits under this whole page: we collect what the account and the wallet need to run, and we tell you plainly where that data sits. Registration captures what you type into the sign-up form. When you fund the account wallet through bKash, Nagad or Upay, the transaction record keeps the reference, the amount and the status, so you and we can trace the same transfer if something looks wrong. Browsing details — which lobby categories you open, the browser and screen size you use — help us keep pages rendering correctly on a phone. We do not pass your account details to outside list brokers. Records stay with the people who need them to answer your question or correct a failed transfer. How much of the rest applies to you depends on where you are. Privacy rules differ by jurisdiction, and some parts of this policy, such as how long transaction records are kept, are set by the law that covers your region rather than by us. Service availability also depends on local law and eligible regions. Where a rule in your area gives you a stronger right than the one written here, that rule takes priority, and you can raise it with us through the routes listed further down. When the way we handle data changes, this page changes with it, and the version live here is the one that applies to your account.
Scope is easier to picture as four rings. The inner ring is your account: the sign-in route, the profile fields you can edit yourself and the wallet balance you see once you are in. The next ring is money movement — the bKash, Nagad and Upay transfer records attached to that wallet. Outside those sits site content: the lobby, the category lists, the game pages for titles such as Roulette Spinnacle or Crash Countdown, and the cookie choices behind them. Then comes everything we do not run. A mobile wallet app, your network provider and your phone's browser each handle data under their own terms, and what happens there is not covered by this page. Nor does this policy govern a studio's own game client, or any site we link out to. When a question crosses from our lobby into someone else's app, treat that app's notice as the one that governs it.
Your sign-in route, the profile fields you can edit yourself and the session that keeps you logged in on a phone all sit inside this policy. Sign in from another device and the same account record follows you, because there is one wallet and one profile behind it.
Every bKash, Nagad or Upay transfer tied to your wallet leaves a record we both can open: reference, amount, status. That record is covered here because we store it. What happens inside the wallet app on your phone is not, since that app runs under its own terms.
The lobby, the category lists and the game pages — Roulette Spinnacle, Crash Countdown, Football Betonsite — are ours to describe, along with the cookie choices behind them. If you open a title and the page behaves oddly, the browser details we log are the ones this policy explains.
Your mobile network, your phone's browser and any site we link out to each answer to their own privacy notice. We cannot change how a wallet app or a telecom provider handles your data, and this page does not try to. Read their notice when you leave our lobby.
Rights only matter if you can use them, so here is what each one looks like in practice. Want to know what we hold? Open your account area and go through the profile section first — most of it is already on screen. If a name or number is wrong, correct it there rather than sending a message, because the edit lands on the record we both see. When you cannot find something, ask us: a request about your data is a normal support question, not a special procedure, and you do not need to explain why you want it. You can also ask what was kept from a bKash, Nagad or Upay transfer, and we will point you to the transaction entry in your wallet. If you want your account closed and your details removed, say so plainly through the contact routes below. Some records, such as completed transaction entries, may have to stay for the period the law sets. We will tell you which ones and why.
Open the profile section of your signed-in account and the stored details are on screen. Wallet entries for bKash, Nagad and Upay transfers sit under the same login, so you do not need a separate request to see where a payment was recorded.
If the name on the account or a saved contact number is out of date, change it in the profile fields instead of messaging us. Edits there update the record directly, and you keep the same wallet and the same sign-in route afterwards.
Ask through the support route published on this site and describe the record you mean — a transfer reference, a page, a date. You do not have to justify the request; we just need enough to find the right entry in the account.
You can ask us to close the account and remove the details that are not tied to a completed transaction. Records linked to a finished bKash, Nagad or Upay transfer may need to stay for the retention period the law in your region sets, and we will say which ones.
Questions about this policy go through the same routes as any other account question, so you do not have to hunt for a separate privacy desk. Start inside your signed-in account: the message option there already carries your account reference, which means we can find the record you are asking about without a back-and-forth. If you are not signed in — say you cannot get into the account at all — use the contact form on this site and write from the mobile number or email address linked to it. Say what you want us to check, not why. A transfer reference from a bKash, Nagad or Upay payment, a date, or the name of the page you were on helps us find the entry instead of guessing. We answer in English, and we may ask one follow-up question if the record is not clear from your first message.
Signed in already? The message option inside the account area carries your reference, so whoever picks it up can open the same record you see. Use it for anything about stored details, a wallet entry or a page that behaved unexpectedly.
Locked out, or reading this before you register? The contact form published on this site works without a sign-in. Write from the mobile number or email address linked to the account and describe the entry you mean, so we can match it.
Every change to the policy appears on this page, so there is nothing to request by post. Bookmark it and compare the date shown here the next time you sign in. If a clause here and a support reply disagree, ask us to confirm which applies.
Three things do most of the work behind this policy: the cookie your browser keeps, the session that holds your sign-in, and the records we store after you leave. Cookies on this site remember small choices such as the language and the last category you opened, so the lobby does not reset on every visit. Blocking them in your browser settings is your call — some parts of sign-in will then ask you to repeat steps. Sessions expire; when yours does, sign in again and nothing about the wallet changes. Stored records are the longer-lived part: transaction entries tied to bKash, Nagad or Upay transfers, and the account details you entered. We keep them for the period the applicable law in your region requires, then remove them. Nobody at k8666 needs your wallet PIN or your bKash PIN to answer a question about a transfer, and we will never ask for either. Treat any message that does as someone else.
The cookie your browser stores remembers small things — the category you opened last, the language you picked. Clear them any time from your browser settings. Some screens will then ask you to sign in or repeat a step, which is expected rather than a fault.
Your session keeps you inside the account while you move between the lobby and the wallet. It ends on its own, and signing out on a shared phone ends it sooner. After that, sign in again with the details you set — nothing in the wallet or the transaction list is lost.
Transaction entries and account details are held for the span the law covering your region sets, not for as long as we like. Ask us about a specific entry and we will say what is kept, why, and when it comes off the record.
Closing an account, correcting a saved detail or removing data that is not tied to a finished transfer all start with a message through the routes above. Say which record you mean and what you want changed; we will confirm what can be done under the law that applies to you.
Some questions arrive often enough to deserve a straight answer on the page rather than in a message. The six below cover the ground people ask about most: what we keep, how long we keep it, who sees it, what you can change and how to reach a person when the answer is not here. Each answer is short on purpose. If yours is about one specific transfer, open the wallet first and keep the reference to hand before you write to us; that single line gets a question settled in one exchange instead of three. Queries about cookies are welcome too — tell us the browser and the screen you were on. Your account reference appears once you sign in, so quote it and skip the description of who you are. Nothing in this section replaces the policy text above it, and where the two read differently, the policy wording is the one that applies to your account.
The details you enter when you register, the wallet entries created by your bKash, Nagad or Upay transfers, and basic browsing data such as the categories you open and the browser you use. We keep them to run the account, trace a payment and fix pages that misbehave.
Yes. Sign in and the profile section shows the stored account details, while the wallet shows each payment entry with its reference and status. That covers most of what people write in to ask about, and it saves you waiting on a reply for something already on screen.
For the span the law covering your region requires for payment records, which is why we cannot always delete an entry on request. Account details that are not tied to a finished transfer can be removed when you close the account. Ask about a specific entry and we will say what applies.
No. This page covers what k8666 holds once a transfer reaches your wallet here. The wallet app you use to send the money runs under its own privacy notice, and so does your mobile network. Read that notice if you want to know what the app side keeps.
Change them yourself in the profile fields of your signed-in account; the edit lands on the record straight away and your sign-in and wallet stay as they were. If a field will not accept the change, send a message with the exact entry and what it should say.
Use the message option inside your account, or the contact form on this site if you cannot sign in. Both reach the same team. Include your account reference and, where a payment is involved, the wallet entry you mean, so the first reply can answer rather than ask.