Reference

How We Protect Your Account Data

This page spells out what account, device and payment details Uttaran20 collects the moment you log in from Dhaka or any other part of Bangladesh, and exactly how we use that data to match your bKash, Nagad or Rocket transfer to the right wallet.

bKash, Nagad, Rocket data stays account-linkedOTP login, no shared credentialsData handling follows local law & regionNo third-party marketing lists
Uttaran20 How We Protect Your Account Data
REACH OUR PRIVACY TEAM

Where To Ask About Your Data

Got a question about what we hold on your account, or think a Nagad reference number is attached to the wrong profile? Our support desk handles privacy requests the same way it handles a stuck withdrawal — you open a ticket, we verify who you are, then we act on it. Live chat is the quickest route if you're mid-session on the app or browser; email works better for anything that needs a written record, like a formal data-correction request tied to your bKash or Rocket wallet.

Live Chat Open live chat from your account dashboard for quick privacy questions — flagging a wrong wallet reference or asking what device data we've logged takes a few messages, not a form.
Email Support Write to our support inbox when you need a data-correction request on record, such as a KYC name mismatch tied to your Nagad or Rocket account.
Account Verification Desk If a withdrawal check needs your data reviewed, the verification desk confirms your identity before touching any stored bKash, Nagad or Rocket transaction details.
SECURITY BEHIND THE SCENES

How We Keep Account Data Secure

Account security starts at login: we use OTP verification rather than static passwords stored in plain text, so a compromised phone number doesn't automatically mean a compromised wallet. Session cookies keep you logged in between a phone browser and desktop tab without re-entering details each time, but they don't feed outside ad networks. We retain transaction and identity records only as long as needed for dispute handling and verification, then age them out. If you want a copy of what's on file, or need something corrected, support routes that request to the team that manages account data directly.

OTP Login Security We verify account access with a one-time code sent to your registered number instead of relying only on a static password, cutting down on account takeover risk.
Cookie Use Session cookies keep your login active between the mobile browser and desktop tab; they support continuity, not third-party ad tracking across other sites you visit.
Data Retention Transaction references from bKash, Nagad and Rocket, along with KYC records, are kept only as long as dispute handling or account verification reasonably requires it.
Request Changes If a wallet number, name spelling or device record is wrong on your account, support can review and correct it once your identity is confirmed.

Common Questions About Your Data

Here are the questions we hear most often about how Uttaran20 handles account, wallet and device data — from what gets stored when you deposit through bKash or Nagad, to how long records stick around and who to contact if something needs fixing on your profile.

Yes — we keep the wallet number and transaction reference tied to your account so a deposit or withdrawal can be matched correctly and verified if a dispute comes up.

Yes, contact support and ask for a summary of the account and device data attached to your profile; we'll confirm your identity first, then share what's on file.

No — account, wallet and device details are used to run and secure your Uttaran20 account, not passed on to advertising networks or outside call centres.

We keep transaction and identity records for as long as dispute handling and verification reasonably need, and retention can vary slightly depending on your region's rules.

Flag it through support right away; a mismatch between your KYC name and your Nagad or Rocket wallet can delay verification until we correct the record together.

Mostly yes, but access and specific data handling can depend on your local law and eligible region, so some details may differ from one area to another.
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.