Reference

Privacy Policy for Your Indonesia Account

Your account privacy covers the same wallet and lobby you use for Live Football Odds, Pyramid Bonanza, Aviator, DANA, OVO, GoPay and QRIS, with access where local law…

Account data useCookie choicesWallet record careSupport privacy route
dewasloto Privacy Policy for Your Indonesia Account
CONTACT ROUTES

How to Reach Our Privacy Desk

Fast privacy contact helps when your phone number changes, a device session looks wrong or a payment receipt needs a data check. Our support desk is available every day from 09:00 to 23:00 WIB through live chat, WhatsApp and email. Tell us your account ID, registered phone, and the last wallet channel used, such as DANA or QRIS; do not send card PINs or app passwords.

Team online

Live chat privacy queue

Use live chat between 09:00 and 23:00 WIB when you need a quick data check. We ask for your account ID and registered phone, then mask wallet references before escalating the case.

WhatsApp account checks

Send WhatsApp when you need to update a phone number, confirm a login alert or ask why a document was requested. We verify identity first and never ask for your wallet app password.

Email privacy requests

Use email for correction, access or deletion requests that need a written trail. Include your username, registered email and a short reason so our team can route the request without extra back-and-forth.

SECURITY PRACTICE

How We Protect Account Data

Privacy is handled at account, wallet and device level, not as a single checkbox. We log the device type, IP range, browser session and wallet reference so we can spot unusual access…

Account setup data

When you open an account, we record your name, phone number, email, username and password hash. We use that record to create access, send security checks and match future privacy requests.

Wallet record handling

For DANA, OVO, GoPay and QRIS, we store transaction ID, amount, time, status and account match result. Support can see the status, while sensitive wallet details are limited by role.

Cookie control path

On mobile Chrome, go to Settings, then Site settings, then Cookies to change browser cookie behavior. If you clear cookies, we may ask for a login code again to protect your account.

Active session checks

Open Account, then Security, then Active Sessions to see recent device access when the tool is available. If a session looks wrong, contact us and we will check IP range and time.

Retention choices

Wallet and login records stay only as long as needed for account security, accounting checks, dispute handling or legal requests. When the reason ends, we queue the record for deletion or masking.

Vendor access rules

Hosting, payment routing and support tools may process limited account data for us. We keep access role-based, record admin activity and remove vendor access when the service is no longer needed.

Privacy Questions Before You Join

Privacy questions usually come before you open an account or when a wallet record needs checking. We answer the points we hear most: what data we collect, why cookies exist, how DANA or QRIS records are stored, and how you can ask for changes. If your question needs a case check, use live chat during 09:00-23:00 WIB and we will move it to the privacy queue.

We collect the data needed to create and protect your account: name, username, password hash, phone number, email, device data and login timestamps. Extra checks may apply where local law permits.

We keep wallet references so deposits, withdrawals, reversals and support checks can be matched to the right account. The record usually includes time, amount, channel, transaction ID and status result.

Yes. Contact live chat, WhatsApp or email with your account ID, registered phone and the field that needs correction. We verify you first so another person cannot change your profile.

Cookies keep your login session, language choice and basic security checks working. You can clear them in your browser settings, but we may ask for fresh verification when you return.

Yes, but only for the task they perform for us, such as payment routing, hosting, fraud checks or support tools. Vendor access is role-based and can be removed when the service ends.

Email our privacy desk with your username, registered phone and request scope. We may ask for extra verification before sending data, especially if wallet records or security logs are included.

Retention depends on the record type. Security logs, wallet references and support cases are kept while needed for account protection, accounting checks, disputes or legal requests, then deleted or masked.