Account form
The account form collects contact details and identifiers needed to create your profile. Its privacy link points back here so you can read the purpose before sharing data.
LEGAL REFERENCE
How v44 handles your data
v44 keeps one clear Privacy Policy for your account, lobby access, identity checks and Pakistani payment records. Open your account where local law permits and you can see...
Account data usePakistan support contextJazzCash and Raast recordsAccess and security checks
Data use across your account
This Privacy Policy explains how we collect, use, store and share data when you create or manage a v44 account in supported regions. We record details you provide, device signals used for security, transaction references from Pakistani payment rails, support messages and activity needed to run your account. We use this data to confirm access, process withdrawals, detect misuse, answer your requests
and meet legal or operational duties where local law permits. We do not ask for more data than the account flow needs, and we restrict internal access to teams handling verification, payments, security and support.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Privacy questions reach real support
If you want to ask about your personal data, correct an account detail or query how a payment record is handled, contact us from inside your account first. That route helps us match your request to the right profile without asking for repeated screenshots or extra identity material.
Team online
Account chat
Use the secure chat after login when your privacy request relates to account access, identity checks or transaction history. We can view your verified profile and reply without exposing data in open channels.
Email request
Email suits longer privacy requests, such as correction, access or deletion queries. Include your account email, registered phone code and a short reason so we can route it correctly.
Payment query
For JazzCash, Easypaisa, SadaPay or Raast privacy questions, share only the reference code requested by support. We use it to find the record without collecting full wallet access.
DATA CHECKS
How we keep the policy current
Our Privacy Policy is maintained by teams that handle account operations, payments, security and customer support. When a flow changes, such as a new verification step or altered withdrawal check, we update...
Operational input
Policy wording is checked against real account journeys, from registration fields to withdrawal verification. This keeps the document aligned with the data we request and the reasons we request it.
Payment handling
We map JazzCash, Easypaisa, SadaPay and Raast records separately because each rail sends different references. The policy explains why these records may be kept for reconciliation.
Security signals
Login time, device type and session behaviour may be logged to protect your account. We use these signals for fraud checks, access alerts and support verification.
Support records
Messages sent to our team may be retained with your account so we can resolve repeated privacy queries, trace past instructions and avoid asking you to repeat sensitive details.
Access control
Internal access is limited to staff roles that need the data for payments, account safety or support. We monitor access paths and remove permissions when they are no longer needed.
Change tracking
When we update this Privacy Policy, we adjust the date and keep the language specific to current account flows. Major changes are made visible before they affect your choices.
POLICY ALIGNMENT
Consistent wording across v44 pages
You may see privacy wording linked from the account form, cashier screen, support area and footer. We keep those references aligned so you are not given mixed messages about data collection, transaction...
Cashier screen
The cashier privacy text focuses on payment references, wallet names and reconciliation checks. It matches this policy instead of adding separate rules for JazzCash or Easypaisa.
Verification steps
When we ask for identity material, the linked wording explains why the check is needed, who handles it and how it supports withdrawal or account security decisions.
Support area
Support prompts remind you not to send unnecessary documents in chat. The same principle appears here, where we explain collecting only what your request needs.
Cookie notice
Cookie wording connects to this policy for device and session data. We describe how signals assist login safety, language selection and account continuity across visits.
Promo board
If you check what is running this week, account eligibility may use basic profile data. The policy states how those checks work without exposing private account details.
Footer link
The footer link brings you to this single policy page. Keeping one source reduces confusion and helps you find the latest wording when account flows change.
VISIBLE CUES
Privacy cues you can see
We built the policy area to make privacy choices easy to notice before you open forms or contact support. These page elements are not decoration; they show where...
Plain headings
Section headings use direct wording so you can find collection...
Local context
Pakistan references are included where they matter, especially wallet records...
Short badges
The badges near the hero summarise key privacy areas without...
Contact prompts
Contact cards separate chat, email and payment queries so you...
Update signals
Policy update language appears near operational sections, not hidden away...
FAQ links
Questions at the end address common privacy concerns in account...
Questions about your privacy
We collect the details needed to create and protect your account, including contact data, login signals, verification records, support messages and payment references tied to JazzCash, Easypaisa, SadaPay or Raast.
Payment references help us match deposits, withdrawals and support queries to the correct account. We keep only the record needed for reconciliation, fraud checks and any duty that applies where local law permits.
Yes. Contact us through account chat or email with the detail that needs correction. We may verify your identity before changing records that affect access, withdrawals or account security.
We may share limited data with service partners that help process payments, verify accounts, host systems or detect misuse. These partners receive only what they need to perform the assigned task.
Retention depends on the data type, legal duties and account history. Payment and verification records may be kept longer than simple support messages because they support audits and dispute handling.
Start with secure chat after login for account-linked requests. If you prefer email, include your registered contact detail and a clear privacy question, but avoid sending unnecessary documents.