How We Handle Your Details
On this page we set out exactly what h789 game collects when you open an account, why we hold it, and the choices you keep over your own...
Where Our Privacy Rules Apply
We run h789 game under the privacy expectations that apply where you live, and where local law permits we follow the stricter standard. Your data sits with us while your account is active, plus a settlement and audit window afterwards. We collect only what the account needs: name, contact number, date of birth, device and connection details, and the transaction references your
JazzCash, Easypaisa, SadaPay or Raast payment produces. We do not sell personal data. Some rights differ by region — access, correction and closure requests are handled as local law allows. Cookies split into those keeping your session secure and an optional group you can switch off.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How To Ask About Your Data
If you want to know what we hold, or you need a record corrected, start with our support desk. Write from the email address on your account so we can match the request to the right profile, and tell us which detail you are querying. Payment disputes involving a JazzCash or Raast reference take slightly longer, because we check the reference first.
Live chat
Our chat window runs inside your signed-in account, so a privacy question rarely waits long. Agents see your ticket history and confirm what a request needs before it goes any further.
Email requests
Send data queries to our privacy mailbox and quote your account number. We answer with a written record you can keep, useful when you pass details to a bank or an employer.
Closure requests
Ask us to close your profile and we explain what stays on file for settlement and audit reasons, and for how long. You get a timeline rather than a vague promise.
Who Checks What We Publish
Our compliance and operations teams write and check this page together, so the wording matches the systems you use. The person drafting it sits with the staff who handle real account queries...
Revision cadence
We read this page against our live systems each quarter, and sooner whenever a payment route or storage rule changes. Each pass is dated and logged with the person who signed it off.
Named ownership
A named data lead answers for this policy rather than a faceless department. When you raise a query, that owner signs off the response you receive and stays reachable when you reply.
Plain-language drafting
We write clauses you can act on rather than dense legal blocks. If a sentence needs a lawyer standing beside it to make sense, we rewrite it before it goes live.
Wallet-side checks
Anything covering JazzCash, Easypaisa, SadaPay or Raast records is verified with the team that reconciles those settlements, so the retention windows you read are the ones we hold to.
Local context
The team behind this page works Pakistan hours and handles queries from Pakistani accounts, so the wording on document checks and settlement timing reflects how things run locally.
Change notices
When a clause shifts in a way that touches your rights, we post a notice inside your account before the change takes effect, giving you time to question it or close.
How This Page Fits Our Others
Privacy wording only works if it agrees with everything else you read on this site. Our account terms, cookie panel, security notices and payment pages describe the same...
| Account terms | Our terms page covers what you agree to at registration and points back here for anything about personal data. The two documents do not contradict each other on retention or access. |
|---|---|
| Cookie choices | The cookie panel lists the same storage reasons described in this policy. Switch off the optional group and the session cookies that keep your sign-in secure stay in place. |
| Wallet pages | Our JazzCash, Easypaisa, SadaPay and Raast pages explain settlement timing using the same reference numbers this policy mentions, so the window you read about is one window, not two. |
| Security notices | Sign-in alerts, device history and password rules live on the account-security page, and the records they generate are described here under device and connection details. One event, one set of records. |
| Support pages | Contact routes and response times match what the help page states, so you are never told one thing by chat and another by a written notice. We keep both updated together. |
| Language versions | Where this policy appears in more than one language, the English text stays the reference point and we note the date each translation was aligned to it. |
| Update log | Every revision is recorded with its date and a short summary of what moved, so you can see at a glance whether a clause you cared about has changed. |
Layout Choices You Will Notice
The policy-side layout is built so you can find an answer without hunting. Clauses sit under predictable headings, retention windows appear in compact tables, and the chips above...