Legal terms for your p0ki account
p0ki sets out the legal terms that shape your account, access, payments, and support records in Pakistan. Read this page before you open your account so you know...
How our legal wording applies
These legal terms are written for the way p0ki operates in supported regions of Pakistan, not as a generic policy file. They explain account eligibility, acceptable use, wallet records, complaint handling, content ownership, and the effect of changes to our terms. Where local law permits access, your agreement with us starts when you create or continue using your account. Payment references such
as JazzCash, Easypaisa, SadaPay, and Raast appear here only to explain records, sender matching, refunds, and verification duties. If a law, regulator, bank, or payment rail requires a different handling route, that route applies first and our support team will point you to the relevant account step. We keep wording simple so you can decide whether to join with clear expectations about
your balance, login, and contact record.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep policy pages current
Our legal wording is checked by the people who run account access, wallet verification, and support escalation. That matters because a clause can affect how you receive a reply or how a...
Cross-team checks
Policy checks happen before public text changes, with legal, payments, and support teams reading the same draft. That keeps account rules, wallet wording, and complaint routes aligned before you see an update.
Change dates
Each legal page carries a date so you can see when wording last changed. If a clause affects your account, we connect the date with your ticket or wallet record.
Plain wording
We avoid dense legal copy where a direct sentence works. You should understand what you agree to before you open an account, send a payment, or request account help.
Access wording
References to Pakistan access use supported regions and where local law permits. That wording keeps the page tied to local requirements without making broad claims we cannot apply everywhere.
Record matching
Legal clauses about wallets connect to sender names, receipt IDs, and account history. This helps us decide requests with a clear trail rather than screenshots alone.
Security handling
When a legal request involves identity or account access, we verify it before sharing details. We may ask for a safer channel if the first message exposes private data.
Consistency across our policy pages
Our legal page sits beside privacy, cookie, promo, and account safety text. The point is consistency: a rule about identity checks should not say one thing here and...
Visible cues on the legal page
The legal page is designed so you can scan the parts that affect your account before you start. Dates, clause labels, contact paths, and jurisdiction wording are placed...