Reference

rimbaslot Privacy Policy For Indonesian Accounts

Our Privacy Policy explains how rimbaslot handles the details connected to your account, from phone verification to wallet records for DANA, OVO, GoPay and QRIS.

Account dataCookie choicesWallet recordsAccess requests
rimbaslot rimbaslot Privacy Policy For Indonesian Accounts
CONTACT ROUTES

Ask About Your Privacy Policy

A clear contact route lets you ask what data we hold, why a record appears, or how to request a correction.

Account data request Ask us to locate your account records by giving the verified phone number and…
Cookie question Tell us which device and browser showed a cookie prompt or stored a preference.
Payment record check For a DANA, OVO, GoPay or QRIS record, provide the date and reference visible…
HANDLING DETAILS

How We Apply This Privacy Policy

We apply this policy through practical account and support controls rather than broad promises. Phone verification connects a request to the right profile, device and sign-in records help us examine access events…

Data we collect

We may receive your phone number, account settings, sign-in events, device markers, support messages and payment references. We collect these details when they are needed to provide account access or answer a specific request.

Cookie controls

Cookies can retain a browser choice and help connect a policy visit with basic page operation. You can manage browser storage through your device settings, although removing cookies may clear saved preferences.

Account protection

Phone verification is used before account access and may be repeated for a personal-data request. Never place a password, wallet PIN or one-time code inside a support message.

Retention approach

We keep account, support and payment references only while they serve access, dispute, safety or legal needs. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Request a change

You can ask us to correct an account detail, explain its use, or request removal where permitted. Include the verified phone number and describe the exact record so we can avoid changing the wrong profile.

Privacy contact

Use the account support path for privacy questions, including cookie choices and wallet records. We may verify your identity before replying, so personal account details are not disclosed to another person.

Privacy Policy Answers Before Account Access

These answers focus on the questions you may have before opening an account or asking us to change a record. They explain how the Privacy Policy relates to phone verification, cookies, local wallets and access requests, while the full policy above remains the reference for your account.

It covers account details, phone verification, sign-in and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the phone number to create and identify your account, complete the account access step and match a privacy request to the correct profile. We do not need your wallet PIN.

Yes. The Privacy Policy covers references needed to match DANA, OVO, GoPay and QRIS activity to an account, such as a receipt date or transaction reference, not your private wallet password.

Cookies may remember browser choices and support basic page operation. You can manage them through your mobile or desktop browser settings, but clearing storage can remove saved preferences.

You can request a correction through account support by naming the exact detail and providing the verified phone number. We may confirm account access before changing personal records.

We retain account, support and payment references for access, dispute, safety or legal needs. When those needs end, we remove the record or separate it from direct identifiers.

You may ask for removal where local law permits. Some records may need to remain for a dispute, account-safety check or legal requirement, and we will explain the reason through support.