Reference

Privacy Policy: What We Record

Two things matter on this page: what 35db records when you open an account, and what you can ask us to do with it.

Account data explainedCookie choicesAccess requestsWallet recordsDevice details
35db Privacy Policy: What We Record
HOW WE HANDLE IT

Cookies, Sign-In and Retention

Three things decide how your data behaves here: the cookies on your browser, the one-time code on your phone, and how long we keep a record before it goes. Sign-in codes go to your registered mobile number every time, so a session cannot hop to a new handset without you. Cookies stay small — session and language only. Retention follows the job: wallet records stay while a verification or a dispute is open, then leave.

Cookie Control

Session cookies keep you signed in and remember your language; they do not build an ad profile. Clear them in your browser and the next login simply asks for a fresh one-time code.

Sign-In Security

Every login is checked with a one-time code sent to your mobile number. Change handsets and the code still goes to that same number, so nobody else can carry your session across.

What We Keep and How Long

We hold wallet and transaction records only as long as verification, dispute handling and the legal duties that apply to us need them. Once that work is done, they go.

Changing or Removing Data

Ask for a correction and we fix the record. Ask for deletion and we explain what can go, and what has to stay for transaction records under the law that applies to you.

DATA REQUEST DESK

Reaching 35db About Your Data

Privacy requests should not feel like a maze. You have three ways in: write to us from the mobile number on your account, open chat from the lobby on your phone, or send a bKash, Nagad or Rocket transaction ID if a payment question is behind the request. Whoever picks it up can see your account wallet record, so you will not be asked to repeat the same details twice. Anything touching your legal rights goes straight to the team that handles those requests.

Team online

Account Data Request

Write in from the email or mobile number tied to your account and say what you need — a copy of your details, a correction, or a deletion request where local law allows it.

Chat From Your Phone

Open chat from the lobby on your handset and ask for the privacy desk. Keep your registered mobile number handy so we can pull your account wallet record without a long back-and-forth.

Wallet Records Check

If a bKash, Nagad or Rocket transfer needs proving, send the transaction ID and the time you sent it. We match it against your account record and reply on the same thread.

Privacy Questions We Get Asked

Rights differ by country, so we answer the common ones here and leave the rest to a real conversation. If you want to know what sits on your account right now, ask and we will read it back to you from the record. Anything about wallet records, cookies or a correction lands with the same team.

Your mobile number, the wallet number you use for bKash, Nagad, Rocket or Upay transfers, the device and browser you sign in from, and the transaction records your account wallet generates.

Only with the payment providers that have to see a transaction to move your money, and with authorities where the law in your region requires it. We do not sell data.

You can clear cookies in your browser and still sign in with a one-time code, though the lobby will no longer remember your language or keep you signed in between visits.

Message us from the mobile number on your account and say what you want to see. We confirm it is you, then send the record back through the same channel.

No. Your wallet number and transaction history sit inside your own account and are only seen by you and the staff who handle a payment query for you.

Yes. Whether you can hold an account depends on your local law and eligible regions, and the privacy rules that apply to you follow that same line.
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.