Reference

Privacy Policy: What We Hold and Why

Your records are what this page is about: what we store when you open a 666kapk account, what we deliberately leave with your wallet provider, and how you get a detail corrected or removed.

Account dataWallet referencesMobile OTP loginCookie choicesRemoval requests
666kapk Privacy Policy: What We Hold and Why
ASK US DIRECTLY

Reaching Us About Your Data

Privacy questions go to the same team that handles account help, so you are not bounced between departments. Open the chat panel inside your logged-in account and the message arrives with your account number attached, which saves a round of questions. Email works too if you would rather keep a written thread. Either way, quote the phone number on the account and tell us what you want changed — access, correction or removal — and we point you to the next step.

Team online

In-account chat

Sign in, open the chat panel and your message carries the account number with it. Ask for a copy of your records or a correction in the same thread.

Email the data team

Write from the address you used at registration so we can match the request to your profile without adding another verification step before we start.

Payment reference desk

If a bKash, Nagad or Rocket load looks wrong, send the wallet transaction ID. We check it against your account wallet and answer in the same ticket.

HANDLING HABITS

How We Handle Your Records

Handling data at 666kapk follows a short set of habits rather than a long rulebook. We collect what a wallet load and a login actually produce, keep it while the account stays open and a payment dispute could still be raised, and let you ask for a copy or a deletion from inside the account you already use. Cookies are split by job: the ones that keep you signed in, and the ones that show us how the lobby behaves on a phone screen. Nothing on that list is sold to outside lists.

Details we keep

Your registered mobile number, the name on the profile, login device details and the wallet references behind each bKash, Nagad or Rocket load. Wallet PINs stay with your provider.

Cookies and sign-in

A small cookie keeps you signed in between visits so you are not typing a fresh OTP every time you switch tabs. Analytics cookies record page flows only, never wallet details.

Security on your phone

We treat an unfamiliar device as a reason to ask for an OTP again. If a login alert looks wrong, change your password first, then message us from inside the account.

Retention and changes

Records stay while the account is active and for the stretch in which a payment dispute could be raised. Ask us to correct or remove a detail and we confirm what was done.

Privacy Questions You Send Us

The same handful of questions lands in our inbox every week, so here they are answered in the open. Each answer below deals with this policy alone — what we hold, what you can ask for, and where local law changes the result. If yours is not here, the chat panel inside your account reaches the team that handles these requests. Keep it short and give us the registered number, since that is what we search by.

It covers the personal details you give us when you open a 666kapk account, what our pages record as you browse, and the choices you have over both.

No. That PIN belongs to bKash, Nagad or Rocket and never reaches us. What we store is the transaction reference the wallet returns after you complete a load.

Yes. Ask from inside your account or by email and we gather the profile details, login records and payment references tied to your number, then send them to you.

Message us with the phone number on the account and say what you want removed. We explain what can be deleted and what a payment or legal rule requires us to keep.

We would rather you did not. An unfamiliar device triggers another OTP, and a shared login weakens the device records we rely on when a session looks wrong.

It can. Access, eligibility and certain rights over your records depend on the law where you live and on whether your region is supported, so check both before you register.
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.