Terms of use
Account conditions, eligibility in supported regions and what happens when you close the account. The same definitions are reused on every other policy page, so wording does not shift between them.
Every policy page on rss99 game is written for the account you open here: terms of use, privacy, security wording and how withdrawals are handled. Read them once...
Every clause here is written for the supported regions we serve, which for us means Pakistan and the areas where local law permits online account play. What you see is not identical in every province: the wording that binds you depends on where you sign in from, the device you use and the payment rail attached to your account. Access through JazzCash,
Easypaisa, SadaPay, NayaPay or Raast changes none of your rights under these pages; those names only mark the rails we support today. Where a local rule conflicts with a clause below, the local rule takes priority for you. We publish revisions before they take effect and keep earlier wording on file, so you can compare what applied when your account was opened.
If online account play is not permitted where you live, please do not open an account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy questions go straight to the desk that maintains these pages rather than a general queue, so you get an answer about the clause you actually asked about. Quote the section heading when you write in and we can point you to the exact line. The desk answers in English on Pakistan Standard Time, seven days a week.
Write to our policy desk with the section heading and the wording you are asking about. You get a written reply, and we keep that thread open until your question is properly closed.
Open the chat window from inside your account area and we pick the question up there. It is the quickest route when you are reading a clause and want an answer straight away.
The policy desk runs on Pakistan Standard Time, seven days a week, with shorter weekend hours. Anything that lands overnight is answered the following morning, always in writing.
Policy text here is drafted in plain English, checked against the rules that apply in supported regions, and updated whenever a payment rail or account feature changes. Each revision is dated, signed...
Every change to these pages carries the date it took effect, so you can see at a glance whether the clause you agreed to has moved since you opened your account.
One desk signs off each page, so there is an accountable owner behind every clause instead of wording nobody stands behind. Write in and you get the reasoning.
We re-check that JazzCash, Easypaisa, SadaPay, NayaPay and Raast stay named correctly wherever these pages describe payment steps, and we correct drift in the next dated revision.
Paragraphs that differ for supported regions are marked individually rather than merged, so you can tell which sentence governs the account you sign in from. Local wording wins where it applies.
We drop dense legal phrasing wherever a normal sentence does the job. If a clause still reads awkwardly to you, tell the desk and we rewrite it for the next dated revision.
Every policy question gets a written answer and we retain what we told you, so a later query can be traced back to the reply you already hold in your own inbox.
Our policy pages share one structure, one set of definitions and the same plain-English tone, so nothing you agree to on one page quietly contradicts another. Where two pages describe the same...
Account conditions, eligibility in supported regions and what happens when you close the account. The same definitions are reused on every other policy page, so wording does not shift between them.
Which details we hold, how long we keep them and who can see them. Rail names appear here spelled exactly as they are on the withdrawal page, with no second set of definitions.
Sign-in protection, device checks and what to do if something looks wrong. The steps described mirror what the account area actually performs, so nothing is promised that the system does not do.
Verification steps, expected timing and the rails involved. Where this page names JazzCash, Easypaisa, SadaPay, NayaPay or Raast, the same spelling runs through the rest of the site.
What has to be true for a running offer to apply and when a round is voided. These clauses use the same wording as the board you see inside your own account.
What is stored on your device and how to switch it off. The choices listed here match the controls in the account area rather than describing a separate arrangement.
How a disagreement is logged, who answers it and how it escalates. The route here follows the same order as the policy desk replies described elsewhere on this page.
Each page opens with a dated header and a short summary box, then the full clause underneath, so you can skim the point before you work through the...