Reference

Privacy Policy For Your radian88 Account

radian88 Privacy Policy explains how we handle the account, device and wallet details connected with Live Blackjack Prestige, Toraja Gold Slots and your login path.

Account clarityWallet dataDevice controlsAccess requests
radian88 Privacy Policy For Your radian88 Account
CONTACT ROUTES

Privacy Questions Near Your Account

A clear contact path helps when you want to ask about a record, correct a detail or understand why a verification step appears. Start from the support route linked to your account and include the email or phone detail connected with your access. We use that match to avoid discussing account data with the wrong person. You can also mention a DANA or QRIS reference when your request concerns a wallet status.

Team online

Account privacy request

Use the account support route to ask what personal details we hold, why they are used or which processing activity relates to your access. Include your registered phone detail so we can locate the correct account without asking for your wallet password.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate date shown in your account. We can check the status record connected to your account while keeping the wallet credentials themselves outside our support conversation.

Access correction

If your phone detail, device record or account name needs correction, tell us which field is inaccurate through the available support route. We may ask for an account step to confirm ownership before changing personal data or restoring access.

DATA HANDLING

What Our Privacy Process Covers

We keep the Privacy Policy practical by connecting each data choice to an account action you can recognise.

Account details

We use the details entered during account creation and phone verification to identify your account, provide requested access and respond to account questions. If a field changes, contact us through the account route so we can compare the request with the existing record.

Device records

Browser and device signals can help us recognise a returning session, detect unusual login activity and keep the account path consistent on mobile. We do not treat a device record as a replacement for your account details or phone verification.

Cookies

Cookies and similar storage can remember session choices, preserve sign-in flow and show the correct account state after you move between the lobby and payment screen. You can manage browser storage through your device settings, though some account steps may then need repeating.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the reference and status needed to match a transaction with your account. We do not ask for your wallet PIN or banking password in a support request.

Retention steps

We keep personal records only while they support account access, payment reconciliation, security checks, dispute handling or a legal duty. When a retention period ends, records are deleted, anonymised or separated from active account access where our process allows.

Change requests

You can ask us to access, correct or clarify personal data through the support route connected with your account. We may verify ownership before responding, and where local law permits, we will explain any reason a requested change cannot be completed.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account actions most likely to raise a question before you open access. We cover the data connected with login, mobile use, local wallets, payment references and correction requests. If your situation is not listed, use the support route connected with your radian88 account and describe the specific record you want us to check.

It covers account details, phone verification, device and browser records, cookies, support cases and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, correction requests and the limits that depend on local law.

Phone verification helps connect an access request with the correct account and reduces the chance of an unknown person changing account data. We use the verification result for account access and security checks, not as permission to request your wallet PIN or banking password.

Yes. The policy covers browser and device signals used to maintain a session, recognise unusual login activity and keep your account state after moving between the lobby and a QRIS payment screen. Device settings can clear stored session data and may require you to repeat login steps.

We may store the payment reference, selected rail, amount status and timing needed to match activity with your account and resolve a support request. We do not need your wallet PIN. The same approach applies to OVO, GoPay, bank transfer and virtual account records.

Yes. Send a correction request through the account support route and identify the field that is inaccurate. We may ask for phone verification or another account step before making a change. Where local law permits, we will explain the result and any reason for refusal.

Retention depends on the record and its purpose. We may keep data while it supports account access, payment matching, security checks, disputes or a legal duty. When the relevant period ends, we delete, anonymise or separate the record from active access where our process allows.

Yes. Privacy rights, account access and the response available for a data request depend on local law. Where local law permits, we will help you access or correct relevant records. We may still need to verify account ownership before discussing personal data.