Reference

Open the Privacy Policy

We explain what personal data we collect, why we keep it, and how you can ask for changes through your account.

Account dataCookiesLocal lawRequest changes
ronaldo4d Open the Privacy Policy
CONTACT ROUTES

Switch to ronaldo4d Privacy Support

When you want to check this policy, we keep the route simple: use live chat, send email from the address on file, or open Account > Privacy in the lobby.

Live chat Send a privacy request in live chat from 09:00-22:00 WIB. We confirm the account holder first, then we help with copies, corrections, or closure steps from the same thread.
Email Email us from the address on file if you want the request in writing. We use the subject line 'privacy request', check the match, and reply with the next step for your record.
Account menu Open Account > Privacy if you want to manage your record yourself. The same route works on Android and iPhone, and you can add a screenshot so we can check the exact screen.
ACCOUNT SAFEGUARDS

Browse Our Data Safeguards

We handle privacy with account controls, not vague promises. Your login is protected by password checks and session expiry on shared devices, while cookies remember language and return visits on Android Chrome…

Collected data

We collect only the details needed to run your account: name, email, device type, login time, payment reference, and support history. When you open slots, live casino tables, or crash games, the session record stays linked to your account.

Cookies

Cookies remember your language, session, and device choice on Android Chrome and iPhone Safari. They help the page stay signed in, and you can clear them in the browser if you want a fresh start.

Account protection

Passwords, fresh login checks on sensitive actions, and short session timeouts help keep account access under control on shared phones. If you switch devices, we ask you to log in again before showing any private records.

Retention

We keep chat logs, payment references, and account changes only as long as we need them for service, dispute handling, or legal retention duties. After that period, the record is removed or anonymised through our process.

Request handling

For a copy, correction, or deletion request, use Account > Privacy, live chat, or email from the address on file. We verify the account holder first, then we apply the change or explain the part we cannot change.

Legal scope

Access and service depend on local law and are available only where local law permits. If a rule limits a request, we tell you what remains possible and keep the rest of the thread open.

Open Answers About Privacy

These are the questions we get when you want to check records, request changes, or confirm how your account data is handled. Each answer points you to the same verified contact route, and our team will only act after the account match is complete. Local access rules still apply, so the final step depends on the law that covers your region.

We keep the details you submit, login timestamps, device type, and support chat history. If you use DANA, OVO, GoPay, or QRIS, we also keep the payment reference so we can match it to your account.

We store the reference, status, and time of each payment, not the full wallet secret or card data. That lets us confirm DANA, OVO, GoPay, or QRIS activity against your account without keeping more than we need.

Yes. Open Account > Privacy or contact us through live chat or email from the address on file. We verify the request against the account holder, then we send a copy or update the record where law allows.

We keep records only for the period needed to run the account, settle a request, handle disputes, or meet legal retention duties. After that period, we remove or anonymise the record through our retention process.

Yes. It covers Android and iPhone browsers, including Chrome and Safari, plus the session logs created when you open slots, live casino tables, or crash games from the same account.

Only staff who need the record for support, account checks, or legal duties can see it. We limit access by role, and any request from a new device needs a fresh verification step before we continue.

If a request conflicts with local law, we explain the part we cannot carry out and keep the rest of the request open where possible. Access and service are available only where local law permits.