Privacy Policy (This Page)
Collection, use, storage and your access rights sit here. Start on this page for any question about what we hold on your account and for how long we hold it.
This page lists everything we store about your 7773d game account, why we need it, and how long it stays with us. It covers login records, device details...
We apply the same internal standard to your data wherever you sign in, but some processing depends on where local law permits it and on which services run in your supported region. When you fund an account through JazzCash, Easypaisa, SadaPay or Raast, we receive a payment reference and a status, never your wallet PIN or bank credentials. That reference lets us
match a deposit to your account, run the checks that keep your login secure, and meet the record-keeping duties placed on us. Where a rule requires a set holding period, we keep the record for exactly that period. Where it does not apply in your region, we still follow the same standard.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We publish this policy so you can judge our data handling before you register, not after. The wording is checked whenever a payment rail, a game studio or a login verification step...
Every revision carries a date, and earlier versions stay on file so you can compare what moved. If a change affects how your data is used, we flag it on your account page.
Clauses are written in ordinary English rather than legal shorthand, so a reader in Lahore or Karachi can follow each paragraph without a translator and without guessing at the meaning.
The policy is written by our own compliance and engineering staff, the people who work with the systems holding your records. Nobody outside that team edits these paragraphs on our behalf.
Older versions stay archived and are available on request, letting you trace which wording applied on the day you registered or the day a JazzCash or Easypaisa payment cleared.
When a material change lands we post it before it takes effect and give you time to read it. Continued use of your account after the new date means you accept the update.
If a clause reads unclearly or sits out of step with what our app actually does, send a note. Corrections are logged and published rather than edited away quietly.
All our policy pages follow one editorial standard: the same heading order, the same revision cycle, the same plain tone. That consistency matters when you read two of them together, because a...
Collection, use, storage and your access rights sit here. Start on this page for any question about what we hold on your account and for how long we hold it.
Eligibility, conduct and account rules sit there. Both pages share the same definitions, so a term defined in one carries the same meaning wherever you read it.
Browser storage, session cookies and analytics tags are listed separately. Read it next to this policy if you want the full picture of what your device sends our servers.
JazzCash, Easypaisa, SadaPay and Raast processing windows live on their own page. The privacy angle, covering what we store from each rail and for how long, stays here.
Verification steps before a payout sit with the banking page, while the identity documents we keep for that check are described here, so the two read as one process.
Login protection, device checks and staff access controls are summarised on the security page, and the retention periods that apply to those logs appear inside this policy.
If support cannot settle a data question, the escalation path is published on its own page with the same reference numbers and timeframes we use here, so nothing gets lost between pages.
The policy is arranged so you can find an answer without reading every clause. Each block opens with a short summary line, then the detail, then the rights...