Reference

Privacy Policy for rumah toto Accounts

Our Privacy Policy explains how rumah toto handles the account details you provide, the device signals created when you browse, and records linked to DANA, OVO, GoPay or…

Account dataWallet recordsCookie choicesAccess requests
rumah toto Privacy Policy for rumah toto Accounts
HELP WITH DATA

Where To Ask About Privacy Policy

A clear support route matters when a Privacy Policy question affects your account or wallet record.

Account privacy request Use the account support path to ask which personal data is linked to your rumah toto profile. Include your registered phone detail and a short request, then keep the reply thread so we can confirm what action was taken.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send only the transaction reference and limited account detail needed to locate the entry. We use that route to discuss wallet data without requesting your full payment credentials.
Login access concern If a privacy request follows a login or phone verification problem, tell us the device type, approximate access time and account contact detail. This gives our support path enough context to check the session while limiting unnecessary data sharing.
DATA PRACTICES

How We Handle Your Privacy Policy

We keep this Privacy Policy tied to the actions you take rather than treating every device signal as a permanent profile.

Account details

When you open an account, we use the submitted contact detail and phone verification result to identify your profile and manage account access. We do not need you to place a password, wallet PIN or full payment credential in a privacy request.

Device signals

Your browser, operating system, session time and security signals can be recorded when you move from login to the lobby. On mobile, these checks help us distinguish a new session from an unusual access attempt without reading unrelated files on your device.

Cookie controls

Cookies can remember a session choice, support security checks and help us understand which policy page was opened. You can manage cookies through your browser settings, although blocking required cookies may interrupt login or the account support path.

Wallet references

A DANA, OVO, GoPay or QRIS entry may create a reference, amount, status and time record for account reconciliation. Bank transfer and virtual account records can serve the same purpose. We do not ask for your wallet PIN through support.

Security records

Login events, phone verification changes and Two Factor Setup activity may be retained to protect your account. If you see an access event you do not recognise, contact us through the account support route and avoid sending a password or one-time code.

Retention requests

You can ask how long a particular account, cookie, security or payment reference is kept, and request correction where the record is wrong. We assess removal requests against security, reconciliation and legal needs before confirming the available outcome.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and device questions we expect before you create a profile. They also explain how to contact us about wallet records, cookies, phone verification and access rights. If your case involves a specific transaction, use the private account support route rather than sharing payment details in an open channel.

The rumah toto Privacy Policy covers account details, phone verification, login events, device and browser signals, cookie choices, support messages and payment references. It explains why we use each category, how retention can apply and how you can request access or correction where local law permits.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We may keep a status, time, amount and reference needed to match an account record, but you should never send a wallet PIN or full payment credential to support.

Use the support path available after login and state that you want an account data request under the Privacy Policy. Provide your registered phone detail and the specific category you want checked. We may ask for an account verification step before discussing private records.

You can ask us to correct an eligible error in your account, contact detail, cookie preference or transaction reference. Send the request through the account support route with a clear explanation and supporting reference. We assess the request against security, reconciliation and legal duties.

When you use a mobile browser, we may record device type, browser version, session time and security signals linked to account access. These checks help protect login and phone verification. They are not a request to inspect unrelated files, contacts or wallet PINs on your device.

The period depends on the record and its purpose. Login security, phone verification, payment reconciliation and legal duties can require different retention periods. Ask through support for the category and reason you want checked; we will explain the available retention or removal route.

Yes. You can adjust browser cookie settings and ask support about the cookie choices linked to your session. Required cookies may be needed for login, security checks or the policy access path. Blocking them can affect account access, so change settings before raising a support request.