Reference

Privacy Policy: What We Hold and Why

Your account at vocabbd rests on a short list of data we can name out loud: the mobile number you verify, the wallet details behind your deposits, and the session records that keep you signed in.

Plain-word policyCookie controlsData requestsOne-time code login
vocabbd Privacy Policy: What We Hold and Why
HOW WE HANDLE IT

Data Handling, Cookies and Account Security

Your login shows how we treat data in practice. We send a one-time code to your mobile number, you key it in, and the platform issues a session token so the code is not needed on every refresh. That token lives in a cookie — it is also why a round at Baccarat Payout or a BPL cricket market page does not reset when your screen locks. Clearing cookies on your phone signs that device out. We never ask for your wallet PIN, and your play record stays inside your account.

What we collect

Mobile number, name, date of birth confirmation, wallet details and the transaction records your account generates. We keep gameplay logs so a disputed round can be checked against the server record rather than anyone's memory.

Cookies and sessions

Session cookies keep you signed in, and a few preference cookies remember language and layout. You can clear them from your phone browser at any time, though the next login will ask for a fresh code.

Account security

A new device asks for the one-time code, your wallet PIN is never requested, and a session closes when a login looks out of place. Report anything odd from the help panel before trying again.

Retention and changes

Transaction records outlast chat logs. Ask for a copy, a correction or a deletion from your account and we will say what can be removed and what local law asks us to keep.

REACHING OUR TEAM

Ways to Reach Us About Your Data

We keep data questions on the same channel as account help, so you are not hunting for a separate desk. Message us from the panel inside your account and the thread carries your account ID with it, which saves a round of questions. If you would rather write, our support email takes privacy requests directly — put 'data request' in the subject line and tell us the wallet number tied to the account. Replies land back in that thread, not in a separate SMS.

Team online

In-account help panel

Open the help icon on your account page and the message carries your account ID automatically. Ask for a copy of your data, a correction or a deletion, and the same thread tracks the reply.

Support email

Write to the address listed on your account page and mark the subject line as a data request. Include the mobile number and the wallet you registered with so we can match you without guesswork.

Wallet verification replies

When a bKash, Nagad or Rocket transfer needs a second look, we message you inside the account first. Send the transaction ID back through that thread and the check keeps its own written record.

Privacy Questions We Get Asked

These are the questions our support desk fields most often about the privacy policy, answered the way we would answer them in a chat window rather than in legal phrasing. If yours is not here, the help panel inside your account reaches the same team.

Your mobile number, your name as given at verification, and the wallet number you register for bKash, Nagad, Rocket or Upay. After that we log the transactions, sessions and device details your account produces.

Yes. Send the request from the help panel inside your account or by email, and we will confirm what we hold, how it was used and which parties saw it for processing.

No. Payment details stay with the wallet operator handling your transfer. Outside firms doing hosting or fraud checks see only what their task needs, under contract and on our instruction.

A session cookie holds the token that keeps you signed in after the one-time code. Clear cookies and that device signs out; you simply request a fresh code the next time you log in.

Your profile closes and the app stops logging activity. Transaction and verification records remain for the period local law sets, because those are the records banks and auditors may ask to see.

Yes. Access depends on your local law and eligible regions, and some rights over your data shift with where you are. Write to us and we will set out what applies in your case.
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.