Mobile / App
shaka7 sets out how your account, your wallet activity and the lobby you open are governed. This page covers what applies when you fund your account, check your transaction record and move through the games, with access always subject to your local law and eligible region.
This policy sits alongside the account you open with us and the wallet you fund through bKash, Nagad, Rocket or Upay. We write it to cover the practical path from signing in to seeing a transaction land on your account, not as a general statement about every market we might reach. Where you access shaka7 from, and whether a given payment route is available to you, depends on your local law and the eligible region you are connecting from — we do not promise access or payment support outside of what your account page actually shows you. If a payment chip is not visible in your account, treat that as the current answer for your region rather than something we have withheld. Our policy posture is deliberately plain: it describes what happens with your account details, how we treat the record of a bKash deposit or an Upay transfer, and what you can ask us to look at again. We update this page when the account-to-wallet path itself changes, not on a fixed schedule, so always read the version shown here rather than a saved copy. Nothing here should be read as a licensing statement or a claim about where we are permitted to operate; those questions sit with your local regulator, not with this notice. If a term on this page conflicts with what your account screen shows at the point of a transaction, the account screen is the practical reference for that moment.
This page draws a line around four areas of your experience with us: how you access your account, what happens to a transaction once it's on your wallet record, what the lobby itself shows you, and where a service outside our own pages gets involved. We keep those four separate because the right answer to a question depends on which one it falls under — a login question is handled differently from a question about a bKash deposit, and a question about a game you opened in the lobby is different again. None of this is a claim about where shaka7 can legally operate; that depends on your local law and the eligible region you're connecting from, and your account page is the practical reference for what's actually available to you right now. Read the four areas below before raising a question, so you know which door to use.
Covers how you sign in, how your account details are stored for return visits, and the device checks that confirm a login attempt is actually coming from you. These checks also cover why a new phone or browser can trigger an extra prompt before you reach your account.
Covers the record a bKash deposit, Nagad transfer or Rocket payment leaves on your account, including how that entry appears in your transaction history for you to check later. It does not cover how the payment app itself processes the transfer on its own side.
Covers the game lobby itself — titles like Cricket Betting Live or Roulette Action — and how that content is presented to you on the page, separate from any payment or account matter. It applies to what you see in the lobby, not to the account or wallet record covered elsewhere on this page.
Covers where a payment rail, game studio or support tool outside shaka7 is involved, and makes clear this policy only speaks for what we control on our own pages. It does not extend to a separate policy a payment provider publishes on its own site.
You're not stuck once an account is open. If something on your wallet record looks off — a bKash deposit that doesn't match what you sent, or an Upay transfer missing from your history — you can raise it through the support route on your account page and ask us to check the entry against our record. The same applies to your account details: if your contact details or saved payment preference needs correcting, that update happens from inside your account rather than through this page. We keep this simple on purpose. You check your own transaction record first, then raise a specific question if something doesn't line up, rather than waiting on a broad check. This way, you're verifying your own wallet activity most of the time, and only escalating when a specific entry needs a second look.
Open your account's transaction history to check a bKash deposit, Nagad transfer or Rocket payment against what you expect to see before raising a question.
Update contact details or a saved payment preference from inside your account rather than waiting for this page to change.
Use the support route shown on your account page when an entry on your wallet record doesn't match, and point to the exact transaction.
If a question needs more than a quick check, ask through the same support route and reference the account and date involved.
Policy questions usually come down to one of two things: an account detail that needs correcting, or a wallet entry you want a second look at. We publish specific support routes rather than a single generic contact line, because a login problem and a bKash deposit question usually need different handling. Start with the support route on your account page — it is tied to your signed-in session, so a check against your record is faster than an unlinked message. If you need the fuller wording behind this notice, our terms and privacy pages carry that detail and sit one tap away from your account footer. We don't operate a separate legal desk outside what's published here and on those pages. Think of these as two doors into the same account: one for a quick wallet check, one for the fuller legal wording, and both point back to the account you're signed into.
Reach us through the support route listed on your account page when a wallet entry or login issue needs a direct answer. Mention the account you're signed into and the specific transaction, bKash deposit or Rocket payment, so the check against our record moves faster.
The help section inside the lobby carries published notices for account and wallet questions, so it's worth a look before you raise a new query. It's organized around the same account-to-wallet path this page describes, from signing in to checking a transaction.
Our terms and privacy pages, linked from your account footer, set out the fuller wording behind this notice, including how we handle data retention and account closures. They're the reference point if a wording question goes beyond what this summary covers.
Your account carries two kinds of information we treat carefully: who you are, and what your wallet has done. Login details and device signals are used to keep your session tied to you, which is also why signing in from a new device sometimes triggers an extra check. Your transaction history — a bKash deposit, a Rocket payment, an Upay transfer — stays attached to your account so you can check it later rather than relying on a receipt from the payment app alone. Cookies on this site mostly support that session continuity: keeping you logged in across pages rather than tracking you for reasons unrelated to your account. We don't share wallet details beyond what's needed to confirm a payment landed. If you want a detail corrected, removed from view, or explained, the support route on your account page is where that request starts, and we handle it against the account you're signed into.
We use login details and device signals to keep your session tied to your own account rather than to a saved password alone, which is why a new device or browser can prompt an extra check before you continue into the lobby.
Deposits and transfers through bKash, Nagad, Rocket or Upay stay logged against your account so you have your own record to check later, separate from whatever receipt the payment app shows you. This matters if you ever need to point to a specific entry when raising a question.
Cookies on shaka7 mainly keep you signed in between pages as you move from the lobby to your account and back. They are not used here to build a profile unrelated to your own account activity, and they behave like standard session cookies rather than tracking you elsewhere.
To correct, question or ask about a data entry tied to your account, use the support route on your account page and reference the specific record, including the date and payment method where relevant, so we can match it against our own copy.
These are the questions we see most often about how this policy touches your account and your wallet record. If your situation isn't covered below, the support route on your account page is still the right place to start, since it ties your question directly to your signed-in session.
We use your payment details only to confirm a deposit or transfer landed on your account correctly. We don't pass wallet details to parties outside what's needed to process that specific bKash or Nagad transaction, and this notice doesn't change if your account activity changes.
Yes — your account's transaction history keeps a record of deposits and transfers through bKash, Nagad or Rocket, so you can check an entry against what you actually sent, rather than relying only on a screenshot from the payment app. That record stays available whenever you want to look back.
A new device can trigger an extra check tied to your account, since our session handling is built around keeping access linked to you specifically, not just to a saved password sitting on a browser. This is a device-continuity step, not a sign that something has gone wrong with your account.
Use the support route listed on your account page and point to the specific entry — the date, amount and payment method, whether it's a bKash deposit or an Upay transfer — so we can check it against our own record and get back to you with an answer.
No — access and which payment routes you see, including whether bKash, Nagad, Rocket or Upay show up for you, depend on your local law and the eligible region you're connecting from. Your account page is the practical answer for your own situation, not a general statement on this page.
Most contact and preference details update directly from inside your account, without needing this page to change. If something needs a manual check — like a payment preference tied to bKash or Rocket — raise it through the account support route instead of waiting on an update here.