Against account terms
Account terms set out what you may do on cb7777. This page sets out what we store while you do it, so the two belong together rather than replacing one another.
We wrote this page so you know exactly what cb7777 keeps, why we keep it and how you can change it. It covers accounts opened in supported regions...
Where local law permits, cb7777 controls the account data you give us, and this policy applies across the supported regions we serve in Pakistan. We collect only what an account needs: your name, contact details, a date of birth check, device and login signals, and the transaction trail your wallet or bank produces. Rails such as JazzCash, Easypaisa, SadaPay, NayaPay and Raast
pass us a reference rather than your credentials, and that reference stays with the transfer it belongs to. If a requirement in your province asks for something different, that rule wins over this page. We flag material changes here, and we keep earlier versions on file so you can compare them.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Your privacy questions reach a real queue rather than a void. Send a request from inside your account and it is logged against your profile, so whoever answers can see the same records you are asking about. Live chat covers Pakistan hours.
Open your profile, choose the help tab and send your data question from there. Because you are signed in, the team can match it to your records straight away.
Prefer email? Use the address listed inside your account and include your registered number. That lets the team locate your profile without asking you for it twice.
Live chat covers Pakistan time zones through the day for quick questions about what we hold. For a full copy of your data, use the message route so the request is logged.
This policy is kept by the cb7777 operations team, the same people who run sign-up, payments and support. Drafts get a second reading against how our systems actually behave, and we revisit...
Nobody outside cb7777 drafts this policy. The team that builds your account flow and payment checks writes the wording, so what you read matches what the platform actually does.
Every change gets a second reading before it goes live. A reviewer compares the new sentences against how our systems handle sign-up details and payment references each working day.
When we edit this page we stamp the date at the top. That way you can tell whether the version you read last month still applies to the account you hold.
We cut legal padding where a short sentence does the job. If a clause needs a legal term, we unpack it in the same paragraph rather than leaving you to look it up.
The wording is checked against the markets we serve, Pakistan included, so local requirements about holding records shape this page rather than a template written for another country entirely.
Questions we field at the privacy desk feed back into this page. When enough account holders ask the same thing, the answer moves here instead of sitting in private replies.
cb7777 keeps several policy pages, and they read as one set. The account terms govern how you use the platform, the payment page explains wallet and bank flows, and this page covers...
Account terms set out what you may do on cb7777. This page sets out what we store while you do it, so the two belong together rather than replacing one another.
The payment page explains how a JazzCash or Raast transfer travels. Here we explain the reference we keep once it lands and how long that record stays on file.
Cookie wording covers what your browser keeps on your device. This policy covers what our servers keep, which is the longer-lived record tied to your registered account number.
Security pages describe how we guard access to your account. This policy names the login signals we keep, and sets out which colleagues can look at them when a case needs it.
A few topics appear on more than one page, payment references being the obvious one. Where that happens we reuse identical wording, so you never have to guess which version is current.
If two pages ever disagree, account terms take priority on usage questions and this policy takes priority on data questions. We correct any clash as soon as it is spotted.
Where a single change touches several pages, we update them together. The dates then line up, so you can tell at a glance whether the wording you saved is still in force.
You do not need to study a legal page to see how cb7777 treats your details. The signals sit in front of you: masked account numbers...
Your wallet and bank details show in shortened form once saved. You see enough to recognise the account you chose, while the full number stays out of casual view on shared devices.
A quiet timer ends idle sessions on shared phones and laptops. You can pick up where you left off by signing in again, and each fresh sign-in adds a new entry to the access record.
Every transfer produces a slip with a reference number and a time stamp. Keep it if you plan to ask us about a record later, because it points straight at the transaction.
Sign-in alerts and transfer confirmations arrive as separate messages. If something you did not expect appears in that trail, contact us and we will look at the session behind it.
Your account page lists the details we hold and lets you correct the easy ones yourself. Anything you cannot edit, such as a verified name, goes through support instead.
When you close an account, the page tells you what gets removed and what we must retain for transaction records. You get a written confirmation once the account is shut.