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.
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...
This Privacy Policy covers the data we collect when you create an account, verify access, browse game pages, enter sportsbook areas, contact us, or request a payout in supported regions where local law permits. We use your data to run your account, keep sessions secure, process payments, detect misuse, answer privacy requests and meet lawful record duties. Pakistani payment references such as
transaction IDs, sender names and status messages may be matched with your g2a.com account so we can confirm activity without exposing full wallet access. We do not sell your account data. When service partners help us with hosting, analytics, fraud checks or payment routing, they receive only what is needed for that task.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
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...
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.
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 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.
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.
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.
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.
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...
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.
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.
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.
Security pages discuss passwords, sessions and alerts. This Privacy Policy explains what device, IP and login data we process to keep those protections working.
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.
When account offers require eligibility checks, this policy explains the data used for that decision. We keep the privacy wording separate from offer copy.
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.
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...
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.
Short chips mention JazzCash, Easypaisa, SadaPay and Raast only where payment records matter. They help you spot which privacy section applies to Pakistan activity.
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.
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.
Device, session and fraud signals are described near the reasons for processing. This helps you connect security checks with the data we may keep.
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.