Your Privacy, Explained In Plain English
Every time you sign in to az777 you hand us details that matter — your name, contact number, and the JazzCash or Easypaisa rail you use to move...
What We Collect And Why We Hold It
az777 collects only what an operating account needs: your name, date of birth confirmation, contact number, email, login and device records, and the transaction trail behind your JazzCash, Easypaisa, SadaPay or Raast transfers. We hold that so you can sign in, so payouts can be checked against the rail that funded them, and so we meet record-keeping duties that apply to us
where local law permits. Retention depends on the jurisdiction your account is registered in and on the rules a payment partner sets, so supported regions may differ and the schedule in your account settings governs you. We do not sell personal data, and share it only with processors that run the service or a regulator with a lawful right to ask.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching Our Privacy Desk
Data questions shouldn't sit unanswered. Live chat is staffed around the clock by agents trained on this document, the privacy mailbox replies inside one working day, and your profile carries a panel for downloads and corrections you can handle yourself, without waiting on a reply.
Live Chat Window
Open the chat bubble inside your account and a privacy-trained agent picks up, usually within a minute. They confirm what we hold, explain each toggle, and raise a formal request for you.
Privacy Mailbox
Write from the address registered on your account and a ticket number comes straight back. Copy and correction requests are answered inside one working day, and more involved ones within a week.
Profile Data Panel
Your profile holds a panel for downloading a machine-readable copy of your records, updating contact details, and switching off optional uses you no longer want, without messaging anyone.
How This Document Stays Current
This document is written and kept current by the team that actually handles account records, not by an outside agency. Every revision carries a date stamp and a short line saying what...
Named Data Lead
One named lead owns this document and signs off every change, so there is a single person accountable when you raise a question about your records.
Version Stamps
Each revision carries the date it went live and a short line describing what moved. Prior wording stays reachable so you can compare what applied when you registered.
Plain-Language Lines
Where a clause is legally necessary but hard going, a plain-English line sits beneath it. The legal wording still binds; the summary just helps you understand it first.
Processor List
We set out the kinds of third parties that touch your data — payments, identity checks, hosting, messaging — and why each one needs access, refreshed as our suppliers change.
Region Mapping
Retention and transfer rules differ across supported regions. Where your account is registered decides which column applies, and we say so plainly instead of hiding it.
Encrypted Sessions
Sign-ins, account forms and payout confirmations travel over encrypted connections, and staff access to full records is limited to the teams that need it and logged.
How This Page Fits Our Other Policies
The wording here matches our sibling documents, so you never have to guess which definition applies. Where two pages overlap we use the same terms for the same...
What You'll Spot On This Page
The layout is built so you can find one answer without reading the whole thing. A jump bar sits above the first heading, retention periods appear in a...