Account pages
Account pages refer to login data, profile details and verification checks. This Privacy Policy gives the deeper reason for those fields and explains how we use them after you submit them.
LEGAL REFERENCE
g2g - Privacy Policy for Pakistan account data
g2g puts account data, payment checks and lobby privacy choices into one Privacy Policy for Pakistan access where local law permits. Before you open an account, you can...
Pakistan data contextJazzCash privacy contextEasypaisa wallet checksSadaPay and Raast
How we handle your data
This Privacy Policy explains how we handle data connected with your g2g account, device sessions, identity checks, wallet activity and support messages. We collect only what helps us run access, protect your account, process payment records and answer your privacy questions. For Pakistan, wallet references may include JazzCash, Easypaisa, SadaPay and Raast where those rails are supported. We do not sell your
personal data. We share limited details with service partners only when needed for verification, fraud checks, payment routing, security logging or legal duties. Access to g2g remains subject to supported regions and where local law permits. You can ask us about access, correction, deletion, retention or consent through the contact paths below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How our policy stays current
We write this page from our operating view of g2g, not from generic legal copy. Each privacy check looks at account journeys, wallet references, support handling, device security...
Account mapping
We map the privacy wording against real account steps, including join forms, login screens, profile edits and verification prompts, so...
Wallet context
Our checks include JazzCash, Easypaisa, SadaPay and Raast references because those names may appear in payment records, support tickets or...
Access controls
We describe staff access carefully because privacy depends on who can see account data. Internal access is limited by role...
Cookie wording
We keep cookie language connected to site use, session continuity, fraud checks and preference storage. That helps you understand why...
Retention checks
We explain retention around account records, wallet activity, support messages and security logs. Some records may stay longer where dispute...
Regional wording
Pakistan access is described with supported regions and where local law permits. We avoid broad promises and keep the policy...
PAGE ALIGNMENT
Aligned privacy across g2g pages
You should not see one privacy story on the account page and another on the support page. We keep related policy pages aligned so each page explains the same data practices from...
Wallet screens
Wallet screens may show JazzCash, Easypaisa, SadaPay or Raast references. The Privacy Policy explains how those references can be stored, matched and used for reconciliation or support.
Support pages
Support pages ask for enough detail to solve your issue. This policy sets the boundary by explaining why we request account identifiers and how we handle messages after your case closes.
Security pages
Security pages discuss login protection and device alerts. The Privacy Policy adds context on session logs, IP data, browser markers and how those signals help protect your account.
Cookie banner
The cookie banner is short by design, while this page explains storage categories in more depth. You can compare both to understand session, preference and analytics handling.
Terms pages
Terms pages set account rules, while this Privacy Policy focuses on personal data. We keep those roles separate so legal duties and privacy rights do not blur together.
Promo board
If the promo board records eligibility or account history, this policy explains the data side. We avoid placing promotional wording inside privacy rights or data retention explanations.
Visible privacy cues on this page
This page is arranged so you can scan the policy before creating or using an account. The layout highlights what data is collected, where payment references...
Plain headings
Each heading names a privacy task, such as collection, sharing, retention or contact. That structure helps you move straight to the data point you want without reading unrelated platform copy.
Local references
Pakistan wallet names appear only where they matter to privacy, such as payment records or support checks. We do not use those names to distract from account data handling.
Rights summary
The policy explains how you can ask about access, correction, deletion and consent. We keep those rights near contact paths so the next step is easy to find.
Retention signals
Retention wording appears beside account, wallet and security data examples. That placement helps you understand why some records are brief while others may be kept for compliance needs.
Security markers
Security language is tied to device checks, session logs and account protection. We avoid vague safety claims and explain the types of signals that may be processed.
Change marker
When the Privacy Policy changes, we aim to make the updated wording clear on the page. Material changes may also be signalled through account or support channels when appropriate.
Privacy questions from Pakistan accounts
We collect details needed to create and protect your account, such as contact data, login credentials, device signals and verification records. We also record wallet references when they are needed for payment handling.
Wallet references are used for payment matching, reconciliation, support and fraud checks. We limit access to staff or service partners who need those details for account handling or legal duties.
No. We do not sell your personal data. We share limited details only with processors, payment partners, security vendors or authorities when required for account operation, verification, dispute handling or legal compliance.
Cookies and similar storage help keep sessions active, remember preferences, measure site performance and detect suspicious activity. Some are needed for account security, while others may depend on your browser choices.
Yes. You can contact us to ask for access, correction, deletion or consent support. Some records may need to remain where payment disputes, security checks or legal duties require retention.
Retention depends on the record type. Support messages may be kept for case history, payment records for reconciliation, and security logs for account protection, fraud checks and legal requirements.
Access depends on supported regions and where local law permits. The Privacy Policy still explains how we handle data when you use g2g, contact support or interact with account features.