Account terms
Our account terms explain permitted use, while this Privacy Policy explains personal data handling. Shared wording for identity checks helps you see why certain details are requested before account changes.
LEGAL REFERENCE
Your mam 32 Privacy Policy
mam 32 keeps the privacy promise close to the account flow: what we collect, why we use it, and how your choices sit beside lobby access in supported...
Account data scopePakistan rails notedSupport route stated
How We Handle Account Data
This Privacy Policy applies when you use mam32.com, create an account, contact us, or enter the lobby where local law permits. We collect account details you give us, device and session records needed for security, transaction references from Pakistani rails, and messages you send to our support desk. We use that data to open and protect your account, process requests, check withdrawal
details, show suitable language and region settings, prevent misuse, and meet legal duties that apply to supported regions. We do not sell your personal data. When JazzCash, Easypaisa, SadaPay, or Raast is involved, each provider may also handle its own records under its own privacy terms. You can ask us to correct, access, or erase data where the law allows.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How This Policy Stays Accurate
We write this policy from inside the mam32.com account flow, so it tracks the data points you actually touch. The privacy text is checked against registration fields, payment...
Rail mapping
We map privacy wording to JazzCash, Easypaisa, SadaPay, and Raast reference handling, so you can see which transaction data reaches...
Access controls
Access to privacy request queues is limited by role. Staff see only the account fields needed for support, verification, or...
Change logging
When policy wording changes, we log the date, reason, and internal owner. That record helps us answer your questions about...
Security testing
Session handling, password reset flows, and device prompts are tested against the data statements in this policy. If a feature...
Plain English
We use clear Pakistani English for privacy terms, not dense legal phrasing. You should know what is collected, why it...
Regional law
Access wording uses supported regions and where local law permits because privacy duties can change by place. We avoid broad...
SIBLING CONSISTENCY
Privacy Across Our Policy Set
Your privacy choices connect with other legal pages, but this page stays focused on personal data. We keep names, contact routes, retention language, and account-security wording aligned across our policy set so...
Cookie settings
Our cookie page explains browser storage, while this policy explains personal data linked to your account. We align both pages so session analytics and preference tools use the same wording.
Security alerts
Security alerts describe unusual access, password resets, and device checks. This policy connects those alerts to the personal data used for verification, session control, and account recovery requests.
Rail records
Transaction terms describe how requests move through Pakistani rails. This policy explains the account reference, wallet name, timestamps, and status updates we may receive from those rails securely.
Withdrawal checks
Withdrawal wording in account terms covers processing steps. The privacy wording here explains identity checks, bank or wallet references, and messages used to confirm that a request belongs to you.
Support requests
Support terms set channel rules, while this page explains how chat transcripts, email threads, and verification replies are stored, accessed, and used to answer your privacy requests safely.
Change log
When one policy page changes, we check related legal pages for matching names, contacts, and dates. That avoids mixed messages about how to reach us on privacy matters.
PAGE SIGNALS
Policy Page Elements You See
The privacy page is built to make the legal text easier to scan before you join. Instead of hiding key choices in long blocks, we place visible markers...
Scope badges
Short badges near the hero show the policy scope, Pakistani...
Section anchors
Each section has a clear anchor so you can return...
Local rail chips
JazzCash, Easypaisa, SadaPay, and Raast chips show where transaction references...
Date marker
A visible date marker helps you see when the wording...
Contact panel
The contact panel keeps privacy channels beside the policy text...
Plain labels
We use plain labels for collection, use, sharing, retention, and...
Questions About Our Privacy Policy
We collect account details you provide, login and device records, transaction references, and support messages. We use them for account access, security checks, service requests, and duties that apply in supported regions.
No. We do not sell your personal data. Limited sharing can happen with payment providers, verification services, security tools, or legal authorities when needed to run your account or follow applicable law.
We may receive reference numbers, status updates, wallet names, or timestamps from JazzCash and Easypaisa flows. The provider keeps its own records, and we keep only what is needed for account handling.
Yes, you can ask us to correct details linked to your account where applicable. We may verify your identity first so another person cannot alter your privacy records.
Retention depends on the data type, account status, legal duties, and dispute needs. We keep data only as long as we reasonably need it, then remove or anonymise it where possible.
Use in-account chat for quick routing or email us for formal privacy requests. Include your account email, supported region, and a clear request so we can respond safely.