LEGAL REFERENCE

Privacy Policy for Your g2a.com Account

Our Privacy Policy tells you how g2a.com handles account, lobby, sportsbook and Pakistani payment data before you open an account. Read it to see what we collect, why...

Account data explainedCookie choices coveredPakistan payment contextSecurity checks described
g2a.com Privacy Policy for Your g2a.com Account

How We Handle Your Data

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

CONTACT ROUTES

Ask Us About Your Privacy

You can reach us about privacy from inside your account or through the help address shown on g2a.com. Tell us which right...

Account chat Use live chat after signing in when a...
Email request Send privacy requests by email when you need...
Payment query If your request relates to JazzCash, Easypaisa, SadaPay...
POLICY CARE

How This Policy Is Checked

We keep this policy tied to real account flows on g2a.com rather than abstract wording. Each change is checked against account sign-in, identity checks, cookies, support replies, payment handling and payout verification...

Operational checks

Our privacy wording is matched against actual account screens, not a blank template. If a new field appears during sign-in, we assess why it exists before keeping it.

Payment mapping

JazzCash, Easypaisa, SadaPay and Raast records are mapped to account events through references and timestamps. We avoid collecting wallet credentials because those are not needed.

Cookie control

Cookie categories are separated so essential security tools are not mixed with preference settings. You can adjust non-essential choices through the cookie panel when available.

Access checks

Login history, device signals and failed password attempts help us protect your account. These signals are kept only as long as needed for security and lawful duties.

Partner limits

Hosting, analytics, payment and fraud partners receive limited data for defined tasks. We require them to protect the data and not use it for unrelated purposes.

Change control

When we amend this Privacy Policy, we record the reason, date and affected section internally. Major changes are highlighted on the page before they take effect.

PAGE ALIGNMENT

Aligned With Our Other Pages

Our Privacy Policy sits beside the Terms, Cookie Policy, account rules and payment help pages. Each page has its own purpose, but they use the same account facts so you do not...

01

Terms alignment

The Terms explain account duties and allowed access. This Privacy Policy explains the data linked to those duties, including sign-in logs, identity checks and security records.

02

Cookie alignment

The Cookie Policy explains browser storage and consent tools. This page connects those tools to account security, preference memory, analytics and fraud prevention on g2a.com.

03

Payment help alignment

Payment help pages describe status messages and reference numbers. This policy explains how those references are used, stored and matched to your account for support.

04

Security alignment

Security pages discuss passwords, sessions and alerts. This Privacy Policy explains what device, IP and login data we process to keep those protections working.

05

Account rules alignment

Account rules may require name, age status, location and access checks. This page explains why those fields matter and how long related records may remain.

06

Promotion alignment

When account offers require eligibility checks, this policy explains the data used for that decision. We keep the privacy wording separate from offer copy.

07

Support alignment

Support pages tell you how to contact us. This policy explains what data our team may view, request, correct or delete while handling your privacy case.

Privacy Cues You Can See

We design the privacy page so you can scan the points that matter before you open an account or continue using g2a.com. Short chips show local...

Clear section labels

Each block is labelled by purpose, so you can move from collected data to contact rights without guessing. The layout keeps legal wording close to account examples.

Local context chips

Short chips mention JazzCash, Easypaisa, SadaPay and Raast only where payment records matter. They help you spot which privacy section applies to Pakistan activity.

Plain account examples

We use account actions such as login, verification, chat and payout checks to explain data use. This keeps the policy practical without turning it into feature copy.

Rights grouped together

Access, correction, deletion and consent choices are kept close to the contact routes. You can see what to ask for before sending a privacy request.

Security wording nearby

Device, session and fraud signals are described near the reasons for processing. This helps you connect security checks with the data we may keep.

FAQ at the end

The final questions answer practical privacy points in short form. If you need more detail, the contact routes above show how to reach us directly.

Privacy Policy Questions Answered

We collect account details, contact data, login signals, device data, payment references and support messages. We only ask for data needed to operate your account, confirm transactions, secure access or meet lawful duties.

JazzCash, Easypaisa, SadaPay and Raast references help us match a payment event to your account. We use transaction IDs, timestamps and status messages, not your wallet PIN or full wallet access.

Yes. Contact us from your account email and state that you want access to your data. We may verify identity first, then provide the data we can lawfully release.

You can request deletion through support or email. Some records may be kept for security, dispute handling, fraud prevention or lawful duties, and we will explain any limit that applies.

Cookies help with sign-in, session security, preferences and site measurement. Essential cookies keep the account working, while non-essential settings can be adjusted through the cookie tools when available.

Some partners help us with hosting, analytics, payment routing, fraud checks and support tools. They receive limited data for assigned tasks and must protect it from unrelated use.