Privacy Policy
This page explains what personal data we collect, why we use it, who may process it for us and how you can ask privacy questions about your 2h88 account.
LEGAL REFERENCE
Privacy Policy for Your 2h88 Account
2h88 collects only the account, device and transaction data needed to open your account, protect access and keep records clear where local law permits. This Privacy Policy explains...
Account dataDevice checksTransaction recordsPakistan access
How We Treat Your Data
We use your personal data to create and secure your 2h88 account, confirm identity details, process transaction records and respond when you ask us for help. We may record your name, mobile number, login activity, device signals, payment reference data and support messages. These records help us spot unauthorised access, match account activity with requests, keep audit trails and meet lawful obligations
in supported regions. We do not sell your personal data. We share limited records only with service providers that help with hosting, verification, security, payment processing or customer support, and only for the work they perform for us. If you access 2h88 from Pakistan, local rails may add their own privacy terms when you use their apps or bank-linked services.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CARE
How We Keep Policy Careful
Our Privacy Policy is written around actions that happen inside 2h88, not vague promises. We connect each data use to account opening, access protection, transaction handling, support replies or legal record keeping...
Clear data reasons
Each data category has a purpose, such as account setup, identity confirmation, transaction matching or security monitoring. We avoid collecting extra details when a shorter record can solve the same need.
Local transaction context
Pakistan payment references can pass through JazzCash, Easypaisa, SadaPay or Raast. We store the reference data needed for matching and support, not wallet passwords or private app credentials.
Security logging
We keep login times, device signals and access alerts to help detect unusual account activity. These logs are used for protection, investigation and recovery when you raise an access concern.
Limited sharing
Service providers receive only the records needed for their task, such as hosting, verification, transaction routing or support tooling. They are not given permission to sell your personal data.
Retention checks
We keep records for account operation, dispute handling, security and lawful record needs. When data is no longer required, we aim to delete, anonymise or separate it from active account tools.
Plain updates
When this Privacy Policy changes, we update the page date and keep the wording direct. Material changes may also be flagged inside account areas or support messages.
PAGE CONSISTENCY
Same Privacy Pattern Across Pages
Your privacy protections should not change because you entered through a legal page, an account page or a support route. We keep the same data principles across related policy pages so the...
Terms page
Our Terms describe account rules, but the privacy wording still points back here for personal data handling. That separation keeps account rules and data rights easier to follow.
Cookie page
Cookie details focus on browser storage, device recognition and session tools. When those tools connect to personal data, this Privacy Policy explains the broader account-level handling.
Security page
Security content explains account protection steps, while this page explains the data behind those steps. Logs, alerts and verification checks stay tied to clear privacy reasons.
Support page
Support forms may ask for contact details, account references and message history. The privacy rule is simple: we use those details to answer the issue you raised.
Transaction help
Transaction pages may mention JazzCash, Easypaisa, SadaPay and Raast references. This Privacy Policy explains how those references are stored, matched and checked for account support.
Account area
Your account area may show contact details, verification status and activity records. The same privacy principles apply whether the data is visible on-screen or held in back-end records.
Privacy Cues Across This Page
We design this policy page so you can scan data topics without losing the legal meaning. Headings, chips and cards show what is collected, why it...
Plain headings
Each section heading states the privacy subject before the detail appears. This helps you move from account data to sharing, retention and contact choices without decoding legal shorthand.
Local context chips
Short chips mention Pakistan payment references only where they affect privacy records. They do not ask for wallet secrets, and they do not replace the Privacy Policy wording.
Actionable contacts
Contact cards tell you which privacy route fits your concern, such as correction, account access or transaction record matching. This reduces back-and-forth and keeps sensitive details limited.
Data purpose links
We connect data types with purposes, including account setup, security checks, support replies and lawful records. You can see why a record exists before reading deeper policy detail.
Change clarity
Policy updates are written so you can spot what changed in plain language. We avoid hiding material privacy shifts behind generic wording or unrelated account announcements.
Mobile readability
The policy is structured for mobile screens common across Pakistan. Short sections, labelled cards and direct answers help you read privacy terms before opening or managing an account.
Privacy Questions Before You Join
We may collect your name, mobile number, account credentials, device signals, login activity, transaction references and support messages. The exact records depend on how you open and use your account.
Device and login records help us protect your account, detect unusual access and support recovery requests. They also help us confirm whether a privacy or security concern relates to your account.
No. For JazzCash, Easypaisa, SadaPay or Raast activity, we use reference details needed to match account records. We do not ask for wallet PINs, app passwords or private banking credentials.
Yes. Contact us through the privacy route and tell us what needs correction. We may verify your identity first, then update eligible records and confirm the change through your registered contact path.
Access is limited to trained staff and service providers who need records for account operation, security, verification, transaction processing or support. We restrict access based on role and task.
We keep data for account operation, legal record needs, security checks and dispute handling. When a record is no longer needed, we aim to delete, anonymise or move it away from active systems.
Send your question through the account privacy contact path with your registered mobile number and a short description. Do not share wallet PINs, full card data or unrelated private details.