Account terms
Our account terms point back to this Privacy Policy when they mention personal data. That keeps contract wording separate from privacy rights while still showing how both documents connect.
LEGAL REFERENCE
Privacy Policy for 388 games Pakistan
388 games puts your account data, device checks, and Pakistan payment references into one clear Privacy Policy, so you can see what we collect before you open an...
Account dataDevice checksSupport recordsPayment references
How we handle your privacy
This policy explains how 388 games collects, uses, stores, and shares data connected with your account in supported regions of Pakistan, where local law permits. We collect only the details needed to create and protect your account, process payments, manage security checks, run support conversations, and meet lawful requests. JazzCash, Easypaisa, SadaPay, and Raast references may appear in our records as transaction
IDs, phone-number fragments, time stamps, or receipt images you send to us. We do not sell your personal data. Access to policy records is limited to trained teams handling support, risk checks, finance reconciliation, and technical maintenance. When you ask about privacy, we verify ownership before sharing or changing account data. These steps help us keep your request tied to you, not
another account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT PATHS
Where to ask privacy questions
Privacy requests need a secure route because they can involve account records, identity checks, and payment references. We keep the contact paths below separate from general lobby messages so your request reaches the team that can verify, trace, and answer it.
Team online
Privacy email
Send a privacy request with your registered phone number or email. We use those details only to locate your account record, confirm ownership, and respond without exposing data through chat.
Account chat
Open chat from the account menu if you need help finding this policy or sending a request. Our team may ask short security questions before discussing any personal record.
Document channel
If we need proof for a correction or access request, we provide a secure upload route. Files are linked to the request and kept only as long as required.
POLICY CHECKS
How we keep this policy accurate
We write this Privacy Policy from the way our account, support, security, and finance tools actually work. The aim is simple: you should be able to see why each data point is...
Internal checking
Each policy change is checked by our internal content and operations teams before publication. We look for plain wording, accurate contact paths, and data uses that match how our account tools work.
Local context
Pakistan payment references are described in practical terms, including JazzCash, Easypaisa, SadaPay, and Raast receipts. We explain the data trail without turning it into a payment instruction page.
Security alignment
Login alerts, device signals, password resets, and session checks are covered because they affect privacy. We connect those safeguards to the account data we may process during access checks.
Support handling
Support records can include chat text, screenshots, and request history. We describe how those records help us answer you while limiting access to staff who need the details.
Data retention
Retention wording is tied to account activity, payment reconciliation, security needs, and legal requests. We avoid open-ended language and explain why some records remain after a request closes.
Change tracking
When the policy changes, we update the page date and adjust related wording across linked pages. That helps you compare current privacy terms without chasing mixed messages.
PAGE ALIGNMENT
Consistent privacy wording across our pages
Your privacy rights should not change from one 388 games page to another. We keep linked policy pages aligned so account creation, login checks, support requests, and payment-reference handling use the same...
Cookie notice
Cookie wording explains browser storage, device identifiers, and session tools in the same privacy language used here. You can compare tracking purposes without learning a second vocabulary.
Support pages
Support pages use the same request channels, verification wording, and response process. If you move from help chat to this policy, the privacy steps should feel familiar.
Payment screens
Payment screens may show JazzCash, Easypaisa, SadaPay, or Raast references. This policy explains the data kept from those screens, including receipt timing and reconciliation records.
Security prompts
Login prompts and password resets refer to device checks and session records. This policy explains why those signals matter and how they help protect account privacy.
Offer pages
If an offer page asks you to check account status, the related privacy wording still follows this policy. We keep eligibility checks separate from unnecessary personal detail.
App-like access
When you add 388 games to your phone screen through the browser, the same privacy policy applies. Device permissions and session storage remain covered by this page.
VISIBLE CONTROLS
Visible privacy cues on the page
This page is arranged so you can spot the practical privacy parts without searching through unrelated copy. We place contact routes, data categories, local payment references, and account-control...
Plain summary
The opening section states the main privacy purpose before the...
Data map
Policy sections group data by use, not by legal jargon...
Contact strip
Contact choices are shown as direct paths for privacy requests...
Local rail chips
JazzCash, Easypaisa, SadaPay, and Raast appear as context chips because...
Retention labels
Retention wording is placed near the data categories it affects...
Choice prompts
Where privacy choices exist, we state how to ask for...
Privacy Policy questions from Pakistan
We collect registration details, contact data, login records, device signals, and security checks needed to create and protect your account. If a payment is involved, related references may also be stored.
We keep payment references to match your account with a transaction, investigate mismatches, and maintain finance records. These references may include receipt images, transaction IDs, time stamps, and partial phone details.
Yes. Send a privacy request through the contact path linked to your account. We verify ownership first, then provide the data we can share under applicable law and security rules.
Device and login data helps us recognise normal account access, detect unusual sessions, and manage password resets. We use those signals for privacy protection, security checks, and support troubleshooting.
No. We do not sell your personal data. We may share limited records with service providers or authorities only when needed for account operation, security, payment reconciliation, or lawful requests.
Support chats are kept for service quality, dispute handling, security checks, and account history. Retention can vary by request type, but access is limited to teams handling the related task.
We update the page date when material wording changes. If a change affects how we handle your account data, we may also show an account message or support notice.