Account terms
The clauses here match the account rules you accept at registration, so a paragraph never reads differently depending on which page you landed on first.
LEGAL REFERENCE
The rules that sit behind your account
These are the terms behind your rainbet app account: what we ask of you, what you can expect from us, and how a clause is applied when your...
Account termsRegion rulesPayment clausesFair use
Terms that apply where local law permits
rainbet app publishes this page so you know where you stand before you move money or open a table. It covers registration, identity checks, the rails you already use, and what happens when a transaction needs a second look. JazzCash, Easypaisa, SadaPay and Raast are named directly, not hidden behind provider labels. Access is offered only where local law permits, and the
rules that bind you are tied to the region you registered from. Where a clause depends on jurisdiction, we say so in the sentence itself rather than burying it. When a rule changes, we update the wording and mark the revision date beside the heading, so you can compare what you agreed to with what now applies to you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY STANDARD
How we draft and keep these terms current
We draft these clauses ourselves, in the order a reader meets them, and we keep the language close to the way we answer account holders on chat. Where...
Plain Pakistani English
We write in clear Pakistani English you can read once and follow, skipping the legal filler that hides what a...
Region tags
Any clause that shifts with jurisdiction carries a tag naming the rule that applies to your registered region, so you...
Revision trail
Each version shows the date we last edited it and a one-line summary of what moved, so you can set...
Named rails
Where a paragraph touches money, we name the rail outright, whether that is JazzCash, Easypaisa, SadaPay, Raast or a bank...
Account security
We set out the login checks, device verification and password expectations we apply, and what we ask you to do...
Record requests
You can ask for the terms version tied to your registration date at any point while your account is open...
MATCHING WORDING
One voice across every policy page
Read this page beside our privacy, cookie and complaint wording and you will notice the same definitions and the same rail names in each. That is deliberate. A term means one thing...
Privacy wording
Where our privacy page describes how we handle your details, this page reuses the same definitions and rail names rather than inventing fresh labels for the same thing.
Cookie wording
Device and session terms are written to line up with the cookie language used across the site, so consent wording and security wording describe the same behaviour.
Payment clauses
Money paragraphs name the same rails everywhere, listing JazzCash, Easypaisa, SadaPay, Raast and bank transfer, so you never meet two names for one route on the whole site.
Closing an account
The steps for closing your account are phrased the same way wherever they appear, and they point back to the support channels listed further up this page.
Complaint steps
Escalation wording follows one order of steps across the site: chat first, a written request second, and a formal reply tied to your account reference after that.
Revision dates
Every policy page carries its own revision date, and we change them during the same editing pass, so the dates rarely sit far apart from one another.
What sits inside this legal page
This page is built so you can find a single clause without reading all of it. Summaries sit beside the full wording, region tags sit next...
Clause summaries
Each long clause opens with a short summary in plain language, so you get the gist before you commit to reading the full paragraph and its region tag.
Region tags
Tags sit beside the sentences they change, telling you which rule applies to the region your account is registered in and which lines do not reach you.
Rail references
JazzCash, Easypaisa, SadaPay, Raast and bank transfer appear by name wherever a clause touches timing or confirmation, so you can see the exact route at issue.
Revision trail
A dated list near the heading shows what changed and when, letting you set the version you accepted beside the version now sitting in front of you.
Contact routes
Chat, email and written clause requests are listed with their hours, so you know which channel gets a fast reply and which one leaves you with a record.
Your side of it
One short block sets out what we ask of you: accurate registration details, one account per person, a password you keep to yourself, and what happens if access is shared.
What you ask about our terms
The version tied to the region you registered from and the date you accepted it. If a rule changes, the update applies from its revision date onward, not backwards.
In places, yes. Clauses that depend on local rules carry a region tag, and access itself is offered only where local law permits, so some paragraphs may not apply to you.
JazzCash, Easypaisa, SadaPay, Raast and bank transfer are named wherever a clause touches timing or confirmation, so you can match a rule to the route you used.
Start a chat or send an email from your account and quote the clause heading. We reply in writing, usually within two working days, with the same meaning in shorter sentences.
The wording shown when you confirmed the transaction takes priority, because that is the version you accepted at the time. We flag any gap if you ask us to check it.
Yes. Request the version tied to your registration date and we will send it while your account stays open, along with a short summary of anything edited after that date.