Shared Definitions
Terms such as account, wallet and verification mean the same thing on this page as they do in our account rules, so you are not decoding two vocabularies.
This privacy policy spells out what data eh777 collects when you open an account, where we store it and who may see it. It covers your registration details...
We collect only what we need to run your account: your name, contact details, verification documents and payment records from JazzCash, Easypaisa, SadaPay or Raast. We keep that data on encrypted servers and limit internal access to staff who need it for account checks, fraud screening or support tickets. We do not sell your details to third parties. Some processing is handled
by partners that support payments or verification, and those partners work under contract with us. Where local law permits, you can ask to see, correct or delete the data we hold, and we will answer within a reasonable window. Rules differ between supported regions, so this wording follows the law that applies to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our compliance team writes this policy and our legal advisors sign off on every revision before it goes live. When we change how we handle data, we update the wording here and...
The people who run account security write this policy. They see the payment flows, the verification queues and the support tickets, so the wording matches how the platform behaves.
Each revision passes an internal accuracy check covering plain language, deletion timelines and consistency with the rules that apply in supported regions. Nothing here goes live without that check.
We store dated copies of every revision. If you want to see what the policy said on the day you opened your account, support can pull that version.
We do not sell your personal details or trade them for advertising space. Payment records stay with the processors needed to move your money and clear withdrawals, nothing else.
Only staff with a work reason can open your file. Every lookup is logged, and unusual access patterns get flagged to the security team for follow-up the same day.
Where the rules in your region differ from the general wording, the stricter local requirement wins. That is how we keep this policy honest across supported regions.
This policy sits alongside our other legal pages and the same definitions run through all of them. Where a term appears in more than one place, it carries the same meaning each...
Terms such as account, wallet and verification mean the same thing on this page as they do in our account rules, so you are not decoding two vocabularies.
Where this policy touches account conduct, we point you to the rules page instead of repeating the clause, and both pages get updated together when something changes.
Anything about JazzCash, Easypaisa, SadaPay and Raast records reads the same way on this page as on our payments page, covering what we store and who sees it.
The verification steps we describe for withdrawals match the wording in our account pages, so you know which documents we ask for and how long checks usually take.
Response times and contact channels are listed the same way across every page. If live chat answers within a few hours here, that promise holds wherever you read it.
Encryption, access logging and device checks are described in identical terms throughout, so a security claim on one page never softens on another. Consistency is the point here.
When a clause is rewritten, we update it everywhere at once and log the date, so you get one clear version instead of two pages quietly disagreeing with each other.
Everything on this page is built for scanning, not squinting. You get a section bar near the header, plain language blocks underneath and a contact panel that stays...