Terms of use
Terms of use defines the account relationship and takes precedence over this page. Both carry matching clause numbers, so a support reply points to the same text wherever you read it.
These are the terms sitting behind your romi slots account: how we hold it, what you accepted when you opened it, and where Pakistani law fits in. Read...
Our legal position is straightforward. We serve accounts in regions where local law permits, and we do not open accounts where that permission does not exist. Registering from Pakistan means the details you give us are yours, the rail you name is yours, and you meet the age rules that apply where you live. Each clause is written to be read, so
we define a term the first time it appears. Where a rule depends on your province, your rail or your device, we say so plainly instead of burying it in a schedule. JazzCash, Easypaisa, SadaPay and Raast settlements each carry their own timing and verification steps, and those steps form part of what you accept. When wording changes we date it and
leave the earlier version linked, so you can compare what applied when you opened the account with what applies now.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Ask us directly and you reach a person rather than a form letter. Our support desk answers account and policy questions in English during Karachi hours, and each written reply quotes the clause it came from, so you can follow the reasoning yourself. Bring your registered email and the settlement reference if your question concerns a transfer.
Chat stays open through the day for account access, locked logins and urgent settlement queries. An agent pulls your account record while you wait, so most policy questions are settled in the first session.
Write to our policy mailbox with your registered email and the clause you are asking about. We reply in writing within one working day, and the reply stays on your account record for reference.
If a written answer does not settle your point, ask for it to be passed to our compliance team. They check the clause, the record and the settlement trail, then send a final position in writing.
We write these pages in house, from the same desk that handles accounts, so the wording reflects the rules our team applies every day. Nothing is borrowed from another operator, and we...
Every clause on this page is drafted by our own policy team in Karachi for you. No agency copy, no borrowed templates, and no wording carried across from another operator's public pages.
We re-read each clause every quarter against the way our support desk and settlement teams actually work. Where day-to-day practice has moved, the wording moves with it.
Every change carries a date and a short line on what moved. Older wording stays linked for twelve months, so you can compare what applied when you opened your account.
One named policy owner signs off each version. If you ask who approved a clause, support tells you the team and the date it took effect.
We define each term the first time it appears and avoid chains of cross-references. Long clauses get split rather than stretched, which keeps the reading short for you.
We publish only what we can point to in your account: settlement timing, support hours, verification steps and regional rules. No awards, no player totals, no figures we cannot demonstrate.
This page sits with our other policy pages, and they share one template: the same headings, the same definitions and the same contact routes. So a settlement window means the same thing...
Terms of use defines the account relationship and takes precedence over this page. Both carry matching clause numbers, so a support reply points to the same text wherever you read it.
Privacy repeats the same definitions of personal data and retention periods. The wording mirrors this page paragraph for paragraph, so reading one tells you how the other behaves.
Account access repeats the login, device and verification wording you see here. Nothing on that page narrows what this page allows you to do, and nothing here widens it.
Settlement rules carry identical JazzCash, Easypaisa, SadaPay and Raast timing tables. If a rail changes its window, both pages are updated in the same release on the same day.
Security practices list the same two-step login and session timeout wording. Any hardening step we add is dated on both pages together, so the versions never drift apart.
Complaints sets out the escalation ladder and quotes the response times printed on this page. It cannot promise less than what we say here, only the same or quicker.
Contact routes come from one shared list, so chat and email details match everywhere on the site. If a channel closes, it disappears from both pages at once.
Before you open an account, the legal pages show you the shape of our policy set: a dated version line, a short summary of each clause...
A dated line at the head of the page tells you when this wording took effect, so you always know which version you are reading and agreeing to.
Each clause opens with a two-line summary in plain English, with the full legal wording underneath. Read the summary first, then go deeper only where you need to.
Numbered headings link straight to the clause they describe. Support replies quote those numbers, so you can find the exact text being referred to in one click.
Chat, email and escalation details sit together near the foot of the page, with our Karachi hours printed beside them, so help is never more than a scroll away.
A short notice states that access is available where local law permits and names the regions we serve. If your region is not listed, the lobby will not open for you.
Older versions stay linked from the page, each one dated with the day it was replaced. You can read back through that trail and check what changed while your account has been open.