Privacy Policy
This page explains personal data collection, account records, payment references, sharing, retention, security, and your request routes. It is the main page for privacy questions about gm7 game.
LEGAL REFERENCE
Privacy Policy for Pakistan Accounts
Your gm7 game privacy choices, account records, and Pakistan payment receipts are handled in one clear policy. Open your account where local law permits, and we will show...
Pakistan account dataJazzCash receipt careEasypaisa record handlingRaast verification logs
How We Handle Your Data
This Privacy Policy explains how gm7 game manages personal data when you create an account, access the lobby, contact support, or use Pakistan payment rails in supported regions. We collect only the details needed to run your account, confirm access, process wallet activity, keep security logs, and answer your requests. Payment records connected with JazzCash, Easypaisa, SadaPay, and Raast are used to
match your account activity with transaction references, not to sell your data. We may share limited records with service providers that help us operate payments, identity checks, hosting, fraud controls, analytics, and support channels. We keep data only for as long as it is needed for account service, legal duties, dispute handling, and security monitoring. You can contact us about access, correction,
deletion, or privacy questions at any time.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA CHECKS
How Our Policy Is Checked
We treat the Privacy Policy as an operating document, not a static page. Our team checks it against account flow, payment handling, support scripts, device security, and data...
Account Flow Matching
We compare the policy with the details requested during account opening, login checks, and profile updates, so the page reflects...
Payment Rail Mapping
We map JazzCash, Easypaisa, SadaPay, and Raast records to their purpose in the policy, including receipt matching, wallet reconciliation, dispute...
Security Log Purpose
We explain why device, IP, session, and access logs are kept. These records help protect your account, confirm unusual activity...
Support Script Alignment
Our support team uses privacy wording that matches this policy when handling data requests. That keeps chat and email answers...
Retention Schedule Check
We connect each record type with a retention reason, such as account service, legal duties, dispute handling, or security monitoring...
Change Notice Process
When the policy changes, we update the page date and keep the wording focused on your account data, payment references...
PAGE ALIGNMENT
Consistency Across Legal Pages
Our legal pages cover different areas, but the privacy wording stays consistent across them. This helps you understand which page covers data use, which page covers account rules, and which page explains...
Terms Page
The account rules page may mention data checks when they are needed for access, verification, or disputes. It points back here when the subject is privacy handling.
Cookie Page
Browser storage and tracking tools are explained separately, but the privacy page connects those tools with account security, analytics, session handling, and preference control.
Promotion Rules
If a campaign requires eligibility checks, the related records are still handled under this Privacy Policy. We avoid collecting extra data beyond what the account process requires.
Payment Help
Wallet help may describe JazzCash, Easypaisa, SadaPay, and Raast receipt matching, while this policy explains why those references are stored and who may process them.
Security Page
Security wording focuses on account protection, while this policy explains the data behind those controls, including login records, device signals, and unusual activity alerts.
Support Page
Support channels explain how to reach us, while this policy explains how your messages, attachments, verification replies, and account references are handled after contact.
Privacy Layout You Can Read
We designed this policy page so you can find privacy details without digging through broad platform copy. The layout highlights account data, security logs, sharing, retention...
Account Data Block
The account data block explains the details we collect during account opening, profile updates, and identity checks, with plain wording about why each record is needed.
Payment Reference Block
The payment reference block separates wallet receipts from personal profile data, showing how JazzCash, Easypaisa, SadaPay, and Raast references support reconciliation and dispute checks.
Security Records Block
The security block explains session logs, device signals, IP records, and access history in privacy terms, so you can see how account protection affects stored data.
Sharing Partners Block
The sharing block describes the limited service partners that help with hosting, payment processing, fraud controls, analytics, and customer support under controlled access.
Retention Block
The retention block connects stored records with clear reasons, including account service, legal duties, dispute handling, and security monitoring, rather than leaving storage periods vague.
Request Route Block
The request block shows how to ask for access, correction, deletion, or privacy clarification, and why we verify your account before discussing personal records.
Common Privacy Policy Questions
We collect account details, login records, device signals, support messages, payment references, and activity records needed to run your account, protect access, answer requests, and meet legal duties in supported regions.
JazzCash, Easypaisa, SadaPay, and Raast references help us match wallet activity with your account, trace disputes, prevent fraud, and confirm reconciliation without using the receipt for unrelated sales activity.
We share limited data with service partners that support hosting, payments, verification, analytics, security, and customer care. Each sharing purpose is tied to account operation, legal duties, or protection of your records.
Contact support by chat or email and state the privacy request you want to make. We may verify the account first, then respond about access, correction, deletion, or stored record questions.
We keep records while they are needed for account service, payment reconciliation, legal duties, dispute handling, and security monitoring. When a record is no longer needed, we remove or anonymise it where allowed.
Yes. Device data, IP records, session history, and login signals are covered by this Privacy Policy because they help secure your account, investigate unusual activity, and manage access where local law permits.
We may update the Privacy Policy when account flows, support routes, payment processing, security controls, or legal duties change. The page will be updated so you can read the current privacy wording.