Sports / App
77joys treats your account details, payment records and browsing activity as data we're responsible for protecting, not something we handle loosely. This policy explains what we collect when you open an account, deposit through bKash, Upay or Bank Transfer, or browse our live tables and slot rooms, and how you can ask about or correct what we hold.
This Privacy Policy sits alongside our Terms and covers how 77joys collects, stores and uses details tied to your account on the lobby, our live tables and our slot rooms. What we gather depends on how you use the platform: registration details when you open an account, device and browser data when you sign in on mobile or desktop, and transaction references when you move money through bKash, Upay or Bank Transfer. We don't collect payment credentials beyond what's needed to match a transaction reference to your account wallet — card numbers, wallet PINs and OTP codes stay inside the payment provider's own system, not ours. Because online gaming access depends on your local law and eligible region, how this policy is enforced and what rights apply to you can vary depending on where you're accessing 77joys from. If a term in this policy conflicts with a mandatory rule in your region, the local rule takes priority. We update this policy periodically and the version live on this page is the one that applies to your account at any given time; we don't maintain a separate archive of older versions for you to compare. Any update that changes how we use your account data will be reflected directly on this page rather than announced through a separate notice.
Not every part of your experience on 77joys sits inside this one document. Account access — your login, password resets and the device you use to sign in — falls under this policy because it's data we hold directly. Transaction records tied to bKash, Upay or Bank Transfer deposits and withdrawals are also covered, though we only see the reference and status, not your banking credentials. Site content — the game rooms themselves, like Roulette Velocity or Slot Starfire, and how long you spend browsing them — is logged as usage data under this policy too. Where this policy stops is at third-party services: payment apps, your mobile carrier and any provider game engine run under their own privacy terms, which we don't control and can't rewrite on their behalf. We separate what we're responsible for from what sits outside our reach, so you know which rules apply where.
Your login details, the password resets you request and the device or browser you use to sign in to 77joys all fall inside this policy, because we store that session and account data directly against your profile and reference it when you contact support about access issues.
Deposit and withdrawal references through bKash, Upay or Bank Transfer are recorded against your account wallet; we see the transaction status and reference number, not your banking credentials, PIN or one-time codes, which stay with your payment provider throughout the process.
Which rooms you open — live tables, slot titles like Slot Starfire or Dhaka Hot Slots, or our sportsbook pages — is logged as usage activity covered by this policy, including how long a session runs and which category you browse most on your account.
Payment apps, your mobile network and any game engine run by a studio operate under their own privacy terms; this policy covers what 77joys holds about your account, not what a payment app or network partner holds on their own separate systems.
You're not locked out of what 77joys holds about you. If you want to check what's attached to your profile — your registered details, your transaction history across bKash, Upay or Bank Transfer, or your login activity — the account section is where that record lives, and you can look at it directly rather than request a separate export. If something is wrong, like an outdated phone number or a misspelled name, you can correct it from your account settings or by raising it with support so the change reflects correctly against future transactions. Questions about how long we keep a record, or why a particular session appears in your activity log, go through the same support route rather than a separate privacy desk. We respond to what's asked, we don't auto-close a query without addressing it, and we keep the correction tied to your account rather than a general ticket queue.
Open your account section to see the details attached to your profile — registration details, device sign-ins and transaction references tied to bKash, Upay or Bank Transfer — without needing a separate request.
If a phone number, name spelling or contact detail is wrong, update it from your account settings or raise it with support so the correction applies before your next transaction.
If you're unsure why a session or transaction appears in your activity log, send the question through support; we address what you've asked rather than redirect you to a general FAQ.
For anything this policy doesn't answer directly — like how a specific record was logged — raise it through the same support route listed in your account; we treat it as a direct account query.
Questions about this policy don't need a separate inbox — they go through the same support route you'd use for an account or payment question. We keep that routing deliberately simple: one path for sign-in trouble, transaction mismatches on bKash, Upay or Bank Transfer, and privacy questions, so you're not guessing which department to message. When you raise a privacy-related question, mention your account email or registered number so the record we check matches the one tied to your profile; this is faster than a generic message sent to a shared address. We don't operate a separate 'data officer' inbox listed outside the main support route, and we don't commit to a fixed response window here, because that detail sits with the support process itself rather than this policy. What we do commit to is reading the question in context — tied to your account record, not a stripped-out ticket number — before we reply.
Use the support option inside your account to ask about any detail this policy covers — your stored data, a correction you need made, or a session on your activity log you don't recognise and want explained before you continue using your account.
The contact path shown in the site footer reaches the same support queue as in-account support, which is useful if you're asking a privacy question before you've opened an account or completed sign-up on your device yet, since no account login is required to send that message.
If you've already raised a question about this policy, reply on the same thread instead of opening a new one, so your account history and earlier reply stay attached to that single conversation record rather than starting over with a fresh support ticket each time.
Keeping your account details straight matters more to us than collecting extra data we don't need. We hold what's required to run your account — login details, device data, and transaction references across bKash, Upay or Bank Transfer — and we don't attach unrelated browsing data from outside the platform to your profile. Cookies on the site are used mainly to keep you signed in and to remember basic preferences like language, rather than to build an outside advertising profile; where a cookie serves a different purpose, we aim to describe it rather than bundle it under one label. Account security on your side starts with your password and the device you choose to stay signed in on — we recommend signing out on a shared device rather than relying on us to detect that for you. Retention follows the same account record: we keep data attached to your profile for as long as the account is active, and a correction or question goes through the support route rather than a separate retention request form.
We keep registration details, device sign-in data and references for deposits or withdrawals through bKash, Upay or Bank Transfer attached directly to your account record, rather than storing them in a separate unlinked system you can't trace back to your profile.
Cookies mainly keep your session signed in and remember basic settings like language; we don't use them to build a cross-site advertising profile that follows you around outside 77joys, and where a cookie serves a different purpose we try to describe that separately rather than bundle everything under one label.
Your password and the device you choose to stay signed in on are the first line of control over your account; sign out on a shared device rather than leaving your session open for the next person to use, especially on a shared mobile.
Account data stays attached to your account while it's active, and we don't run a separate retention timer outside the account itself; if you want something corrected or explained, raise it through the same support route rather than a standalone retention request form.
A short set of questions account holders raise most about how 77joys handles data, payments and support under this policy.
We share only what's needed to confirm a transaction — your reference number and account identifier — with the payment provider you use, like bKash, Upay or Bank Transfer. We don't pass your gaming activity or account history to a payment provider beyond what completes that transaction.
Yes — open the account section where your profile is managed to check registration details, device sign-ins and transaction references. If something looks unfamiliar or incomplete, raise it through support so we can check the record against your account directly.
Update what you can directly from your account settings — things like a phone number or display preference. For details you can't change yourself, such as a registered name, send the correction request through support and we'll apply it against your existing account.
No — because access depends on your local law and eligible region, some parts of how this policy applies can vary depending on where you're signing in from. Where a mandatory local rule differs from what's written here, that local rule takes priority over this policy.
Use the support route inside your account, or the contact path shown in the footer if you haven't opened an account yet. Mention your registered email or number so the question gets matched to the right account record instead of sitting in a general queue.
Cookies on our site are mainly used to keep your sign-in active and remember settings like language, not to build a profile that follows you across unrelated websites. Where a cookie serves a different purpose, we describe that separately rather than labelling everything the same way.