Slots / App
This page explains how qq78 collects, uses and protects the details attached to your account, from the profile fields you fill in to the wallet history behind your transfers. What we can offer, and which parts of this policy apply to you, depends on your local law and eligible regions.
qq78 runs for readers in Bangladesh, and this page explains the ground rules we follow when you open an account, move money through your wallet or browse the lobby. What we can offer, and which parts of this policy apply to you, depends on your local law and eligible regions, so nothing here should be read as a promise that every feature is open to you. We write it in plain words rather than legal filler, because you should be able to see where your details go without a lawyer. When you register, we hold what you type in: your name, your contact route and your login credentials. When you move funds with bKash, Nagad, Rocket or a Bank Transfer, we keep a transaction record so your wallet balance and your history agree with each other. When you open a table such as Holdem SmashBet, our systems log the session so unusual access stands out and disputes can be settled from evidence rather than memory. Cookies do a smaller job. They keep you signed in, remember your language choice and tell us which lobby pages load slowly on mobile. You can clear or block them in your browser settings and the site will still work, though you may need to sign in again each time. We keep records only while we need them for the reason you gave them, or while the rules we answer to require it. If you want to know what we hold, the support route published on this site is the place to ask, and we will walk you through the request step by step.
Think of this policy as the line around our house. Inside it sit the account you create with us, the wallet and transaction records that follow from your deposits and withdrawals, and the content we serve you, from lobby pages to game sessions such as Crash ShockWave. Outside it sit the other places you go online. If a link takes you to a payment page run by a wallet provider, or a messaging app you use to talk to a friend, their own rules apply and you should read them there. We do not control what your bank does with a Bank Transfer once it leaves your instruction. We show what we receive, and it appears in your account history. Your device, browser and network provider keep their own settings, and changing them is your call. When something falls outside this policy, we say so on the page where it happens rather than leave you guessing. That way you always know which set of rules you are reading.
Everything tied to the login you create with us, including the name and contact route you enter when you register, sits inside this policy. That covers how we store your credentials, how sessions link to your profile, and how you ask for a correction when something you typed is wrong.
Deposits and withdrawals you make through bKash, Nagad, Rocket or a Bank Transfer appear in your wallet history, and those records stay inside this policy. If a wallet provider or your bank applies its own checks, those fall under its rules, while what reached us shows in your account.
Lobby pages, game sessions and the device data we log when you browse sit inside this policy. That includes the titles you open, such as Roulette DiamondSpin, and the technical detail we use to keep pages loading properly on a phone screen.
Links to a wallet app, a browser extension or a messaging tool lead away from us, and their own privacy terms take over at that point. We do not set their rules and cannot change their records, so read what they publish before you share anything with them.
Having an account here comes with practical choices, not just obligations. You can look at the profile details we hold for you from inside your signed-in area, and if a phone number, address or name has changed, correcting it takes a short form rather than a letter. You can ask what records we keep about your wallet activity, and we will explain what each entry means in plain words. If something looks wrong, tell us through the support route published on this site rather than guessing at a fix. We will check the record with you, explain what we find and, where the rules we answer to allow it, change or remove what we hold. Where a request cannot be met, you will get a reason, not silence. You also choose how much of your browsing we see by managing cookies in your own browser, and you can decide which devices stay signed in to your account. Those switches sit with you. Nothing in this policy takes them away.
Open your signed-in area to see the name, contact route and preferences attached to your account. If a detail is out of date, the form there lets you correct it yourself, and the change shows on your profile once it is saved.
Wallet entries from a bKash, Nagad, Rocket or Bank Transfer deposit all carry a reference. Send that reference through the published support route and we will explain what the entry means and when it was written to your history.
Cookie settings live in your browser, not in a hidden panel behind ours. Clearing them signs you out of saved sessions; blocking them entirely still lets you read pages, though some parts of the lobby may ask you to sign in again.
If you think we have handled your details badly, say so plainly through the support route on this site. Describe what happened and which part of the policy it relates to, and we will take it from there with you.
Privacy questions rarely arrive at a convenient moment, so we keep the routes simple. The support page published on this site is the front door: it lists what you can ask about and links straight into the account tools you need. From there you can describe a concern about your data, ask what we hold, or flag a record that looks wrong to you. If you are already signed in, your account area carries the same route. Sending a message from inside your account lets us match your request to your profile without you repeating details we should already have, and it is the quickest way for us to see the wallet entry or profile field you are writing about. We do not publish separate phone lines for privacy matters, because a written request leaves a record you can check later. Keep the reference you receive, and use the channel shown on the support page.
The help page published on this site is where privacy requests start. It explains which questions we can answer from your account and points to the tools you need, so you can write to us with the details already in front of you.
Once you are signed in, your account area carries the same support route. Writing from inside your account lets us tie the request to your profile, which saves you repeating your contact route and speeds up the check on your records.
Profile fields, wallet history and session details sit behind your login, and the support route is listed beside them. Look at what is stored first, then raise anything that looks wrong with the exact field or entry name so we can act on it.
Handling your details well is mostly unglamorous work: limiting what we collect, watching who can reach it and clearing it out when it is no longer needed. We ask for the minimum a working account needs, a name, a contact route and credentials, and we do not sell it on. Access inside our own systems is limited to the people whose job requires it. Cookies stay narrow in scope too. They keep a session alive, remember your language and show us slow-loading pages on mobile so we can fix them. Security around your login is your side of the bargain as well: use a password you do not reuse elsewhere, and sign out on shared phones. Retention is tied to purpose. We keep wallet records because your history has to add up, and we keep account details while your account is open. When a record no longer has a reason to exist, it goes. If you want something changed, the support route published on this site is where to ask, and you will get an answer explaining what we can do.
We ask for a name, a contact route and login credentials, and that is where collection stops for a standard account. Gameplay logs exist so sessions can be traced and disputes settled, not so we can build a profile and sell it to anyone else.
Cookies here keep you signed in, remember your language and help us spot pages that load slowly on mobile. They sit in your browser, so you can clear or block them whenever you like; the site still opens, though you may have to sign in again.
Wallet entries stay while your account is open, because your balance and your history have to agree. Other details are kept only while the reason you gave them still stands, and they are removed once that reason ends and the rules we answer to allow it.
Your password is the gate. Pick one you do not reuse on other sites, sign out on shared phones, and tell us through the published support route if your account shows activity you do not recognise, so we can look at it with you.
Most privacy emails we get ask the same handful of things, so the answers sit in one place below. They cover what you can see about your own account, how long we hold records, how to ask for a correction and how cookies change what happens on your phone. Read the question closest to yours first; if none of them fits, the support route published on this site is still open to you. Two points apply across all of them. What we can do depends on your local law and eligible regions, so an answer here describes our normal practice rather than a promise for every case. And anything tied to money, a bKash, Nagad, Rocket or Bank Transfer entry, is easier to sort out when you send the reference along with your question.
The name and contact route you enter when you register, your login credentials, and the preferences attached to your profile. Everything you see in your signed-in area is drawn from that record, so if a field looks wrong, correcting it straight away keeps your account accurate.
Yes. Your account history lists deposits and withdrawals from bKash, Nagad, Rocket and Bank Transfer, each with its own reference. Open that page first, then send the reference through the published support route if a line needs explaining in more detail.
Use the support route shown on this site and name the field you want changed. We will check it with you, explain what we can adjust under the rules we answer to, and tell you plainly if a request cannot be met and the reason for that.
Some records stay for a while after closure because wallet history has to remain complete and traceable. Others are removed once we no longer have a reason to keep them. Ask through the support route and we will explain what applies to your account.
No. Ours keep you signed in, remember your language and help us find slow pages on mobile. They do not build an advertising profile. You can clear or block them from your browser settings whenever you like, and the pages still open for you.
The support route published on this site is the one to use, whether you are signed in or not. Describe the problem and the page it happened on. A written request leaves a record on both sides, which helps if you need to follow it up later.