Reference

How goredb Handles Your Account Data

goredb keeps your account privacy tied to what your wallet actually needs — no more, no less. We collect only the phone number, wallet reference and device details linked to your bKash, Nagad or Rocket transfers, and how that data gets used depends on…

Data kept to what's neededbKash & Nagad transfers protectedAccount access logs reviewedLocal law applies
goredb How goredb Handles Your Account Data
REACH OUR TEAM

Where to Send a Privacy Request

Questions about your account data usually come down to one of three things — a copy request, a wallet dispute, or a quick clarification. We keep the channels for each one direct so you're not stuck explaining your bKash or Nagad activity to more people than necessary. Pick the path that matches your question below.

Privacy Requests Send a written request through our support ticket form if you want a copy of your account data or ask us to delete records tied to a closed bKash or Nagad wallet.
Wallet Verification Queries If a bKash, Nagad or Rocket transfer looks off on your statement, message support with the transaction ID so we can trace it without exposing your full wallet history to anyone else.
In-App Support Chat Open the chat option inside the goredb mobile site or app and ask directly about how your login details, device fingerprint or wallet data are stored on our side.
HOW WE PROTECT YOU

How We Keep Your Wallet Details Safe

Trust on a privacy page comes down to specifics, not promises — what we store, how long, and who can ask us to change it. Here's the short version of how goredb handles account data day to day, from the moment you sign in to the point a record gets cleared out.

Data Handling

We store the minimum account fields tied to your identity and wallet — phone number, transaction references, device ID — and avoid holding anything beyond what a bKash, Nagad or Rocket transfer needs.

Cookies & Sessions

Your browser or app session carries a short-lived cookie that keeps you logged in and remembers your last screen, so switching from phone to desktop doesn't force a fresh sign-in every time.

Account Security

Every login runs through an OTP check tied to your registered mobile number, and unusual sign-ins from a new device trigger a fresh verification step before your wallet balance is shown.

Retention & Deletion

We keep transaction and login records only as long as dispute resolution or local law requires, then phase them out of active systems — you can ask us to check what's still held.

Privacy Policy Questions From goredb Players

These are the questions we hear most often about account privacy on goredb, from what we collect during sign-up to how a wallet-linked record gets cleared once you close an account.

We collect your phone number, wallet details linked to bKash, Nagad or Rocket, and basic device data used for login verification — nothing beyond what's needed to run your account and process transfers.

Your wallet reference and transaction ID stay within the payment chain needed to confirm a transfer; we don't pass this data to outside advertisers, and sharing beyond that follows your local law.

We hold transaction and login records long enough to resolve a disputed transfer or support a wallet verification request, then remove them from active systems once that need passes.

Yes — send a request through our support channel and we'll process it based on what local law and eligible-region rules allow for closing an account and clearing stored records.

We use session cookies to keep you signed in across your phone and desktop and to remember basic preferences; these don't track your activity outside the goredb account experience.

Reach our support ticket form or the in-app chat with your registered phone number ready — that's the fastest path to a privacy or wallet-data question being looked into.
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.