Reference

Privacy Policy for dumaitoto Accounts

dumaitoto Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesCookie choicesWallet checksAccount requests
Browse Our Lobby Read FAQ
dumaitoto Privacy Policy for dumaitoto Accounts
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path helps when a Privacy Policy question concerns your own account rather than a general page.

Account data request Use the support route beside your account when you want to ask what personal details we hold or why a phone verification step appears. Include your registered contact detail so we can match the request safely, and never place your password, PIN or one-time code in the message.
Correction request If your name, phone detail or account contact is inaccurate, tell us which field needs correction and why. We may ask for an account step that confirms ownership before changing it, especially when the record is connected to a bank transfer, virtual account or wallet status.
Privacy access route For questions about cookies, device records or retained payment entries, contact us through the account support path and identify the page or action involved. A screenshot can help us trace a login or QRIS status issue, but remove wallet balances, codes and unrelated personal details first.
DATA CONTROLS

What We Do With Your Data

The Privacy Policy is designed around the moments that matter to your account: opening access, signing in, checking a wallet status and asking for help.

Account creation

We use the contact details and verification results you submit to create and protect your account. A clear account path helps prevent records being attached to the wrong person. If a required field changes, the Privacy Policy gives you a route to ask for correction after ownership checks.

Device and login signals

When you move between a mobile browser and desktop, we may record device type, session activity and security events connected to sign-in. These signals help us identify unusual access and investigate a stalled login. They do not replace the account details needed for a direct privacy request.

Cookies on pages

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage browser cookie controls, although refusing some cookies may affect sign-in or the handoff from account access to the lobby. The Privacy Policy explains this trade-off.

Wallet references

A DANA, OVO, GoPay or QRIS action may leave a payment reference, amount status and time record in the account history. We use those details to reconcile the requested action and answer support questions. We do not ask you to disclose a wallet PIN or one-time code.

Security controls

We limit sensitive account changes to authenticated support or account steps and may request phone verification before access or correction. Keep your password and verification codes private. If you notice an unfamiliar login, contact us through the account route and describe the date, device and action you recognise.

Retention and requests

We keep personal records only while they serve account operation, dispute handling, security work or a legal requirement where local law permits. You can ask about access, correction or deletion through support. We may retain a limited record when a continuing legal or security reason requires it.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain the data linked to access, device use and local wallet activity without asking you to guess which team handles a request. If your situation involves a specific account, use the support path and include only the details needed to locate it. Availability depends on local law.

The dumaitoto Privacy Policy covers personal details submitted for account creation, phone verification, sign-in activity, cookies, device signals and payment references. It also explains how we use records for account operation, security, support and legal duties where local law permits, including requests to access or correct details.

Phone verification helps us confirm that the person requesting account access or a data change controls the registered contact detail. It can protect your account when a device changes or a correction involves wallet activity. Never send us the verification code itself through support.

Yes. The Privacy Policy covers the account-side reference for a DANA, OVO, GoPay or QRIS action, such as its selected rail, status and time. We use that record to reconcile the requested activity and answer a support question, while your wallet PIN remains private.

Use the support path connected to your account and ask for an account data access request. Include the registered phone or email detail and describe the records you want to understand. We may complete an ownership check before responding, and the response path depends on local law.

You can ask us to correct an inaccurate name, phone detail or account contact through support. State the field that needs changing and provide the account detail used for matching. We may request phone verification or another account step before applying a change to protect your record.

Cookies may keep your session active, remember settings and show whether a page loads correctly. Your browser can restrict or remove them, but some cookie choices may interrupt sign-in or the move from account access to the lobby. Our Privacy Policy explains which functions can be affected.

We retain records for the time needed for account operation, payment reconciliation, security checks, support disputes or a legal requirement where local law permits. The period can differ by record type. Ask through support if you want a retention explanation or want to request deletion of eligible details.

Related Pages

dumaitoto Indonesia About Us FAQ Access guide Live Baccarat Salon