Privacy Policy
This page explains the personal data we collect, why we use it, who may handle it, and how you can ask us to access, correct, or remove certain records.
LEGAL REFERENCE
Privacy Policy for Your Account
Our Privacy Policy explains what data we collect when you open a hot 77 account, verify access, use Pakistan payment rails, or ask us for help. We keep...
Account dataDevice checksJazzCash contextSupport requests
How We Handle Your Data
We collect only the details needed to run your account, protect access, process transaction records, and answer privacy requests. That may include your name, mobile number, login activity, device signals, payment references, support messages, and security checks connected to hot 77. Pakistan access is supported only where local law permits, so we may use location or network clues to confirm eligibility. We
do not sell your personal data. We share limited records with service partners only when needed for account security, payment handling, fraud checks, or legal requests that apply to our operations.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY HELP
Ways to Reach Our Privacy Team
Privacy questions should reach people who can act on them, not a generic inbox. Use these routes when you want access to your data, a correction, deletion where allowed, or an explanation of a specific account check.
Team online
Account privacy inbox
Open the help area after login and choose the privacy request option. We link the request to your account record, which helps us confirm identity before releasing or changing personal data.
Live chat handoff
Chat can collect the basics, then pass the case to our privacy queue. Do not post full card, wallet, or identity images in chat unless our team asks through the secure upload step.
PKT support window
Our support desk handles privacy tickets during Pakistan-friendly hours. If your request needs a payment partner check, we may ask for the transaction reference rather than extra personal documents.
POLICY CHECKS
How We Keep This Policy Clear
We write this Privacy Policy from the way hot 77 actually handles accounts. Each point is tied to a real step: login, verification, wallet reference matching, support handling...
Plain data categories
We name the data types we use, such as mobile number, device signal, account activity, and transaction reference. This keeps...
Local wallet context
JazzCash, Easypaisa, SadaPay, and Raast references can create transaction records. Our policy explains that those records help match account activity...
Access controls
Only trained teams can open privacy-sensitive account records. We use role permissions, login logs, and case tagging so internal access...
Security monitoring
We use device and session signals to spot unusual access attempts. The policy explains this because privacy and account protection...
Retention discipline
We keep account records only for operational, legal, security, and dispute needs. When a record is no longer required, we...
Readable updates
When the Privacy Policy changes, we adjust the page date and wording so you can see what matters. Major changes...
POLICY ALIGNMENT
Consistency Across Our Legal Pages
This Privacy Policy sits beside our Terms, cookie wording, and account rules. We keep the language aligned so one page does not promise a data practice that another page treats differently.
Cookie wording
Cookie wording explains browser storage, analytics tags, and session tools. It links back to this policy because cookies can connect device activity with your account session.
Terms page
Our Terms explain account rules, while this policy explains the data side of those rules. Verification, access checks, and dispute handling need both pages to stay aligned.
Promo terms
Promotional rules may use account status, region, or eligibility checks. This policy explains the data handling behind those checks without turning campaign wording into privacy wording.
Security notices
Security messages focus on account protection, password resets, and unusual login alerts. This policy explains the data signals that allow those notices to be sent safely.
Wallet records
Transaction terms explain wallet movement, while this policy explains the personal data linked to wallet references. We keep those purposes separate so each page stays clear.
Support scripts
Support wording tells our team what to ask when you contact us. Privacy wording sets the boundary, so we request only details needed to handle the case.
PAGE SIGNALS
Privacy Page Layout Signals
We design the policy page so you can scan the privacy points before opening or managing an account. The visible structure helps you find data categories, contact routes...
Policy date area
A clear date marker shows when the Privacy Policy wording...
Short badges
The badges at the start summarise the data themes without...
Contact blocks
Support blocks are placed near the policy explanation so you...
Local context chips
Context chips name Pakistani rails that may create transaction references...
FAQ placement
Questions sit after the main sections because privacy requests often...
Account wording
We say you and your account throughout the page because...
Privacy Questions for Pakistan Accounts
We may collect your name, mobile number, login details, device signals, support messages, and transaction references. The exact data depends on how you access your account and which verification steps apply.
Device and login data help us protect your account, detect unusual access, keep sessions stable, and apply regional access checks where local law permits. We use these signals for security, not resale.
Wallet activity can create reference numbers, timestamps, and status records linked to your account. We use those details to match transactions, answer disputes, and keep financial records consistent.
Yes. Send a privacy request from your logged-in help area so we can confirm identity before sharing account data. We may redact security or third-party details where disclosure is not allowed.
Retention depends on the record type. Support tickets, verification records, transaction references, and security logs may have different timeframes because legal, dispute, and account protection needs are not identical.
We share limited data only when needed for account operation, payment handling, security checks, technical hosting, support tools, or lawful requests. Partners must handle the data for the agreed purpose.