Privacy Policy for Your at99 Account
Open your at99 account knowing this Privacy Policy explains the account data we collect, why payment records matter, and how you can ask us to adjust or erase...
How We Treat Your Account Data
This Privacy Policy sets out how at99 handles the details you share when you create an account, verify access, request a payout, contact support or browse pages in supported regions. We collect account identifiers, device signals, payment references, session logs and messages you send us, then use them for account security, fraud checks, service handling and legal record duties where local law
permits. JazzCash, Easypaisa, SadaPay, NayaPay and Raast references may appear in your account history, but we keep cardless wallet numbers, transaction IDs and payout evidence separated from public page activity. If a verification step is needed, our team checks only the records needed for that request and keeps an audit trail for later dispute handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Help Without Guesswork
If you need to ask about your data, send a correction request, or question a payment record, contact us from the same account you want checked. That helps us match your request with the right profile while avoiding extra exposure. For privacy matters, include the channel used, an approximate date, and the record you want us to inspect.
Live chat handover
Start with in-account chat and ask for privacy support. We confirm your account access first, then move the request to a safer channel if documents or payment references are involved.
Email privacy desk
Email us from your account address when the request needs detail. Keep screenshots cropped to the record in question so unrelated wallet, device or personal data is not exposed.
Payment record query
For JazzCash, Easypaisa, SadaPay, NayaPay or Raast issues, share the transaction reference and date. We check only the linked account trail and reply with the next privacy step.
How We Keep This Policy Accurate
We write this Privacy Policy from the way at99 actually runs account access, wallet records and support handling for Pakistan. Our privacy wording is checked when account flows change, when a local...
Operational wording
Policy text is based on account tasks we handle every day, including login checks, wallet reference matching, payout verification and support replies, not copied from unrelated legal templates.
Access control
Support agents see only the data needed for their queue. Privacy requests that involve payment evidence or identity checks are escalated to staff with narrower, logged access.
Payment separation
JazzCash, Easypaisa, SadaPay, NayaPay and Raast references are stored as account records. Public browsing activity is kept separate so payment evidence is not mixed with page tracking.
Device safety
We use device and session signals to protect account access. Those signals help us spot unusual entry attempts without turning your private account messages into public page data.
Change checks
When we adjust account forms, support routing or wallet fields, the Privacy Policy is checked for matching wording so your rights and our data use stay understandable.
Request trail
Privacy emails and account chat requests are logged with dates and handling steps. That record helps us answer follow-up questions without asking you to repeat sensitive details.
Aligned Privacy Pages Across at99
The Privacy Policy should read consistently wherever you reach it from inside at99. A footer link, account page link, payment help link or support reply should take you...
| Account page | The account area points back to this Privacy Policy when profile fields are collected, edited or checked. That keeps your name, contact and security data under the same explanation. |
|---|---|
| Wallet records | Payment screens should match this policy when JazzCash, Easypaisa, SadaPay, NayaPay or Raast references are saved. We connect wallet records to your account, not public browsing data. |
| Support replies | Support responses about data access, correction or deletion should follow this same policy language. If a request needs proof, we explain why before asking for extra records. |
| Login security | Security prompts, password changes and device checks are linked to the same privacy basis. We use those records to protect account access and investigate unusual activity. |
| Promo preferences | If you adjust message preferences, the privacy wording should explain what changes and what account notices still remain. Service alerts may continue when they affect your account. |
| Document checks | Where a payout or account query needs verification, document handling should follow this policy. We ask for relevant proof only and keep the request tied to its case. |
| Policy date | Each privacy page should carry the same version date after changes. That helps you see whether a linked page reflects the current account and payment handling rules. |
Privacy Cues You Can See
We design the Privacy Policy page so you can scan the data points that matter before opening an account. The visible layout separates account data, payment...
Clear section labels
Each block uses plain labels for account data, payment records, support handling and rights requests. You can move straight to the privacy issue you care about.
Local payment chips
JazzCash, Easypaisa, SadaPay, NayaPay and Raast chips show where wallet references may enter our records. They are context markers, not requests for extra data.
Account-first wording
The copy speaks directly to you because privacy requests depend on your account. We avoid vague third-party wording and explain how at99 handles its own records.
Change date placement
When policy wording changes, the date is placed where you can see it before reading deeper. That helps you understand whether recent account steps are included.
Request prompts
Contact cues ask for the smallest useful detail, such as date, channel and record type. That keeps your privacy request focused and avoids extra exposure.
Rights language
Rights sections explain access, correction and deletion requests in plain Pakistani English. We also mention where local law permits because some records must be kept longer.