Reference

Privacy Policy: What We Keep

This page sets out what apk333 keeps when you fund an account with bKash, Nagad or Rocket, why we keep it, and how you get it changed or removed.

No PIN requestsWallet reference keptCookie scope spelled outCorrection on requestClosure requests accepted
apk333 Privacy Policy: What We Keep
PRIVACY DESK CONTACT

Reaching the Privacy Desk

One desk handles privacy requests, and you do not need a long explanation to reach it. Write from the mobile number registered on your account so we can match the record without asking you for extra papers. If your question is about a bKash, Nagad or Rocket reference, paste the transaction ID in the first message and we can trace it in one pass. Requests that need a name change or a record copy may add one verification step, and we will tell you what is still missing instead of leaving the ticket open without an answer.

Privacy mailbox Send your request from the mobile number registered on your account, with the wallet reference if a payment is involved. We reply to that number and keep the thread open until you confirm it is settled.
In-account help chat Open the help icon inside your logged-in session for anything tied to your own record. Chat is verified by your session, so we can discuss your account without asking for your password again.
Payment trace request If a bKash, Nagad or Rocket transfer looks unmatched, send the transaction ID and the amount in taka. We check the wallet reference against our ledger and write back with what the record shows.
HANDLING AND RETENTION

How We Store and Protect

Your account record is built from four things: the number you register, the wallet name and reference returned by bKash, Nagad or Rocket, your session logs, and the handset you sign in from. Cookies do a narrow job here. They keep you signed in and remember the language you picked, and we read them for that rather than to follow you across other sites. Sign-in runs on a one-time code sent to your registered number, so an old password on its own will not open the account.

Wallet reference storage

Every bKash, Nagad or Rocket transfer returns a transaction ID. We store that ID beside the amount in taka, so a deposit can still be matched if the wallet confirmation lands after you close the app.

Cookies with a narrow job

Two cookies do most of the work: the session cookie that keeps you signed in and the one that remembers your language choice. Clearing your browser signs you out and resets both, and nothing else changes.

One-time code at sign-in

Each new device asks for a one-time code sent to your registered number. If a code arrives when you did not try to sign in, change your password and message the privacy desk the same day.

Retention and correction

Transaction evidence stays as long as local rules require. A misspelled name or an old address can be corrected on request, and we confirm the change in writing once the record is updated.

Questions About Your Account Data

Most privacy questions reach us just after a deposit, when a wallet reference and an account name do not quite line up. The answers below cover the ones the desk handles most, from wallet PINs to closing an account for good. If your own case is not here, write to the privacy mailbox from your registered number and we will reply in the same thread instead of sending you off to a different page.

Your registered mobile number, the wallet name and transaction reference from bKash, Nagad or Rocket, your gameplay and login history, and the device details that keep your session working.

No. The PIN is entered inside the wallet app, not on our pages. Our team will never ask for your PIN or your one-time code in chat, by call, or by message.

Write to the privacy mailbox from your registered number and say what you need. We may ask one verification question before releasing the record, then send it in the same thread.

You can ask us to close the account at any time. Transaction evidence may need to stay where local law requires it, and we will tell you exactly which records are held back.

Only to the parties that make the service work: the wallet operator confirming your transfer, our message provider sending your one-time code, and any authority we are legally required to answer.

Sign out after each session and clear the browser if you can. A one-time code goes to the registered number, so keep that SIM with you and change your password before handing the handset on.
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.