LEGAL REFERENCE

Privacy Policy for Your sfg2 Account

sfg2 keeps live casino, slots and sportsbook access in one account, so our Privacy Policy explains exactly how we handle your account details, device records and Pakistan payment...

Pakistan account dataJazzCash contextEasypaisa contextSadaPay recordsRaast checks
sfg2 Privacy Policy for Your sfg2 Account

How Our Privacy Policy Works

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

CONTACT PATHS

Contact Us About Privacy

Privacy questions need a clear route, not a maze. We keep the same contact paths inside your account area and on our brand home, so you can ask about access, correction, deletion or a payment record tied to your profile.

Team online

Account Help

Use the account help channel when you want us to locate profile details, session logs or payment references linked to your sfg2 account. We may ask for checks before discussing personal data.

Privacy Email

Send privacy requests by email if you need a written record of your question. Include your account phone number, approximate date and the data topic you want us to check.

Live Chat

Use chat for quick privacy routing, such as where to send a correction request or how payment references appear. Chat staff can escalate detailed data matters to our account team.

POLICY CARE

How We Keep This Policy Accurate

Our Privacy Policy is maintained by the team that works with account flow, verification and payment records. That matters because privacy wording must match how the product actually...

Account Flow Match

We map policy wording to the real account journey, from mobile number entry to login checks. When a field changes...

Payment Rail Detail

Our policy separates payment reference data from wallet credentials. For JazzCash, Easypaisa, SadaPay and Raast, we handle transaction status and...

Session Records

We explain why session logs exist, including device type, IP range, login time and account actions. These records help us...

Partner Checks

When service partners support hosting, analytics, verification or payment routing, we limit shared fields to the task. We also expect...

Local Language

We write this policy in clear Pakistani English so you can understand practical data use without legal fog. Key payment...

Change Tracking

When the policy changes, we update the page date and keep the new wording tied to account, security or payment...

Consistent Privacy Across sfg2 Pages

Privacy wording should not change its meaning from one sfg2 page to another. We align this page with account terms, cookie wording and support scripts, so you get...

Account Terms
Our account terms explain conduct and access rules, while this Privacy Policy explains data handling. When both mention verification, the privacy wording focuses on records collected and reasons for use.
Cookie Page
Cookie wording covers browser storage, analytics tags and preference tools. This Privacy Policy connects those records to account security, page performance and privacy choices without changing cookie meaning.
Support Scripts
Support replies follow the same privacy position shown here. Staff should not ask for full wallet access, secret credentials or unrelated documents when handling your privacy question.
Payment Screens
Payment screens may show JazzCash, Easypaisa, SadaPay or Raast status. This policy explains how those references are stored, checked and matched to your account request.
Security Prompts
Login checks, one-time codes and device prompts are security events. This policy explains why records of those events may remain on file after the session ends.
Promo Board
If you check the promo board, related account records may show eligibility status and timestamp. This policy explains that handling without turning privacy wording into promo copy.
Lobby Activity
Live tables, slots and sportsbook areas create session records. This policy keeps the privacy explanation focused on access, security and account history, not game promotion.

Policy Layout You Can Scan

We design this Privacy Policy so you can find the part that matters without reading a wall of legal copy. The layout separates data types, reasons...

Data Types

We group account details, device records, session activity and payment references separately. This helps you see which data comes from you and which data is created by platform activity.

Use Reasons

Each data category is tied to a reason, such as account access, verification, support, fraud prevention or legal compliance. We avoid vague wording where a practical reason can be stated.

Sharing Limits

The sharing section explains when partners may receive limited data for hosting, identity checks, analytics or payment routing. We do not describe open-ended sharing that leaves you guessing.

Retention Detail

Retention wording explains that some records remain while your account is active and some stay longer for security, dispute handling or legal reasons where local law permits.

Your Requests

The request section shows how you can ask to access, correct or delete data. We may verify identity before acting so another person cannot alter your privacy records.

Update Signals

When privacy wording changes, we show the updated date and keep the new text on this page. Important account-related changes may also be flagged after login.

Privacy Policy Questions Answered

We collect account details you provide, login and device records, session activity, support messages and payment references. The Privacy Policy explains each category so you know what is collected during normal account use.

No. For JazzCash, Easypaisa, SadaPay and Raast activity, we record transaction context such as reference number, status, amount and timing. We do not need your wallet password to process account records.

Device and login records help us protect account access, confirm security events and investigate disputed activity. The Privacy Policy treats these records as security data, not as open-ended tracking for unrelated use.

Yes. Contact us through the privacy path and explain which account detail appears wrong. We may verify your identity before changing records, especially where payment references or security logs are involved.

We may share limited fields with partners that support hosting, verification, analytics, payment routing or legal requests. The Privacy Policy requires a clear purpose before any partner receives account-linked data.

Retention depends on the record type. Some data stays while your account remains active, while payment, security and dispute records may remain longer where local law permits or risk checks require it.