Your Data Handled On Clear Terms
This page sets out how 777cb apk collects, uses and safeguards the details you share when you open an account. You will see which records we keep for...
How We Handle Your Account Records
We collect the least we can: your name, contact details, device signals and the transaction references that appear when money moves through JazzCash, Easypaisa, SadaPay or Raast. Where local law permits, we also hold short access logs so we can spot an unusual sign-in before anyone reaches your balance. We do not sell personal records. Sharing is limited to the payment partners
confirming your transfers, the specialists keeping our servers online, and authorities who ask in writing. Access is offered in supported regions, and any change to what we hold is shown in the text on this page. You may ask to see, correct or delete your details at any time, and those requests are logged and answered inside the timelines the applicable rules
allow.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach Us About Your Records
Policy questions should not sit unanswered. Our support desk takes data requests from inside your account and by email, replying in English. Say what you need, whether that is a copy, a correction or a deletion, and we log it the moment it arrives.
In-Account Support Desk
Open your account, head to the help area and raise a policy ticket. Every request arrives with your account reference attached, so the team can trace the exact records you mean.
Email Requests
Send a written request to the policy address on this page and keep our reply. Email suits access and deletion asks because you hold a dated record of the exchange.
Reply Timelines
We acknowledge every data request within two working days and aim to finish simple corrections inside a week. Anything touching a payment reconciliation takes longer, and we explain the delay.
Who Writes And Updates This Page
One named owner signs off every revision here, and a second reader checks the wording before anything goes live. Where a clause depends on Pakistani rules, we say...
Named Owner
One role signs off every change to this page. Ask who approved a wording update and we can name that...
Plain Drafting
We write short sentences and avoid clauses that need a second read. Where legal wording is unavoidable, a plain line...
Dated Revisions
Each version carries a date at the foot of the page. Compare any two dates and you can see what...
Secure Handling
Account access runs over encrypted connections, sign-in attempts are recorded, and staff work under role-based permissions, so only people handling...
Third-Party Limits
Payment partners and hosting providers get only what their job needs. We do not pass marketing lists on, and partners...
Regional Clauses
Some terms shift with where you live. The text marks which clauses cover Pakistan-based accounts and which cover other regions...
How This Page Matches Our Others
You should not have to reconcile four documents written in four different voices. Our legal pages share one structure, one revision process and one contact route, so a...
| Shared Definitions | Terms such as account data, transaction reference and retention period carry the same meaning on every legal page we publish, so you never learn the vocabulary twice. |
|---|---|
| One Contact Route | The support desk inside your account handles questions about any of our legal pages. No separate address is needed for cookie queries, corrections or deletion requests. |
| Matched Revision Dates | When a change to one legal page touches another, both are updated the same day and each revision log carries the change, keeping the whole set in step. |
| Aligned Cookie Labels | Cookie categories named on this page match the labels in our consent panel word for word, so the choice you make on screen lines up with what you read. |
| One Retention Rule | How long deposit references, sign-in logs and support tickets are kept is stated once and repeated identically across the legal set, so no two pages disagree. |
| Marked Regional Rights | Where a right applies only in certain regions, each legal page marks it the same way, so a limit is obvious without laying two documents side by side. |
| No Conflicting Promises | Nothing in our public copy overrides what these legal pages state. If a campaign message seems to clash with the policy, the policy text is the version that applies. |
The Sections You Will Read Here
This page keeps legal padding to a minimum and specifics up front. You get a clear list of what we collect, a plain account of who...
Summary Panel
The opening panel gives the short version: what we collect, why we need it and which choices sit in your hands. Read that first and the longer clauses can wait.
Context Chips
Small chips name the rails your transaction records come from, covering JazzCash, Easypaisa, SadaPay and Raast, so you can tell which clauses touch your payments and which do not.
Your Choices Blocked Out
Access, correction and deletion sit together with the steps spelled out. Each one tells you what to send us, where to send it, and how long an answer usually takes.
Retention Table
A short table pairs every record type with the period we keep it. Sign-in logs, support tickets and transaction references all appear, so you know when each item leaves.
Revision Log At The Foot
Dated entries near the bottom of the page show each change and what moved with it. Trace a clause back through earlier versions instead of wondering when the wording shifted.
Cookie Controls
Cookie categories and the switches that control them are described on this page before you meet the consent panel, so your choices make sense once the banner appears.