Account terms
Our account terms describe access rules, while this Privacy Policy explains the personal data behind those rules. We keep both aligned so sign-in checks and privacy wording do not conflict.
LEGAL REFERENCE
Privacy Policy for your 99abai account
99abai keeps your privacy choices, account details, and Pakistan payment records within a clear policy you can read before you open an account. We explain what we collect...
Pakistan privacy scopeAccount data useJazzCash record contextSupport contact paths
How we handle your personal data
This Privacy Policy explains how 99abai handles data linked to your account in supported regions of Pakistan, where local law permits access. We collect only the details needed to create your account, secure sign-in, process account checks, respond to support requests, and keep required operational records. Payment references from JazzCash, Easypaisa, SadaPay, and Raast may be stored with your account record so
we can match confirmations, resolve missing receipts, and answer privacy questions tied to a transaction. We do not sell your personal data. Where we use service partners, we limit access to the task they perform and keep internal permissions narrow. You can ask us to explain, correct, or update your account data through the contact paths below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Ask us about your privacy rights
Privacy questions need a clear route, not a maze. We keep support paths simple so you can ask what data we hold, request a correction, or raise a concern about account access. When you contact us, we may verify that the request comes from you before we discuss private records.
Team online
Account privacy desk
Use the in-account help path when you want us to check personal data linked to your profile. We verify ownership first, then route your request to the team handling privacy records.
Email privacy request
Send a privacy email if you cannot access your account or need a written response. Include your registered phone or email, but never send passwords or full payment app credentials.
Live help handoff
Our live help team can receive a privacy concern and move it to the right queue. They may ask short identity checks before discussing account records or payment references.
DATA ASSURANCE
Policy checks we apply internally
We write this policy from the way our account flow actually works. That means the wording covers sign-in records, payment references, support transcripts, and security checks rather than...
Data minimisation
We ask for account details that support registration, access checks, payment matching, and service replies. Extra fields are avoided unless...
Access controls
Internal account data is limited by role, so support staff see what they need for a case. Broader records require...
Payment reference care
JazzCash, Easypaisa, SadaPay, and Raast references are used to match account activity, not to expose your app balance. We store...
Security monitoring
We may log device, session, and sign-in signals to spot suspicious access. These records help protect your account and support...
Partner limits
When a service partner helps with hosting, messaging, verification, or support tooling, we restrict their role. They are not given...
Policy refresh cycle
We check this policy when account screens, support flows, or payment handling changes. If wording changes in a meaningful way...
POLICY CONSISTENCY
How this page stays aligned
Legal pages should not contradict one another. We keep this Privacy Policy aligned with our account terms, cookie wording, and support scripts so the same privacy position appears across the 99abai site...
Cookie wording
Cookie wording covers browser storage and session tools. This Privacy Policy connects those signals to account security, preference handling, and the choices you may raise with support.
Support scripts
Support replies use the same privacy posture as this page. That helps you receive consistent answers when asking about correction, access, payment references, or account security records.
Payment records
Transaction pages may show receipt status, while this policy explains privacy handling around those records. We separate account balance actions from personal data rights questions.
Security alerts
Security messaging focuses on protecting account access. This page explains which sign-in signals may be logged and why those signals matter for privacy and account protection.
Regional access
Where local law permits access, our privacy wording applies to supported regions. We avoid broad claims and explain the Pakistan-facing data handling you should expect.
Change handling
When we update a linked legal page, we check whether this Privacy Policy also needs clearer wording. That keeps connected privacy statements from drifting apart.
PAGE SIGNALS
Privacy layout details you can scan
This page is designed so you can inspect our privacy position quickly before opening your account. The visible layout points you toward scope, contact options, policy alignment, and...
Clear scope line
The opening section tells you this policy concerns 99abai account...
Local context chips
Short chips name JazzCash, Easypaisa, SadaPay, and Raast only as...
Contact-first layout
Support routes appear early so you do not search through...
Plain language
We use direct Pakistani English rather than dense legal phrasing...
Role-based signals
The layout calls out internal access controls because privacy depends...
Change awareness
Policy refresh wording tells you that account-screen changes can trigger...
Common privacy questions at 99abai
We collect account details, contact data, sign-in records, support messages, and limited payment references needed to run your account. We avoid asking for data that is not connected to access, security, or service handling.
Payment references from JazzCash, Easypaisa, SadaPay, or Raast help us match account activity with a receipt. We use them to resolve support cases and keep records accurate, not to view your app balance.
Yes. Contact us through the account help path or privacy email and tell us what needs correction. We may verify your identity before changing personal data, because account records must stay protected.
We may share limited data with service partners that help with hosting, support tools, security checks, or messaging. Their access is restricted to the assigned task and is not for unrelated use.
We log session and device signals to help detect unusual access. Access to those records is limited internally, and support will not discuss private account activity until ownership checks are complete.
We keep account and transaction records for as long as needed for service, security, dispute handling, and legal duties. When data is no longer required, we remove it or reduce its link to you.
Use in-account help for the fastest ownership check, or email us if account access is not available. Give enough detail to locate your record, but never include passwords or full wallet credentials.