Privacy policy
Sets out what we collect from your account, how payment references from JazzCash, Easypaisa, SadaPay and Raast are treated, and the choices you can exercise over your own records.
This page sets out how romeo slot collects, uses and protects the details tied to your account. You will see what we gather when you register, how payment...
We apply this policy to every account opened through romeo slot, and we treat the rules of your own jurisdiction as the starting point. Where local law permits online gaming, we hold your details under the terms described here; in supported regions outside that scope we may limit registration rather than bend those rules. Payment references from JazzCash, Easypaisa, SadaPay, NayaPay and
Raast are matched to your profile for verification, then kept in an encrypted store with access limited to staff who need it. Ask us to correct, export or erase a record and we act within the timeframe your local rules set. If a legal duty obliges us to keep something longer, we say so in our reply rather than leaving the file
in place silently.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We would rather show you the machinery than ask for blind faith. Staff who can open an account record work from logged sessions, so each lookup leaves a trace, and our security...
One manager holds this policy, answers for its wording and signs off each revision, so you clearly know which team stands behind the terms you are reading today.
Every internal lookup of a customer record is stamped against the staff account that opened it, so we can trace misuse and tell you who has seen your file.
JazzCash, Easypaisa, SadaPay and Raast references are matched to your profile for verification, then stored in a restricted table that only settlement and compliance staff may query.
We set a retention window for each record type and delete what has passed its date on a rolling schedule, rather than letting old files sit on the system.
When the wording changes we keep the previous version reachable and mark the sections that moved, so you can see at a glance what shifted without rereading every paragraph.
We hold account data to the standard your own jurisdiction sets, and where local law permits we add the extra safeguards our security team judges necessary for Pakistan-based accounts.
Our policy pages share one vocabulary, so you are never left guessing which document means what. Where this page says personal data, the terms page uses the same phrase and points to...
Sets out what we collect from your account, how payment references from JazzCash, Easypaisa, SadaPay and Raast are treated, and the choices you can exercise over your own records.
Defines the account rules, eligibility in supported regions and the conduct we expect, and uses the same binding definition of personal data that appears throughout this page.
Explains the small files our lobby sets on your device, which of them keep your session open and which measure traffic, and how you can switch them off.
Lists the rails we accept and the settlement timing for each, and points back here for how long a transaction reference is retained after the transfer clears.
Covers sign-in checks, session timeouts and the steps we take if we detect unusual access, all of which feed the breach wording in this policy and our notice to you.
Carries the same support hours and escalation path listed on the privacy page, so a data complaint reaches the same team whether you start there or here.
Keeps dated copies of each policy version, so if you want to compare what applied when you registered with what applies now, the difference is always clearly visible.
We lay this policy out so you can reach the part you need without reading from the first line. A summary bar sits under the headline, a jump...