Reference

Open rajaslot Privacy Policy before account access

Our Privacy Policy shows how rajaslot handles the details connected with your account, mobile browser, wallet activity and support requests.

Account dataCookie choicesWallet recordsRequest changes
rajaslot Open rajaslot Privacy Policy before account access
REQUEST ROUTES

Contact us about your Privacy Policy request

A clear request path helps you ask what we hold, why it is used, or how a record can be corrected. Sign in first when possible, then use the account support route shown beside the cashier area so we can connect the request with the right account. If login stalls, include the phone number on the account and the relevant wallet reference without sending a password.

Team online

Account access

Use the support route after login to ask for a copy of account details held under your Privacy Policy record. We may ask for phone verification before discussing private account data.

Wallet reference

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date, not your wallet PIN. We use those details to trace a status while limiting unnecessary payment data.

Policy changes

Ask us to correct an outdated phone detail, explain a cookie choice or review a retention question through the account support path. Keep your request specific so we can respond accurately.

ACCOUNT SAFETY

Protect your account data across each device

We keep this policy practical by linking each data practice to an account action you recognise.

Data we receive

We may receive your phone details, account entries, login events, device signals, support messages and payment references. The Privacy Policy explains how each category relates to access, account checks or service requests.

Cookies on mobile

Cookies can remember session choices and help connect a mobile browser with your account visit. You can ask us about cookie use through support, especially when changing device or clearing browser data.

Phone verification

Before account access, we use the phone verification step to confirm that a request belongs to you. Do not send a password or wallet PIN when asking us to check identity.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help match a payment event. Our handling does not require you to provide a wallet PIN in a support message.

Retention questions

We retain selected account, security and payment records only for stated operational, dispute or legal needs. Ask support which category applies to your request and whether correction or removal is available.

Change requests

You can ask us to correct account details, explain a data use or address a cookie preference. Include your account phone and a precise request so we can locate the relevant record.

Find Privacy Policy answers before opening an account

These Privacy Policy answers focus on the questions you may have before sharing account details with us. They cover phone verification, mobile browsing, local wallet references, correction requests and access conditions. If your situation is different, use the support route after login and describe the exact record or event you want us to check.

The Privacy Policy covers account details, phone verification, login events, device and cookie signals, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm that the person requesting account access or data assistance is connected with the account. It also helps us avoid discussing private details with an unknown requester.

Yes. The Privacy Policy covers device and cookie signals created when you use a mobile browser for login or account access. You can ask support about a cookie choice or related record.

We may keep references needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with an account. Do not send a wallet PIN or password in any request.

Use the account support route and identify the detail you want changed, such as an outdated phone number. We may request phone verification before confirming or applying a correction.

Retention depends on the record and its operational, security, dispute or legal purpose. Ask support about the category involved; we will explain whether correction or removal can be considered.

You can open this Privacy Policy from Indonesia, while account access and eligibility depends on local law. Where local law permits, the policy and request path remain available through your account.