Reference

Your Privacy Policy, Plainly Written

This is the privacy policy for bigpari — what we record when you open an account, deposit through bKash, Nagad or Rocket, and pick the same session back up on your phone.

Account dataCookie useLogin and OTPYour requests
bigpari Your Privacy Policy, Plainly Written
DATA HANDLING

How bigpari Handles Your Account Data

Handling privacy well is mostly about not collecting things we have no use for. We ask for a mobile number, a name that matches your wallet, and nothing beyond what a payment check actually needs. Cookies exist to keep you signed in between pages, not to follow you around other sites. Clear them or switch from browser to app and the login simply starts again with a code to your registered number.

Data we hold

Mobile number, account name, wallet reference and transaction lines form the core. Device and browser details sit alongside so an odd login stands out. Ask for a copy of the whole set from inside your account.

Cookies and storage

A cookie keeps your browser session alive between pages; the app uses a stored token instead. Neither reads personal files on your handset. Clearing cookies or reinstalling signs you out, nothing more.

Login and OTP

Each login can be confirmed with a one-time code sent to your registered number, and a wallet change asks for the same check. If a session looks wrong, we close it and you reset from the app.

Retention and edits

Session logs are dropped sooner than transaction records, because payment disputes and audit rules need the trailing paper. Request a correction or deletion inside your account and we work through it with you.

REACH THE TEAM

Where to Send a Privacy Question

Privacy questions need a real person, not a form that disappears into a queue. Message us from the support tab inside your logged-in account so we can tie the request to your number without making you repeat everything by email. From there you can ask what we hold, request a correction, or close the account. We answer on the same thread, so the history sits in one place and you are not explaining it twice. If your region is not eligible, we will say so plainly instead of leaving the request open.

Team online

In-account message

Open your account, tap support and send the request from there. We confirm with a one-time code to your registered number before discussing anything tied to your wallet or transactions.

Email follow-up

Prefer email? Write from the address saved on your account so we can trace it back. Include your registered number and the exact change you want, and we reply on that thread.

Request checklist

Say whether you want a copy, a correction or a deletion. Name the wallet involved — bKash, Nagad, Rocket, Upay or bank transfer — and we pull the right records without guesswork.

Privacy Questions You Might Ask

Most privacy questions come down to three things: what you can see, what you can change, and who reads it. These are the ones our team answers most on the support thread. Send anything else from inside your account and we reply on that same thread. Eligibility counts too — access depends on local law and eligible regions, and where a region is not covered we do not hold an account for it.

It covers the account data we keep — mobile number, name, wallet reference, transaction lines and device logs — plus how cookies work, how long each record stays, and how you ask us to change something.

Yes. Send a request from the support tab inside your account and we confirm with a one-time code to your registered number before sending a copy of what is on file.

Only with the payment rail and processor completing your own transfer. It does not go to outside list brokers, and no third party gets it for marketing. Nothing is sold.

In the browser, a cookie keeps you signed in between pages until you close it or clear site data. The app uses a stored token instead. Either way, logging back in needs a code.

Write to us from inside your account with the specific change. We verify the request first, then act. Some transaction records stay where dispute and audit rules require them, and we tell you which.

Access depends on local law and eligible regions. Where a region is not eligible we do not open or hold an account, so there is usually no data to keep beyond the request itself.
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.