Reference

What We Collect and Why

This page sets out exactly what we record when you open an account wallet, fund it with bKash, Nagad or Rocket, and use the lobby from your phone.

Account wallet recordsbKash and Nagad deposit recordsRocket payment logsCookie and device dataDeletion requests
777abe What We Collect and Why
REACH THE TEAM

Where to Send Privacy Questions

Data questions get their own lane. Write to our privacy contact from the email tied to your account so we can match the request without asking you to repeat your details. Where you sign in from does not change the answer — the same terms apply whether you are in Dhaka or Chattogram. If you only want to know what is stored, that is a quick reply. A copy or a deletion takes a step more: we confirm the request, check your identity through the account, and tell you what we can action under your local law.

Team online

Account email

Send privacy requests from the address registered on your 777abe account. That single match lets us confirm it is you without asking for your bKash or Nagad PIN.

Wallet match

For data tied to deposits, we verify the wallet number used for your last Rocket or bKash transfer. Matching that number keeps your records out of the wrong hands.

Written reply

We answer in writing once a request is logged, so you hold a record of what was asked and what we changed, corrected or removed from your account file.

HOW WE HANDLE IT

Storage, Cookies and Account Access

Your data sits behind the same login you use for the lobby. Sign-in runs on a one-time code sent to your phone, so a password alone does not open your wallet or your history. Cookies do a narrower job: they keep the session alive and remember your language and device preferences. We set what we need to run the account; you can clear the rest from your browser whenever you like. Records linked to deposits stay for as long as payment and audit rules require in your region, and then they go.

One-time code login

Every sign-in sends a fresh code to your registered phone. No code, no session — that stops someone with a guessed password from reaching your deposit history.

Cookie control

Session and preference cookies keep you signed in and remember your settings. Clear them in your browser any time; the lobby will simply ask you to sign in again.

Retention window

Payment and audit records for bKash, Nagad and Rocket transfers are held for the period your local rules require. After that we delete or anonymise them.

Change requests

Ask us to correct a wrong phone number, drop marketing consent or close the account. We confirm in writing and tell you plainly what stays on file by law.

Your Rights Over Your Data

These are the questions our support desk sees most, answered the same way we answer them on chat. If yours is not here, send it through the account email above and we will write back with the specifics rather than a link back to this page. Nothing in this policy takes away a right your local law gives you over your own data.

The wallet reference number, the amount, the time and the method — bKash, Nagad, Rocket, Upay or bank transfer. We never store your wallet PIN or your full card number.

Yes. Send the request from your registered email and we close the account, then remove what we are not required to keep. Payment records tied to local rules usually stay.

No. We share data only where it is needed to run your account — the payment rail clearing your deposit, and the studios whose games you open — or where your local law requires disclosure.

Turn them off in your account settings, or reply to any message and ask. We action it on the account itself, so you still receive notices about your deposits and sign-ins.

Our support and risk teams, and only when there is a reason such as a payment query or unusual activity. Your history is never shown to other account holders.

Tell us and we will confirm what changes. Access to 777abe depends on your local law and eligible regions, so some features may not be available from your new location.
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.