Terms of use
The terms explain account eligibility, access rules, prohibited conduct and dispute steps. They are the starting point for understanding what you agree to when you use i2c.
LEGAL REFERENCE
Legal terms for your i2c account
Our legal page gives you the account terms, privacy position and contact routes that apply when you use i2c from supported regions in Pakistan. Read it before you...
Account termsPrivacy rightsPakistan contextSupport routes
How our legal terms apply
i2c makes this legal page available so you can understand the rules that sit behind your account before you join. Access is intended only where local law permits, and the terms may change when laws, banking rules or product controls require an update. We explain how account checks work, how payment records are kept, how withdrawals may be verified, and how we
handle privacy requests tied to your profile. If a clause conflicts with a requirement in your supported region, the local requirement takes priority. Keep your account details accurate, use your own payment wallet or bank rail, and contact us before opening a dispute so we can check the record attached to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECKED COPY
How we keep policy copy accurate
Our legal copy is written around how i2c actually operates: account creation, login security, wallet checks, withdrawal verification and support handling. We check it when a rule, payment flow or contact route...
Operational input
The policy text is shaped with input from account, payments and support teams. That keeps legal wording connected to the screens, forms and checks you use inside i2c.
Change tracking
When a material clause changes, we record the reason and update the visible copy. Older wording is kept internally so account queries can be matched to the correct period.
Local wording
Pakistan payment names and support routes are written plainly, not as imported boilerplate. We use familiar terms for JazzCash, Easypaisa, SadaPay and Raast where they matter legally.
Account security
Legal clauses cover password care, device access and identity checks because those controls protect your account record. We link those rules to support steps when access is disputed.
Privacy handling
Our privacy wording explains why certain account details are stored, such as contact data, transaction references and support messages. It also explains how correction requests are handled.
Plain language checks
We remove vague legal phrasing where a clearer sentence will do. You should be able to understand key rights, restrictions and contact routes without decoding legal jargon.
PAGE SYNC
Policy pages that stay aligned
This legal page works with our privacy, cookie, account and payments policy pages. Each page has its own purpose, but the rules should read consistently when you move between them.
Privacy policy
The privacy page explains what account data we collect and why. It supports the legal terms by setting out data handling, correction requests and contact consent in plain wording.
Cookie policy
The cookie page explains browser storage linked to login sessions, analytics and preference settings. It keeps tracking wording separate from account clauses while staying consistent with privacy rights.
Payments policy
The payments page covers wallet references, verification checks and withdrawal handling. The legal page points to those rules when a payment record affects account status or dispute handling.
Security policy
Security wording covers password care, device access and suspicious activity checks. It supports legal clauses that require you to keep account access private and report misuse quickly.
Promotions terms
Promo rules sit separately so campaign details do not clutter core legal terms. If you join an offer, the campaign terms apply alongside the main account rules.
Contact policy
Contact wording explains which route to use for account, privacy, payment or legal requests. It helps us respond with the correct records instead of passing you between teams.
What you see on legal pages
The legal layout is built to help you act, not just read. We place version cues, contact links, clause labels and local context close to the...
Version marker
Each policy page shows when the wording was last changed, so you can tell whether you are reading current terms. Material changes are handled with clearer placement.
Clause labels
We break legal text into named clauses for faster reference during support chats. You can point to a section name instead of copying a long paragraph.
Local context chips
Where a clause mentions payment records, chips highlight JazzCash, Easypaisa, SadaPay or Raast. The chips do not replace the terms; they show relevant Pakistan context.
Contact prompts
Legal pages include contact prompts beside clauses that often need clarification, such as privacy requests or account disputes. That keeps the next step close to the rule.
Short summaries
Some clauses include a short summary before the full wording. The summary helps you scan, while the complete clause remains the part that controls the account relationship.
Cross-page links
When another policy carries the detail, we link to it from the relevant clause. That avoids repeating legal text and helps the pages stay consistent.
Legal questions before you join
Your account is governed by the i2c terms and any local rule that applies in your supported region. If access is not permitted where you are, you should not open or use an account.
Verification helps us match your profile, payment records and support requests to the right person. It also helps us handle withdrawals, disputes and privacy requests with a clear account trail.
Yes. We may update terms when laws, payment requirements, product controls or support processes change. The visible policy date helps you see when the wording was last changed.
When a payment query arises, we use wallet references, dates and account details to match the transaction. Those records support verification, correction requests and dispute handling tied to your i2c account.
You should contact us through the privacy route if you want to ask about stored profile data, correction of account details or contact consent. Identity checks may apply before action is taken.
Tell us as soon as you notice unusual access. We check login records, device signals and support history, then apply the account terms that cover security, misuse and recovery.