Terms Of Use
The clause numbers you see here continue onto the terms page, so a cross-reference lands on the same definition rather than a second, differently worded version.
Everything that governs your account at 91club sits on this page in plain English: the terms you accept, how a dispute is handled, and which rules apply where...
Access to 91club depends on where you are. We open accounts across supported regions of Pakistan, and we ask you to check that betting and casino play is allowed where you live before you join. Where local law permits, your account, wallet and play history sit under the terms on this page; where it does not, we may limit or close access.
If a channel such as JazzCash, Easypaisa, SadaPay or Raast is unavailable to you, it simply will not appear in your cashier, and your terms stay unchanged. One account policy applies across the platform, and we check it when you sign up. How we handle your data sits on the privacy page, which this policy cross-references.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy questions are not something you should have to dig for. Write to our policy desk from the email address on your account and we will reply in the same thread, so your history stays together. Chat handles quick questions; WhatsApp suits Pakistani numbers. Urdu or English, whichever you prefer.
Send your terms question to our policy desk with your account number in the subject line. We answer within one working day and the reply stays in your inbox.
Open chat from the help button on any page. Our team can walk you through a clause, check what your region allows, or point you to the right section of this page.
Pakistani numbers can message our WhatsApp line for written answers about account rules. Keep screenshots of anything you were shown and we will compare them with the terms here.
We write these policy pages ourselves, in the same voice as the rest of 91club, and we keep a dated change log so you can see what moved...
Every clause edit carries a date and a short line explaining what changed. You can read the log in order...
The writers of this page also answer your emails, so a question about a clause reaches a writer who can...
Clauses are drafted in English and kept short enough to read on a phone. Where a term is unclear, our...
Policy email, chat and WhatsApp all reach the same desk and every reply is signed by a person. Keep the...
Before we open an account we confirm your region, the payment rails available to you and whether play is allowed...
When you tell us a paragraph reads badly we redraft it rather than leave it. Several clauses here have been...
Terms, privacy, security and region access are written as one family, so a word means the same thing wherever you meet it. Where this page needs a fee example or a dispute...
The clause numbers you see here continue onto the terms page, so a cross-reference lands on the same definition rather than a second, differently worded version.
How we store your documents, what survives an account closure and who may open a file follow the privacy page exactly, with no quieter rules tucked in here.
Sign-in rules, device checks and the steps for reporting a lost phone are mirrored from the security page, so you follow one procedure instead of two slightly different ones.
The supported-regions wording is reused word for word, which is why the same limits appear here and on the access page whenever local law changes in your area.
Clearing times for JazzCash, Easypaisa and Raast follow the payments page, and any revision is dated in both places on the same day so nothing drifts apart.
Where we offer a clause in Urdu, the English wording on this page stays the reference copy, and any disagreement is settled by reading the two side by side.
Both pages carry the same revision dates, so you never find the terms updated in one place and left stale in another when you check them together.
This page is built as blocks you can scan: a short opening, the jurisdiction wording, the change log and the contact paths. Each block reuses the same heading...