Terms of Service
Our terms reference the same data categories you'll read here, so the two documents never contradict on retention or sharing.
LEGAL REFERENCE
Our Privacy Policy, Written Plainly
This is the ratucasino77 privacy page. We tell you what account data we collect when you open a lobby session, why we hold it, and how long it...
Account dataCookie useYour rightsContact deskLast updated
How We Handle Your Account Data
We collect only what your account needs to run: your sign-in details, device fingerprint, deposit and withdrawal references, and the lobby activity tied to your session. Where local law permits, we retain these records for the period our licensing obligations require, then we remove them. Your payment identifiers — whether DANA, OVO, GoPay or QRIS — are tokenised at the gateway, so
we never store the raw wallet credentials on our servers. You can ask us at any time to export your record, correct an entry, or close the account and trigger deletion within the supported regions we operate in. We share data only with the processors that keep the lobby running, and never sell it onward.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PLATFORM TRUST SIGNALS
How We Keep This Policy Honest
Reviewed Quarterly
Our compliance team reads the full policy every quarter and re-dates the document when wording shifts. You'll see the revision stamp at the foot of this page so changes are never quiet.
Licensed Operator
We run under a gaming licence that audits our data handling. The auditor reviews retention schedules, breach logs and processor contracts, and we keep the certificate referenced inside our footer for you to check.
Named Data Officer
A named privacy officer signs off on every change to this page. The role isn't outsourced — it sits inside the same team that builds the lobby you use.
Processor Register
Every third party that touches your data — payment gateway, KYC checker, hosting partner — is listed on our register. We update the list before adding a new processor, not after.
Breach Protocol
If a data incident affects your account, we notify you inside the window our regulator sets and explain what was exposed, what we did, and what you should do next.
Plain-Language Drafting
We write this policy ourselves, in the same English you read across the lobby. No template clauses copied in from another jurisdiction, no legalese hiding what actually happens to your record.
BENCHMARKED
Consistency Across Our Policy Pages
Cookie Notice
The cookie page expands on the tracking summary in this policy and lists each cookie by name, purpose and lifetime.
KYC Policy
Identity-verification rules sit on a sibling page; this policy explains what we keep, that one explains what we ask for at signup.
AML Statement
Our anti-money-laundering page describes the checks behind deposit reviews and links back here for the retention timelines.
Account Closure
The closure page mirrors the deletion clause in this policy so the exit flow matches what we've promised about your data.
Marketing Preferences
Opt-in and opt-out controls live on the preferences page, and this policy points to it whenever consent is mentioned.
Complaints Route
The complaints page lists the regulator path; this policy names the same body so escalation is consistent wherever you start.
SERVICE CONTEXT
What This Policy Page Includes
Revision Date
The footer of this page carries the date we last...
Section Anchors
Each clause has its own anchor link so you can...
Plain Summary Box
Above each long clause we drop a one-line summary so...
Request Form Link
A button inside the rights section opens our data-request form...
Change Log
At the foot of the page we list what changed...
Contact Block
Our privacy desk address, postal route and chat queue all...
Privacy Policy Questions
We hold your sign-in credentials, verification documents, deposit and withdrawal references, lobby session logs and the device fingerprint of the browser you sign in from. Nothing outside that scope is collected by us.
No. DANA, OVO, GoPay and QRIS credentials stay with the payment gateway. We receive a tokenised reference that lets us match the transaction to your account, never the wallet password or PIN.
Retention follows our licence conditions. Active accounts keep records for the session lifetime; closed accounts hold a minimum regulatory window, after which the personal fields are deleted from our production systems and backups age out.
Yes. Send a deletion request to the privacy desk and we'll action it inside the window our regulator sets, subject to the records we're legally required to keep for anti-fraud and accounting purposes in supported regions.
Only the processors that keep the lobby running — payment gateways, identity-verification partners and our hosting provider. Every one of them sits on the processor register linked from this page, and we never sell data onward.
We update the revision date at the foot of this page and post the diff in the change log. For material changes that affect your rights, we email the address on your account before the new wording takes effect.
Contact our privacy desk first so we can resolve it directly. If you're not satisfied, the complaints page lists the regulator you can escalate to, and we'll cooperate fully with any review they open.