Privacy Policy
Your personal details are handled under a separate policy that matches the identity checks described here, so what we collect and why stays consistent across both pages wherever you read them.
Joining 777fp means accepting one clear set of terms that covers your account, your wallet transfers and every wager you place. Below we set out what you agree...
By opening an account you accept these terms in full, and they form the agreement between you and us. You confirm you are of legal age where you live and that nothing in local law bars you from using our services in supported regions. Your account is personal: sharing credentials, holding more than one account or letting another person wager from your
balance breaks the agreement and can lead to suspension. Money arriving through JazzCash, Easypaisa, SadaPay or Raast must come from a source registered in your own name, because we match every transfer to the identity on your account before releasing a withdrawal. Keep your phone number and wallet details current, since an expired wallet can pause a payout while we check it.
Every clause block below carries the operative wording.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write our terms the way we would want to read them: short clauses, plain English and no buried conditions. Where a rule depends on where you live, we say so, and...
Every clause is written to be read once and understood. If a rule needs two readings, we rewrite it rather than leave you guessing at what the paragraph was meant to say.
Each change to these terms carries a date and a short line on what moved. You can see whether an update touched wagering rules, payout timing or account access without comparing whole pages.
Wording that depends on jurisdiction is marked as such, because rules differ between provinces and between supported regions. Where something cannot apply to you, the clause says so plainly.
We refer to JazzCash, Easypaisa, SadaPay, NayaPay and Raast by name instead of a vague phrase like e-wallets, so you always know which transfer route a clause is describing.
Ask for anything in writing and you get it in writing, including the clause we relied on and the date it took effect. That record is useful when you raise a question later.
Account terms sit alongside the practices protecting your login: device checks, session timeouts, and identity matching applied to every cash-out request that our team handles before money leaves your balance.
These terms cover the account relationship. Privacy, cookies, verification and payout timing each have their own page, and they are written to line up with what you read here rather than contradict...
Your personal details are handled under a separate policy that matches the identity checks described here, so what we collect and why stays consistent across both pages wherever you read them.
Browser storage rules live on their own page. Nothing in that cookie policy changes how your account is opened, funded or closed under the terms you accept here.
Identity checks described in these terms follow the same sequence on every account: name, wallet ownership, then a match on the withdrawal route you have registered before any payout leaves.
Payout windows stated here apply to JazzCash, Easypaisa, SadaPay and Raast alike, though each rail settles at its own speed once our checks finish. Where one is slower, the payout schedule page says so.
Campaign clauses sit with each individual offer and always defer to these account terms, so a campaign condition can never override what you accept on this page. That order never changes.
Closing your account follows the same procedure wherever you live: settle open wagers, clear any pending checks, then withdraw your remaining balance through a registered wallet in your own name.
If you disagree with a decision taken under these terms, the complaints page sets out how to raise it, what we need from you and how long a response takes.
The layout is built so you can find a clause without scrolling twice. Wallet chips, clause blocks and the region line sit where you expect them, and every...