LEGAL REFERENCE

Privacy Policy For Your baji22 Account

This Privacy Policy explains how baji22 collects, uses, stores and protects personal data when you open an account or use our services in supported Pakistan regions. We keep...

Clear data purposesPakistan-focused wordingAccount securityContact choices
baji22 Privacy Policy For Your baji22 Account

How We Handle Personal Data

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY CONTACT

Reach Us About Your Data

Our support routes are available for privacy questions, account-data requests and concerns about how a record has been used. Tell us the email or phone number linked with your account, describe the request clearly and avoid sending passwords or one-time codes. We may ask for reasonable proof of account control before releasing or changing personal details.

Team online

Privacy request

Ask us to access, correct or remove eligible account data. Include your registered contact detail and the specific records involved so our team can locate the right account without requesting unnecessary material.

Account support

Use the account support channel when a privacy matter affects login access, identity checks or transaction history. We will separate operational help from data requests and keep the conversation tied to your account.

Security concern

Tell us promptly if you notice an unfamiliar login, device, message or account change. We may restrict access while checking the event, then contact you through a channel already connected with your account.

DATA SAFEGUARDS

Controls Behind This Policy

Privacy is built into the way we operate account access and customer care. We limit internal access according to work needs, record important security events and use verification steps when a request...

Purpose-based collection

We ask for account, contact, device and transaction details because they help deliver a requested service, protect access, resolve disputes or meet a lawful operating duty.

Access controls

Our account systems use permission levels so staff and service providers receive only the data needed for their assigned work, with sensitive actions subject to additional checks.

Payment references

When you use JazzCash, Easypaisa, SadaPay or Raast, we may retain status, amount and reference data for reconciliation without asking for your wallet password.

Device signals

Login time, browser type, device markers and approximate location can help identify unusual access. These signals are assessed alongside account activity rather than treated as conclusive alone.

Retention checks

We periodically consider whether records are still needed for service delivery, safety, disputes or legal duties. Data no longer required is removed, anonymised or securely restricted.

Policy changes

If this policy changes in a material way, we will update the page and may use an account contact route when notice is appropriate for the change.

How This Policy Fits Related Pages

This page focuses on personal data and privacy choices, while related legal pages may address account conduct, service access or transaction handling. Reading them together gives you a...

Privacy Policy
Use this page for collection, use, storage, sharing, security controls, retention and requests concerning personal data connected with your baji22 account.
Account terms
Account terms address the conditions for opening, maintaining and using an account, while this policy explains the data handling that supports those activities.
Payment records
Questions about JazzCash, Easypaisa, SadaPay or Raast references belong here when they concern personal data; a transaction page may address processing status separately.
Security events
A suspected account compromise should be sent to support promptly. This policy explains how related records may be checked, restricted and retained during the response.
Regional access
Where local law permits access, regional rules may affect an account request, retention period or identity check. We apply the relevant requirement to the specific request.
Third-party services
Payment, hosting, messaging and security providers may process limited data for defined tasks. Their role does not remove our duty to explain the handling on this page.
Policy updates
The date and wording on this page show the current privacy position. Check it again after a material change or when you begin using a new account function.
PAGE HIGHLIGHTS

What This Privacy Page Covers

We designed this page so you can move from the main purpose of data collection to practical controls and then to contact options. Each visible element addresses a...

Collection map See which account, contact, device and transaction details may be...
Use and sharing Understand when baji22 uses data internally and when selected providers...
Security practice Find the everyday controls that help protect account records, including...
Retention approach Learn why some records remain available after an account action...
Your requests Use the contact paths to ask about access, correction, deletion...
Regional context The wording explains how supported Pakistan regions and applicable local...

Privacy Answers For Your Account

We may collect contact and account details, login records, device signals, approximate location, transaction references and support messages. The exact data depends on the action you take and the service needed.

A check may help confirm account ownership, protect against unauthorised changes, resolve a transaction issue or meet a legal operating duty. We request only the material needed for that purpose.

No. For JazzCash, Easypaisa, SadaPay or Raast activity, we may receive status, amount and reference details needed for reconciliation, but your wallet password and one-time code should remain private.

Yes, where local law permits. Contact support from an account-linked route, describe the categories you want and complete reasonable ownership checks before we provide an appropriate response.

You may request correction or deletion where applicable. Some records may need to remain for security, dispute handling, legal duties or transaction reconciliation, and we will explain any relevant restriction.

Retention depends on the record and its purpose. We may keep data for account administration, security investigations, disputes, audits or legal duties, then remove, anonymise or restrict it when no longer needed.

Contact support promptly, change your account password through the normal account route and avoid sharing codes. We may review access events, restrict sensitive actions and contact you through a linked channel.