LEGAL REFERENCE

How 777ox Handles Your Account Data

This privacy policy sets out exactly what we collect when you open an account with us, why we need it, and the choices you hold over it. You...

Account data onlyRupee rails coveredClause-by-clause wordingRevision dates shown
777ox How 777ox Handles Your Account Data

The Ground Rules We Hold To

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY DESK

Reaching Our Privacy Desk

Privacy questions reach a real desk rather than a queue that never moves. Write to our privacy contact, or open live chat from inside your account, and a person answers you directly. Keep your registered email to hand so we can match the request to the right record and reply without delay.

Team online

Privacy Mailbox

Write from the email address registered to your account and we confirm receipt the same working day, whether you want a copy, a correction or a closing date.

Live Chat Window

Open chat inside your account and ask for the privacy desk. Chat runs daily across Pakistan hours, so a data question can be settled before you transfer again.

Written Requests

Send a written request and we log it, date it and reply in writing, keeping the letter in your file so both sides point to the same record later.

HOW WE PROVE IT

Signals That Back This Policy

We wrote this policy so you can check our claims against your own account. Each promise maps to something you can see, ask about or test, from the records in your transaction...

Data Map Written Down

Every field we hold is listed in plain words with a reason beside it, so you can match our list against what appears inside your own account pages.

Dated Versions Kept

We date every rewrite and keep earlier versions on file, so when a clause changes you can read the wording before and after instead of guessing what moved.

Everyday English

We write our clauses in everyday English rather than lawyer-only English. Where a legal phrase is unavoidable, we explain it in the same paragraph so you never open a second page.

Named Desk Owner

A specific privacy desk owns this page and answers for it, so when you raise a point you deal with the same team that drafted the clause.

Local Practice First

Our clauses are shaped around Pakistani practice, from rupee settlement records to the way JazzCash and Easypaisa confirm a transfer, and we adjust quickly when a rule changes.

Consent Before You Tap

Sign-up screens show what you are agreeing to before you tap accept, with a direct link to the matching clause, so no part of this policy arrives as a surprise later.

How This Page Lines Up

This page shares its wording with the sibling pages beside it: terms, cookies, cashier rules, identity checks and closure. Move between them and the same definitions apply, so...

Terms of UseThe account rules you accept at sign-up use the same defined terms as this page, so a dispute starts from one shared set rather than two competing versions.
Cookie StatementCookie rules line up with the consent wording here, so the choice you make on your first visit matches the permissions described in this policy, with no second setting to find.
Identity ChecksVerification steps on our identity page follow the same retention periods listed here, so nothing you upload for a check sits on file longer than this policy allows.
Cashier TermsRupee cashier pages reuse the transfer-record wording written here, covering how JazzCash, Easypaisa, SadaPay and Raast references are stored once a transfer settles, and for how long.
Account ClosureClosing your account follows the deletion timetable set out in this policy, with the same exceptions for records we must retain under local rules after you leave.
Complaints RouteOur complaints page points back to the privacy desk named here, so a data concern and a service concern travel the same tracked path and reach a named owner.
Mobile App TermsApp-side permissions set out in our mobile terms match the device data listed in this policy, so what the app reads on your phone is the set we name here.
PAGE LAYOUT CUES

Signposts Across Our Policy Page

The layout is deliberate. Summary strips open each part, clause numbers let you cite a line when you write to us, and chip rows name the rails your...

Summary Strip Each part opens with two or three larger lines stating...
Clause Numbers Numbered clauses give us a shared reference. Quote a number...
Rail Chips Chip rows naming JazzCash, Easypaisa, SadaPay and Raast sit beside...
Change Log Line A dated line near the foot of the page marks...
Choice Panel One panel gathers every option you control, from marketing messages...
Table Rows Retention periods sit in short table rows instead of buried...

Privacy Questions We Get Asked

Your name, contact details, date of birth and the identity documents local rules require, plus device and session records created when you sign in. Transfer references sit alongside those.

Only what a transfer needs, meaning the reference, the amount and the account number, to the rail handling it, whether that is JazzCash, Easypaisa, SadaPay or Raast. Nothing more leaves our hands.

Transfer records stay for the period local rules set, often several years, and account records go once you close and that window passes. We delete what we are not obliged to hold.

Yes. Write from your registered email and ask for a copy. We confirm receipt the same working day and send the record once your request is matched to the account.

Only if you leave that option switched on. Every message carries a one-tap opt-out, and switching it off never touches your account access or the way your transfers clear.

Use the privacy desk details on this page, whether by email, live chat or a written request. Quote the clause number if you have it and we will trace the answer to its owner.