Reference

The Privacy Policy Behind Your Account

Our privacy policy names every field we keep: your mobile number, the bKash, Nagad or Rocket reference tied to a deposit, and the login records that follow each sign-in.

bKash, Nagad, Rocket referencesOTP login trailConsent you can withdrawWritten replies to requests
7i77com The Privacy Policy Behind Your Account
SECURITY AND RETENTION

How We Hold Your Records

Cookies here do two jobs: they keep you signed in, and they tell us which pages load slowly on mobile data. You can clear them from your browser whenever you like, though the login cookie is the one you will need to replace. Passwords never sit in plain text, and every sign-in needs the OTP we send to your registered number. Records tied to a deposit or a disputed round stay for the period our payment partners and record-keeping rules require, then leave on our normal cycle. Ask and we will confirm what applies to you.

Login and OTP

Your password is stored hashed, and a fresh OTP goes to your registered number at each sign-in. If a login looks unfamiliar, tell support and we lock that session.

Cookies on this site

We set a session cookie to keep you signed in and a small set to measure page speed. You can clear both from your browser, though you will log in again.

Retention windows

Wallet statements and bet records stay for the period our payment partners and applicable rules require. Once that window closes, they leave our active systems on the normal cycle.

Changes and deletion

You can ask us to correct a name, update a number, or remove optional data. We confirm what changed and what we must keep, and log the request on your account.

RAISING A REQUEST

How to Raise a Privacy Request

One route, one reference. Write to our privacy desk from the email or mobile number registered on your account and say what you want: a copy of your data, a correction, or a stop on optional processing. If the request touches a deposit, paste the bKash, Nagad or Rocket transaction ID so we can pull the matching record before replying. In-app chat suits quick questions. Email keeps the paper trail if you want something you can point to later.

Privacy desk email Send your request from the mobile number or email registered on your account and state what you want changed. We reply to that same address so the thread stays with you.
In-app chat Short questions about cookies or login work well in chat. Open your account, tap support, and keep the ticket number — it links the conversation to your account history.
Wallet reference For a payment-related privacy request, keep the bKash, Nagad or Rocket transaction ID to hand. It lets us match the record without asking you for anything extra.

Questions About Your Account Data

Six questions cover most of what people ask us. If yours is about a single transaction rather than the policy itself, start with the wallet statement — that reference number answers more than a general question can. Everything else, from a copy request to a name correction, goes through the privacy desk and gets a written reply. Keep that reply. It is your record of what we told you, and when.

Your registered mobile number, name, wallet references from bKash, Nagad or Rocket, deposit and withdrawal history, login records, and the games or markets you opened while signed in.

Yes. Write from the number registered on your account and ask for a copy. We pull the records attached to your user ID and reply to that same address.

We share the reference for a specific transaction with the wallet you used, so the payment can be matched. We do not hand your full profile to a wallet or a game provider.

Message support with the correction and, where a name is changing, a document that matches it. We update the record and confirm in writing once it is done.

You can close the account and ask for removal. Records tied to payments or a disputed round stay for the period our partners and applicable rules require, then go.

It depends on where you live and on rules we must follow as an operator. Access and eligibility depend on local law and eligible regions, and we say plainly where a request cannot be met.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.