Legal terms for Pakistan accounts
Legal terms, privacy duties and account rules sit in one clear place before you join at99. Read how we handle Pakistan access, payment records and dispute contact so...
How our legal terms apply
Our legal page explains the terms that apply when you create or use an at99 account from Pakistan, subject to access only where local law permits. We write these terms in plain English because your account decisions should not depend on unclear wording. The legal position may change by city, province, device location or service provider, so we may restrict features, ask
for extra checks or decline activity when our checks require it. Payment records connected with JazzCash, Easypaisa, SadaPay and Raast are handled as account records, not as public material. If a rule conflicts with a promotion panel or lobby message, the legal wording on this page takes priority until we publish a newer version. You may contact us before joining if any
clause feels unclear.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about legal matters
Legal questions need a route that keeps your message tied to your account. Use the channel that matches the issue, include your registered mobile number, and never send payment PINs. We log each legal contact with time, channel and case reason for follow-up.
Account terms desk
Ask about account clauses, identity checks, suspension reasons or closure language. We may request your registered mobile number, recent login time and the exact clause you want clarified before we reply.
Privacy request channel
Use this path for access, correction or deletion requests linked to personal data. Our team confirms account control first, then explains what can be amended, retained or erased under applicable rules.
Dispute email
Send screenshots, payment reference IDs and dates when you raise a legal dispute. We connect JazzCash, Easypaisa, SadaPay or Raast records with account logs before giving a written response.
How we keep policies accurate
We treat legal copy as operating copy, not decoration. Each clause is checked against the account screens you see, including registration, login, verification, payment history and closure flows. When a workflow changes...
Version control
Every policy edit is saved with a date, reason and owner inside our internal file. Support can see which wording was active when your account action or payment record occurred.
Local wording
We use Pakistani English and familiar payment names rather than imported legal phrasing. That helps you understand how JazzCash, Easypaisa, SadaPay and Raast records relate to account duties.
Screen matching
Clauses are checked against live account screens before publishing. If a button, form field or verification step changes, we compare the legal wording with the new account flow.
Payment audit trail
Payment records are linked to transaction IDs, wallet names and timestamps. That structure helps us answer legal questions about successful cash-in, pending withdrawal checks or reversed attempts clearly.
Security alignment
Our legal terms refer to account protection steps we actually use, including OTP checks, device signals and password resets. We do not describe controls that are absent from the account area.
Clear escalation
When support cannot answer a legal point, the case moves to a senior queue with the original chat or email attached. You should not need to repeat the same facts.
How this page fits others
Our legal page works beside privacy, cookies, promotions, account terms, security and dispute rules. The wording is arranged so one page does not quietly undo another. If two...
| Terms of use | The account terms set your core duties, while this legal page explains how those duties are interpreted. We keep both pages aligned on eligibility, verification, account closure and prohibited conduct. |
|---|---|
| Privacy page | Privacy wording explains data handling in more detail, but this page states the legal basis for account records. Requests about correction, deletion or retention are routed through that companion policy. |
| Cookie page | Cookie wording covers browser storage and session tools. The legal page links that wording to consent, account security and cases where we need logs to investigate access disputes. |
| Promotion rules | Promotion terms can set campaign conditions, yet they cannot override identity checks, withdrawal checks or account restrictions. Where wording differs, the stricter account-protection clause applies until corrected formally. |
| Security page | Security wording explains passwords, OTPs and device checks. The legal page confirms that these controls may affect access, investigation timelines and our ability to release account records safely. |
| Dispute rules | Dispute rules describe evidence we need from you, such as screenshots and wallet references. This page sets the legal channel, response scope and final escalation path clearly for account cases. |
| Support standards | Support standards cover timing and tone, while legal terms define what we can disclose. That distinction matters when identity, payment history or account ownership is under question directly. |
Visible cues inside the legal area
The legal area is built to be scanned before you open an account. We place clauses, contact routes, version dates and dispute steps where you can...
Clause cards
Short clause blocks make legal duties easier to scan on mobile. Each card keeps one subject, such as identity checks or withdrawals, instead of mixing several account rules together.
Version stamp
A visible date shows when the legal page was last changed. If you contact us later, that date helps support connect your question with the wording you saw.
Plain summaries
Plain summaries sit near dense clauses, but the clause itself remains the controlling text. We use summaries to help you read faster, not to replace legal wording there.
Contact rail
Legal contact cards remain close to the policy text they relate to. That way, privacy requests, account disputes and terms questions move into the correct queue faster inside support.
Payment labels
Wallet labels appear only where account records need context. We mention JazzCash, Easypaisa, SadaPay and Raast to identify record types, not to turn legal text into checkout copy.
Access reminders
Where access depends on location rules, the page says so in the relevant clause. We avoid burying legal limits in footer text or after-account screens for clarity upfront.