Privacy Policy for Your ar77 Account
Your ar77 privacy policy explains what account data we collect, why we collect it, and how it supports access in Pakistan where local law permits. Before you open...
How We Handle Your Privacy Data
We collect only the data needed to run your ar77 account, confirm access, process local payment activity, answer privacy requests, and protect your login in supported regions. That may include your name, mobile number, account credentials, payment reference, device details, IP address, session history, and messages sent to our support team. When you use JazzCash, Easypaisa, SadaPay, or Raast, we keep transaction
references so we can match requests, handle reversals, and trace account changes. We do not sell your personal data. We share limited data with service providers only when they help us host the site, verify account activity, secure sessions, or handle payments under privacy controls.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Current
This policy is maintained by the ar77 team that handles account flows, payment checks, and privacy requests. We update wording when our data use changes, when a local rail changes its required...
Operational ownership
The privacy policy is tied to the same workflows we use for login checks, payment matching, and support replies, so wording reflects actual ar77 account handling rather than abstract legal language.
Local payment awareness
We write privacy terms with Pakistan rails in mind, including JazzCash, Easypaisa, SadaPay, and Raast references. Each rail can create different transaction data, so our policy names the records we may need.
Access security checks
When you log in, we may compare device, browser, IP, and session signals. These checks help us detect unusual access while limiting use of those signals to account protection and fraud prevention.
Support handling standards
Support agents see only the account data needed for your request. Sensitive changes require matching details, and we avoid sharing full payment references inside chat unless verification calls for it.
Change tracking
When privacy wording changes, we keep internal records of what changed and why. That helps our team answer your questions about newer clauses, older wording, or account data collected earlier.
Plain language checks
We aim to keep this policy readable in Pakistani English. If a clause affects your account, payment history, device checks, or support messages, we explain it without hiding the practical effect.
How This Policy Fits Nearby Pages
Our privacy policy works beside other ar77 legal pages, but it has a separate job. This page explains personal data use. Other pages may explain account rules, cookies...
Visible Privacy Cues Across ar77
We design the privacy page so you can find the parts that affect your account before you join. The layout separates collection, use, sharing, retention, and...
Hero badges
The badges at the start show the main privacy areas quickly: account data, local rail references, access checks, and contact routes. They help you scan the page before reading deeper clauses.
Data purpose blocks
Each block connects a data type to a purpose, such as login safety, payment matching, or support handling. We avoid vague labels so you can see why a record exists.
Sharing markers
Where third parties are involved, we mark the reason clearly, such as hosting, security checks, or payment processing. The page separates service sharing from selling, which we do not do.
Retention cues
Retention wording explains why some records remain after a request, especially payment references, dispute records, and security logs. These cues help set expectations before you ask us to remove data.
Choice prompts
Choice prompts point to actions you can take, including asking for a copy, requesting correction, or limiting certain messages. We place them near the data category they affect.
Contact tiles
Contact tiles separate fast questions from formal privacy requests. That prevents sensitive account changes from being handled too casually and helps us move your request to the right ar77 workflow.