LEGAL REFERENCE

q98 Privacy Policy for Pakistan

q98 keeps account privacy clear from the first screen: what we collect, why we use it, and how your Pakistan payment context is handled. Open your account only...

Account data usePakistan payment contextDevice security signalsSupport contact routes
q98 q98 Privacy Policy for Pakistan

How We Handle Your Data

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

HELP PATHS

Contact Us About Privacy

Privacy questions should reach the team that can see your account record safely. Use the route that matches your request, include your account email or phone, and avoid sharing card or wallet PINs in any message.

Team online

Live chat

Use chat from your signed-in account when you need a quick privacy check on profile data, login alerts, or payment labels linked with JazzCash, Easypaisa, SadaPay, or Raast.

Email desk

Send email for detailed privacy requests, such as asking what account data we hold, why a record is needed, or how long a support thread may remain stored.

Account centre

Open the account centre to change contact details, refresh your password, check active sessions, and reduce avoidable exposure before you ask our team for deeper privacy help.

POLICY CARE

How We Keep Policy Checks Current

Our policy work is tied to real account handling, not generic wording. We check this page when data flows change, when support routing changes, or when Pakistan payment...

Operational input

The policy reflects account steps we actually run: sign-in, verification, payment context, support messages, security checks, and record handling tied...

Local wording

We name Pakistan rails such as JazzCash, Easypaisa, SadaPay, and Raast only where they help explain how payment-related labels can...

Security signals

Device type, browser session, IP region, and failed login patterns may be processed to protect your account and help us...

Partner limits

When hosting, analytics, support, or verification partners process data for q98, their role is limited to the task we assign...

Record discipline

We keep account, payment-context, and support records for service, security, legal, and dispute needs, then reduce or remove data when...

Clear updates

If we change how we collect or use your data, this page is updated so you can read the current...

How Privacy Lines Up Elsewhere

This page works with our other legal pages, but it has one job: explain privacy. Where another page covers account rules, cookies, or promotions, this page explains the...

Terms pageOur terms explain account use and service access; this policy explains the personal data connected with those actions, including profile records, login logs, and verification checks.
Cookie pageCookie wording deals with browser storage and tracking choices; this policy connects those signals to wider privacy handling across account security, analytics, and session stability.
Promotions pageIf you open a promotional area, this policy explains the data used to show eligibility, record participation, and answer your support questions about account visibility.
Payments pagePayment pages describe account funding routes; this policy explains how related labels, reference numbers, and verification records may be stored for support and security checks.
Security pageSecurity wording explains protective tools; this policy explains the personal data those tools may process, such as device signals, login history, and unusual access alerts.
Support pageSupport wording explains how to contact us; this policy explains how your messages, attachments, and account references are handled after you ask for help.
Account pageAccount pages let you manage profile details; this policy explains why those fields exist, how changes are recorded, and when q98 may retain past values.

Visible Privacy Layout Cues

We design this policy page so key privacy points are easy to scan before you join. The layout separates collection, purpose, sharing, storage, rights, and contact...

Date marker

A visible date marker helps you see whether the policy has changed before you continue account activity, especially after updates to verification or support routing.

Purpose blocks

Each privacy purpose is grouped by function, so you can separate account setup, security monitoring, payment context, support handling, and legal record needs at a glance.

Local labels

Pakistan payment names are used as context labels only, helping you understand how JazzCash, Easypaisa, SadaPay, and Raast references may appear in account records.

Choice prompts

Where you can change profile fields, communication settings, or browser storage choices, we point you toward the relevant account area instead of hiding the action.

Sharing limits

Partner references are written beside the privacy purpose they support, so you can see when hosting, analytics, verification, or support routing may involve another service.

Contact panel

The contact panel stays close to privacy wording so you can ask about access, correction, removal, or retention without searching through unrelated casino or sportsbook content.

Privacy Questions Before You Join

We collect account details you provide, sign-in records, device and browser signals, payment context labels, support messages, and verification records needed to run your account safely.

We use your data to create and manage your account, protect access, process payment context, answer support requests, keep service records, and meet legal duties in supported regions.

Yes, only where a partner helps with hosting, analytics, support routing, verification, or security. They may process data for that assigned task, not for unrelated use.

JazzCash, Easypaisa, SadaPay, and Raast references may appear as payment context in your account records. We use those labels for verification, support, reconciliation, and security checks.

Yes. Contact support from your account or email us with the field that needs correction. We may verify your identity before changing sensitive profile or payment-context records.

Retention depends on the record type. Account, security, support, and payment-context records are kept while needed for service, disputes, legal duties, and fraud prevention.