Terms Link
The terms page may describe account conduct, but this page explains the data used to support those rules. If a rule needs a record, the privacy purpose should be clear here.
LEGAL REFERENCE
788min Privacy Policy for Pakistan
788min keeps the Privacy Policy close to your account journey: what we collect, why we collect it, and how you can ask us about it. Open your account...
Account data useJazzCash contextEasypaisa contextRights requests
How We Handle Your Data
This Privacy Policy explains the data we collect when you create or use a 788min account, including contact details, login signals, device records, payment references and messages you send to us. We use that data to run account access, check activity, process payment-related requests, protect sessions and respond when you ask about your records. For Pakistan, references to JazzCash, Easypaisa, SadaPay and
Raast describe the payment context linked to your account, not a separate banking promise from us. Access is offered in supported regions and where local law permits. We limit internal access to staff who need it for account, risk, payment or privacy support, and we keep retention checks tied to legal and operational needs.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
Policy Checks We Keep Current
We write this policy around the systems we actually use, not a generic template. Each check below explains how 788min keeps the page aligned with account flow, device...
Data Map
We map account details, login signals, payment references and support messages to the purpose that needs them. That helps us...
Payment Context
JazzCash, Easypaisa, SadaPay and Raast references are treated as account-support data. We record transaction IDs, timing and status where needed...
Access Controls
Internal access is role based, so support staff see request details while payment or risk staff see the records needed...
Retention Rhythm
We keep records only for account operation, legal needs, dispute handling and security checks. When a retention reason ends, we...
Device Signals
Device and session signals help protect logins and detect unusual account access. They are not used to expose private browsing...
Change Log
When the Privacy Policy changes, we update the page date and adjust wording around the changed practice. Major changes may...
PAGE CONSISTENCY
Same Privacy Thread Across Pages
Our legal pages should not contradict one another. The Privacy Policy explains data use, while related pages may explain account rules, cookies, payment records or contact steps. The links below show how...
Cookie Link
Cookie wording should match the device and session data described in this Privacy Policy. If cookies help with login security, analytics or language choice, both pages should say so.
Payment Records
Payment pages may mention JazzCash, Easypaisa, SadaPay or Raast processing steps. This policy explains which account-linked records we keep from those steps and why we may retain them.
Security Page
Security wording focuses on protecting your account. This Privacy Policy explains the personal data side of that work, including login signals, identity checks and restricted internal access.
Support Page
Support routes tell you where to send a message. This Privacy Policy explains how that message may be stored, matched to your account and used to answer your request.
Account Page
The account area may let you edit profile fields or view status prompts. This policy explains why those fields exist and when we may need to keep older records.
Regional Access
Where local law permits, regional access wording should match our data handling. Pakistan references in this policy are linked to supported regions, payment context and language support.
SCAN POINTS
Privacy Layout You Can Scan
We shaped this page so you can find privacy answers without reading every legal line first. The layout separates collection, use, sharing, retention and contact routes. Each visible...
Short Lead
The opening section states the purpose of the Privacy Policy...
Local Chips
Short chips name Pakistan and the payment references that may...
Plain Sections
Each section uses direct headings instead of dense legal blocks...
Action Paths
Contact cards explain how to send privacy requests without mixing...
Rights Focus
FAQ answers cover access, correction, deletion and security questions in...
Update Signals
The policy structure leaves room for change dates and visible...
Privacy Questions Before You Join
We may collect your contact details, login credentials, device signals, support messages and payment references. The exact record depends on how you use the account and which support or payment request you make.
If your account activity involves JazzCash or Easypaisa, we may store related references such as status, time and transaction ID. We use them to trace requests, reconcile records and answer privacy or payment questions.
Yes, you can contact us through the privacy routes listed on this page. We may ask you to confirm account control before sharing records, so your data is not released to the wrong person.
You can update some profile fields inside your account. If a field is locked, archived or linked to verification, send a request and we will explain what can be changed.
We may share or receive limited data needed to process payment-related requests, confirm status or handle disputes. That can include references tied to SadaPay, Raast, JazzCash or Easypaisa records.
Retention depends on the record type and the reason it is needed. Account, support, payment and security records may be kept while legal, dispute or operational reasons still apply.