Privacy
Privacy tells you what data we collect and why. This page tells you what you agree to when you use that data inside an account, from login details to the way we handle requests.
LEGAL REFERENCE
Terms That Shape Your Account
These Terms & Conditions set the rulebook for your account on isb 7. They explain how you join from supported Pakistan regions, how we verify details, when access...
PakistanAccount RulesLocal LawPayment Checks
How These Terms Apply Here
These terms apply when you create an account, use the site, or send us any payment instruction from a supported region. We keep the wording practical: you are responsible for accurate profile details, keeping your login secure, and following the clause shown next to each action you take. If local law permits access, the terms on this page control your use of
isb 7 in Pakistan; if a rule changes by region, the regional wording will apply. When a JazzCash, Easypaisa, SadaPay or Raast transfer needs checking, we may hold it until the name, number, and account details line up. Continued use after an update means you accept the new text, so it is worth checking this page before you move funds or change
account settings.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
ASK US DIRECTLY
Where To Ask About Clauses
If you want a clause explained, or you think a term was applied the wrong way, speak to us before you continue. We keep the support path tied to your account so the thread, the date, and the clause number stay together. That makes it easier to resolve payment checks, access questions, and region-specific wording without guesswork.
Team online
In-account chat
Use the in-account chat for clause-by-clause questions. We can point you to the line that applies, check whether a request is paused, and explain what we need before the account can move ahead.
Email desk
Send your account email plus the clause number you want explained. We reply in plain English, keep the thread attached to your profile, and use it as the record if the same issue comes back later.
Document desk
If a name, number, or payment route needs checking, share the requested file through the secure upload path. We use it only for that clause, then close the file once the check is complete.
CLEAR POLICY WORK
Why Our Terms Stay Clear
We write the terms in plain English so you can read them on mobile without losing the thread. Every section is tied to a real account action: joining, verification, payment checks, access...
Plain English first
We keep the wording direct so the rule you need is easy to find on mobile or desktop. Each clause is short enough to read fast, but still specific about the action it covers.
Region wording
Where access depends on local law, we say so in the clause itself. That keeps the page aligned with supported Pakistan regions and avoids guesswork about whether a rule applies to your account.
Version trail
When we change a clause, the updated text replaces the old one and stays in the same page structure. You can check the current wording without hunting through old copies or mixed messages.
Account matching
If a payment route, name, or account detail does not line up, we can pause the request until the record is matched. That protects both sides and keeps the clause tied to the right profile.
Support record
Every answer from support stays attached to the same thread, so you can return to it later if the same term comes up again. That makes the conversation easier to verify and resolve.
Action-based clauses
We link each rule to a real action such as joining, logging in, sending a transfer, or changing account settings. That makes the page practical instead of abstract.
PAGE FIT
How This Page Fits Others
This page sits beside our other policy pages but does a different job. Privacy tells you what data is handled; these terms tell you how the account is used. Payment wording explains...
Payments
Payment wording covers routes, timing, and checks. These terms set the rule for when a transfer can be held, declined, or asked for again if the details do not match the account.
Security
Security wording explains how we protect access. These terms explain your side of the same process, including keeping your login private and using the account only in the way the page allows.
Verification
Verification pages ask for document matches. These terms explain why that match matters, what happens if the details differ, and how access can be limited until the record is clean.
Content rules
Content rules tell you what is not allowed on the site. This page turns those rules into binding account terms, so the same standard applies every time you use the service.
Support
Support pages show where to ask for help. These terms define what support can change, what it cannot change, and when the written clause stays in force even after a chat reply.
Local law
Local law wording sets the region boundary. This page uses the same boundary to say where the account can be used and when a clause changes because supported regions are different.
LAYOUT FOCUS
Page Elements You Will See
The policy page is built to be quick to scan on a small screen. Short section labels, clear clause blocks, and a visible update stamp help you find...
Numbered clauses
We break the text into numbered blocks so you can...
Update stamp
A visible date stamp shows when the current wording went...
Region callout
When a clause depends on supported Pakistan regions or local...
Support links
The contact links stay near the policy text so a...
Short badges
Small badges at the top of the page give you...
Clear spacing
We keep enough space between sections for mobile reading, which...
Questions About These Terms
They apply when you create an account, use the site, or send a request from a supported Pakistan region where local law permits access. If you continue after an update, the current wording applies to that account.
Yes. We may update the page when law, account control, or site rules change. The latest version replaces the earlier text, and your continued use after it is posted means the new wording governs the account.
If a name, number, or payment route does not line up, we can pause the request and ask for a fresh check. That keeps the record clean and helps us apply the right clause to the right account.
Yes. Any JazzCash, Easypaisa, SadaPay, or Raast transfer can be checked against the account record before it moves ahead. If something looks off, we may hold it until the details are matched.
If the account stays unused for a long period, we may apply the inactive-account clause shown here. That can affect access or account status, and we will use the contact details on file where possible.
We do. The text, graphics, and layout belong to isb 7, while your use of the service stays limited to the account and the clause set on this page.