Reference

Privacy For Your Wallet And Lobby

Our Privacy Policy explains how rumah123 handles the account details, device signals and payment status you share when you open an account or browse titles such as Sic…

Account dataWallet recordsDevice choicesPolicy requests
rumah123 Privacy For Your Wallet And Lobby
CONTACT ROUTES

Questions About Account Data

If a Privacy Policy question affects your login or wallet status, start from the support route shown beside your account and cashier area. We ask you to include the account contact detail already attached to your profile, rather than sending a wallet password or full payment credential. A clear request helps us locate the relevant record, explain why it was collected and confirm whether a correction, copy or deletion request can proceed.

Team online

Account data request

Use the account help route to ask what personal data we hold, why it is connected to your profile and which parts can be corrected. We may ask you to complete phone verification before discussing account-specific details, so another person cannot request your records.

Wallet record question

For a DANA, OVO, GoPay or QRIS status question, share the date, amount reference and account contact detail shown in your payment record. We use those details to trace the relevant entry without asking you to disclose a wallet password or private security code.

Privacy request path

When you want to correct, export or remove personal data, send the request through the listed support contact from your signed-in account. We may need identity checks, and we will explain any record that must remain for account security, dispute handling or a legal obligation.

DATA PRACTICES

Security Around Sic Bo Sessions

Our handling of Privacy Policy matters is tied to practical account behaviour, not just a page of definitions.

Data collection

We collect details you enter during account creation, plus sign-in events, phone verification status and payment references from routes such…

Cookie choices

Cookies or similar browser storage can keep your sign-in state, language selection and privacy choices available on the same device.

Account protection

Phone verification is required before account access can be completed in the stated flow.

Retention period

We keep account, support and transaction references for the period needed to maintain account security, resolve a payment question and…

Correction requests

If your name, contact detail or other account entry is inaccurate, ask us to correct it through the signed-in support…

Device access

The mobile browser path can store a session token and device preference so you can return to the lobby without…

Privacy Policy Questions For rumah123

These Privacy Policy answers address the account, device and payment questions you are most likely to have before opening an account. They also explain the practical steps for requesting a copy, correction or deletion, including cases where a record may need to remain for security or legal reasons.

The rumah123 Privacy Policy covers data from account creation, phone verification, sign-in, device sessions, support requests and payment references. It explains how we use those details for account access, wallet matching, security, retention and requests to correct, copy or remove personal data.

Yes. The Privacy Policy covers payment status and reference details connected with DANA, OVO, GoPay and QRIS. It also covers bank transfer and virtual account references used to match a payment record with your account. We do not need your wallet password to check status.

Phone verification helps connect account access with the contact detail you supplied and reduces the chance of another person entering your profile. It can also be required before we discuss account-specific data or complete a request to change personal details.

We may record device type, browser session signals, sign-in events and approximate network data. These details help maintain a mobile session, remember privacy choices and identify unusual access. They are handled for the stated account and security purposes rather than as a substitute for your identity.

Use the support contact shown from your signed-in account and clearly ask for a copy of your personal data. Include the account contact detail used during registration. We may complete a phone verification check before releasing account-specific records to you.

You can request a correction or deletion through the account support path. Tell us which record is affected and why. We will assess the request under applicable requirements; some account, payment or security records may need to remain for legal or dispute purposes.

Yes. Access and eligibility depend on local law. Our Privacy Policy still explains the data practices for a supported account flow, but you should check whether access is available where you are located. We may restrict account actions where local requirements call for it.