Terms Of Use
Your terms set the rules of conduct; this privacy policy sets what we store to apply them. Both documents name the same account ID, so a clause in one can be traced in the other.
Your name, your mobile number, your JazzCash and Easypaisa transaction references — all of it sits under one privacy policy, and this page is that document in everyday...
This privacy policy applies to anyone holding an account with 365pkr game in supported regions, and it is drafted to sit alongside the local rules that reach Pakistan. Where local law permits, we process your details on the basis of the consent you give at registration and our need to run an account-based service. That is why we keep a record of
your identity checks, your JazzCash, Easypaisa, SadaPay, NayaPay and Raast transaction references, and the device you sign in from. Part of that record exists because bookkeeping rules require it, so it survives after you close your account; the rest you can ask us to erase. If a request of yours meets a legal duty, we will say so plainly rather than quietly
ignore it. This policy also lists the categories we never sell and how long each one stays on our systems.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Three groups touch this document: the team that drafts it, the payment staff who apply it to your JazzCash and Easypaisa records, and an outside adviser who checks it against Pakistani record-keeping...
Our own policy team writes each clause rather than licensing a generic template, so the wording matches how verification, withdrawals and chat support actually work at 365pkr game.
An adviser with Pakistan-facing practice reads every revision before it goes live and flags anything that sits badly against local record-keeping duties or consumer rules.
The staff who process JazzCash, Easypaisa, SadaPay and Raast transfers tell us how transaction references are stored, which keeps our clauses accurate instead of theoretical.
Each version carries the date it took effect, and a short change log at the top of the page names what was altered, so a returning reader can tell what is new.
English-speaking agents cover policy questions every day, with chat open at all hours, so a query about your own record rarely waits more than a single working day.
Ask us to explain any clause in ordinary words and we answer in writing you can keep, without sending you back to the same paragraph you just read.
This document is one of several that govern an account here, and they are meant to read as a set. Where our terms describe what you may do, this policy describes what...
Your terms set the rules of conduct; this privacy policy sets what we store to apply them. Both documents name the same account ID, so a clause in one can be traced in the other.
The cookie page lists the trackers your browser receives. This policy goes further and states how long each of those identifiers is kept and which ones you can switch off yourself.
Verification explains which documents we ask for. The policy adds the retention side, covering how long an approved identity scan stays on file and what happens to it after closure.
Withdrawal rules cover timing and minimums, while the policy covers the records behind them, including JazzCash and Easypaisa references and which staff are cleared to open them.
Closing your account ends lobby access, and the policy spells out which records outlive that closure because Pakistani bookkeeping duties require them to remain on our systems.
The complaints page tells you where to raise a dispute. The policy adds what data we hand over while a case runs and how long the case file is retained afterwards.
Each promotion carries its own conditions, and the policy explains which account data those conditions rely on and confirms we do not sell entry details to the partners who fund them.
We lay this document out so you can find an answer without reading it end to end. A dated change log opens it, a table of...
The first block names what moved in the current version and the date it took effect, so a returning reader can spot the difference in under a minute.
One table groups what we hold into identity, contact, transaction, device and support records, and every row points to the clause that governs that category.
Each category carries a stated retention term, from short-lived chat transcripts to transaction references that stay for the span Pakistani bookkeeping rules set out.
This block names the processors who can see any part of your record, from payment handling to fraud screening, and says what each one may do with it.
Direct links to the copy, correction and erasure forms sit inside the relevant clauses, so you can send a request without leaving the paragraph you just read.
A closing block lists the controls you hold yourself, covering marketing messages, chat transcripts and the identifiers tied to the device you sign in from.