Terms and Conditions
The account rules you accept at registration match this page on age, eligibility and closures, and both send you to the same support routes when something is disputed.
This Privacy Policy sets out what we collect when you open an account with pakbet7, why we collect it and how long we keep it. You can see...
We keep this policy short on purpose, but some points depend on where you live. If you register from Pakistan, the way we hold your records follows the rules that apply in supported regions, and any request you send is handled on that basis. Payment details you enter at the cashier, through JazzCash, Easypaisa, SadaPay, NayaPay or Raast, are processed by those
providers under their own terms, so we describe only what reaches us. Where local law permits an account, you can ask for a copy of what we hold, ask us to fix something wrong, or close the account and have your profile removed. Some records, such as transaction logs behind a withdrawal, must be kept for a set period because payment providers
require it, and we tell you which ones when you ask.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If something here is unclear, you do not have to guess. Write to our privacy desk and a person reads it and replies, not an automated message. We aim to answer within two working days, and for a data request we confirm your identity first so nothing goes to the wrong account. Our team works Pakistan hours, so a question raised in the morning usually has an answer the same day.
Send a message to our privacy desk from your registered address and it reaches the person handling data requests that week. You get a reference number to quote later.
Open the help panel inside your account for anything on this page, from cookies to closure. Chat runs Pakistan daytime hours and the transcript lands in your inbox.
Use the data request form for a copy of what we hold, a correction, or your profile removed. We confirm your identity, then write back on what we did.
We write this page ourselves, in the same voice you hear elsewhere on pakbet7, and we keep a dated version of every change so you can see what moved. A named member...
We write clauses so they survive one reading, with the practical consequence sitting next to the rule. Definitions are linked rather than buried, and every obligation is spelled out in plain English.
Every revision carries a date stamp on the first line and an archived copy behind it, so you can see what changed between two versions of a clause you rely on.
One operations manager owns this page by name and signs off each revision, so a question about wording has a person behind it rather than a shared inbox.
Account records sit in encrypted databases with access limited to staff who need them for a specific task. We log who opens a profile and keep data inside our own systems.
We hand over only what a payment provider or a legal order needs. No profile is sold, rented or traded to advertisers, and contact lists stay out of outside marketing hands.
When a clause that affects you is rewritten, we email you and post a banner in your account before the new wording starts. Fixed typos only reach the change log.
Everything on this page sits alongside the other documents you accept when you join, so wording, dates and contact routes line up. When a term changes here, we update the matching line...
The account rules you accept at registration match this page on age, eligibility and closures, and both send you to the same support routes when something is disputed.
Our cookie page breaks down each category we set, why it exists and how to switch it off, using the same headings as this policy so the two read together.
That page covers clearance timing for JazzCash, Easypaisa, SadaPay, NayaPay and Raast, and its retention lines match the record-keeping periods described here, so a withdrawal trail stays consistent.
The verification page explains which documents we ask for and how long copies are kept, then links back here for the deletion route once a check finishes.
That page sets out the steps and timeframes when you disagree with an outcome, and repeats the escalation contacts listed here so nothing is lost when you escalate.
The closure page walks through what happens to balances, saved payment tokens and profile data if you decide to leave, mirroring the removal steps described here.
The eligibility page states who can hold an account in supported regions and uses the same jurisdiction wording, so the two documents cannot be read against each other.
This page is built so you can find an answer fast instead of scrolling through walls of text. The chips above the headline show what the...
The chip row under the headline names what this policy covers, so you can tell at a glance whether it touches the part of your account you came to check.
A jump bar sits under the chips and takes you straight to a clause without scrolling. On mobile it collapses into a list you tap, then closes when you land.
Every sub-heading is phrased as a question, so you can skim and stop where your situation matches. The answer sits directly beneath it, with the linked clause if you want detail.
A dated change log lists every edit to this page, newest first, with a single line on what moved, and older versions open side by side on desktop.
You can download the whole policy as a PDF or save it to your phone for offline reading. The file carries the same date stamp as the live page.
A contact strip runs at the foot of every section, putting the privacy desk email, the in-app chat entry and the data request form one tap away on mobile.