Reference

Privacy Policy, Written the Short Way

This page spells out what bd9999 records when you open an account, pay in with bKash, Nagad or Rocket, and pick up where you left off on your phone the next day.

Account data onlybKash, Nagad, RocketCookie choicesYour request path
bd9999 Privacy Policy, Written the Short Way
HOW WE HANDLE IT

Cookies, Security and Retention in Practice

Handling your data here is deliberately boring and repeatable. Passwords are hashed, sessions are tied to your device, and the reference from a bKash, Nagad or Rocket transfer is stored against your account so a disputed amount can be traced. Cookies do a narrow job: keeping you signed in, remembering your language, and holding the session while you move between Baccarat Night Room and Crash Lightning. Retention follows one rule — keep what a wallet partner or local law needs, drop the rest. Every request you send gets a written reply from a person, not a form letter.

Data We Keep

Your account number, the wallet number you pay from, device and session records, and payment references. Nothing beyond what runs the account and settles a transfer gets collected.

Cookies We Set

A sign-in cookie keeps your session alive, a preference cookie remembers your language, and a security cookie flags a login that looks off. Clearing them in your browser resets sign-in.

Security Steps

Passwords are hashed, a one-time code goes to your phone at sign-in, and changing the wallet number on your account triggers a fresh check before any transfer is accepted.

Retention and Requests

Payment records stay while a wallet partner or local law requires them. Ask us to close the account and we delete the rest, telling you what went and what had to stay.

ASK US DIRECTLY

Where to Send a Data Request

One place handles every data question: our support desk, reachable from the help tab inside your signed-in account and at privacy@bd9999. Write from the number or email already linked to your account so we can find you without asking for a password — we never ask for one. Tell us what you want changed, corrected or deleted and which wallet you pay with, and we take it from there. Anything touching a live payment gets checked against the bKash, Nagad or Rocket reference before a record is altered.

Privacy Mailbox Send your request to privacy@bd9999 with your account number and the wallet you use. Say whether you want a copy, a correction or a deletion and we route it to the right desk.
In-Account Help Tab Signed in but not sure where to begin? The help tab opens a message thread that already carries your account ID, so you do not repeat yourself or share a password.
Wallet Reference Check If your question is about a bKash, Nagad or Rocket payment, keep the transaction ID handy. It lets us match the record on our side without asking you for anything sensitive.

Privacy Questions We Get Asked

Six questions cover most of what lands in the mailbox. Each answer points at the actual step rather than a policy clause, so you know what happens after you send something in. If yours is not here, writing to the address above is the shortest route.

Your account number, phone number, the wallet number you pay from, device and session records, and the reference for each bKash, Nagad or Rocket transfer. Your wallet PIN never reaches us.

Yes. Write to privacy@bd9999 from the contact details on your account and ask for a copy. We confirm the account is yours before sending anything, then reply in the same thread.

Ask us to close it and we delete what we are not required to keep. References tied to a bKash, Nagad or Rocket transfer stay while a wallet partner or local law needs them.

Only where it runs the account: wallet partners who settle a payment, and providers who host the lobby. We do not sell your details, and sharing rules follow the law where you live.

Because a session on a phone we have not seen is the first sign of someone else in your account. A one-time code goes to your registered number and confirms it is you.

Access depends on local law and eligible regions. Where we are not open, we do not keep data we have no basis to hold, and any request you send still gets an answer.
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.