Terms Of Use
Sets the account rules you agree to at sign-up, while this page handles what we do with the data those rules create. Read them side by side and nothing contradicts.
Everything we collect when you open your guruji game account is set out on this page in plain English. Read it once and you will know how your...
Privacy terms only make sense alongside the law you live under, so everything here is framed as applying where local law permits and in supported regions. Our commitments sit under Pakistani law, and where your province or territory sets a stricter rule, the stricter rule is the one we follow for your account. The wording stays deliberately plain: we tell you which
data categories we hold, why we hold them, how long they stay, and who can see them. Wallet identifiers from JazzCash, Easypaisa, SadaPay and Raast are stored as references, never as credentials you type back to us. If any sentence here conflicts with a mandatory local requirement, that requirement wins and we correct this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Accountability only counts if somebody owns it. This page has one named custodian inside guruji game, a dated change log anyone can read, and staff access rules that limit who can open...
One named custodian owns this page and signs off every change, so wording never drifts after a product launch without somebody accountable ticking it through.
Every edit to this policy is dated and kept in an open change log, so you can see what moved, when it moved, and which paragraph was rewritten because of it.
References from JazzCash, Easypaisa, SadaPay, NayaPay and Raast are tokenised before storage, so a database copy never carries the full detail you type at checkout on a phone or desktop.
We publish how long each category stays with us. Account data lives as long as your account does, wallet references follow tax rules, and marketing preferences expire sooner.
Staff access runs on least-privilege roles with two-factor login, and every look-up of your record is logged against a named team account rather than a shared login used by the whole office.
Hosting, messaging and payment partners that touch your data are listed with the country they store it in, and we flag any new one here before it goes live.
Our policy pages are written as one set, so a promise made here cannot quietly vanish from the terms, cookie page or KYC section. Where two pages touch the same ground, the...
Sets the account rules you agree to at sign-up, while this page handles what we do with the data those rules create. Read them side by side and nothing contradicts.
Covers the small files stored in your browser. It picks up where the device section here stops, listing each cookie by name, purpose and how long it stays.
Explains how payouts to JazzCash, Easypaisa, SadaPay, NayaPay and Raast are verified. This page explains which identity and wallet details we keep while that check runs.
Tells you how to shut an account and what survives afterwards. The retention table here is what closure actually follows, so the two pages must agree word for word.
Maps how a disagreement escalates from chat to a senior desk. If your complaint touches data handling, the timelines quoted here apply instead of the general ones in that route.
Describes the documents we ask for before a first payout. The data categories listed there match the table on this page, so you are never asked for something we have not disclosed.
Handles promotional SMS and email separately from the account messages we have to send. Unticking it there changes nothing about the security alerts your own account still needs.
Nothing about a privacy page has to be a wall of grey. Here you get a three-line summary before the long wording, a sidebar that tracks your place...