Reference

The Rules Behind Your Account

Your ckbaje account runs on one short set of terms, and this page sets them out in plain English. A bKash deposit, a sign-in from a new phone, a withdrawal request — the same rules follow you across every part of the site.

bKash, Nagad, RocketAccount accessFair useContact path
ckbaje The Rules Behind Your Account
ACCOUNT HELP DESK

Ask Us Before You Deposit

Confused by a clause? Ask us first, not after the money moves. Support handles term questions over live chat and email, and both routes reach someone who can open your account rather than paste a canned reply. Tell us what you were doing when the rule seemed to bite: a Nagad transfer that bounced, a sign-in that locked, a table that refused to load in the browser. We will point to the clause and the fix. On eligibility we answer from the law where you live, even when the answer is one you did not want.

Live chat Chat opens from the account menu on mobile and desktop. Use it for clause questions, a stuck sign-in, or a deposit that never landed in the wallet.
Email us Write from the address on your account so we can match the message to you. Attach the bKash or Rocket transaction reference whenever money is involved.
Wallet disputes If a transfer left your bKash or Nagad app but never reached the account, send the transaction ID. We trace it against the wallet record before answering.
DATA AND ACCESS

How We Handle Your Details

We store what an account actually needs: sign-in details, wallet history, and device records that let us flag a login from an unfamiliar phone. Cookies hold a session together between browser and app; clear them and you sign in again, which is normal behaviour rather than a fault. Records behind deposits and withdrawals stay as long as the law where you live requires, then they go. Want a copy of what we hold, or a correction to your name or number? Write from the email on your account.

Sign-in checks A new phone or a fresh browser asks for a one-time code before the account opens. That step exists so a borrowed handset cannot reach your wallet balance.
Cookies and sessions Cookies keep you signed in while you move between pages. Clear your browser and the session ends, so the next visit asks for your password again.
Records we keep Deposit and withdrawal records stay as long as the law where you live requires them, then they are removed. We do not hold them simply because we can.
Correcting your details Changed your Nagad number or moved address? Send the update from your registered email and we adjust the account after a short verification step.

Terms Questions We Get Often

The same handful of clauses comes up again and again in chat, so we have answered them here in the order people usually ask. If yours is not covered, the support desk takes it from there.

No. One account per person, tied to your own phone number and wallet. Two accounts under one name break the terms, and both can be frozen while we check.

Send support the bKash transaction ID from your app. We match it against the wallet record and credit the account once it clears, or explain why it was returned.

Any new version appears on this page and applies from the day it goes live. Larger changes get a message to your account before they take effect.

It depends on the law where you live and on eligible regions. We restrict access where a service is not permitted rather than ask you to work around it.

Yes. Ask from your registered email and we close it once the balance is settled. Records we must keep by law stay; the rest is removed.

Tell us straight away and change your password. We freeze the session and read the sign-in records, then decide from what the device history actually shows.
Reference

Terms & Conditions

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.