Reference

dewaslot Privacy Policy for Your Account

dewaslot Privacy Policy sets out how we collect, use and protect the details connected with your account, mobile browser and wallet activity.

Account dataWallet recordsDevice choicesPolicy requests
dewaslot dewaslot Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path matters when you want to ask about personal data, a phone verification record or a wallet reference.

Account data request Use account help to ask what personal details are connected with your dewaslot profile. We may ask for phone verification so we can match the request to the right account.
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, use the cashier-help path. Share the transaction reference, never your wallet password or security code.
Correction request If your account detail is outdated, send a correction request through the policy contact route. We check the account record first, then explain which fields can be changed.
HANDLING YOUR DATA

What We Do With Account Details

Our privacy process follows the account steps you can see: phone verification before entry, wallet reference matching during payment checks, and session controls across mobile and desktop.

Account data

We use your submitted account details to create access, respond to policy requests and connect phone verification with the correct profile. We do not ask for a wallet password as part of this process.

Device sessions

A mobile browser session may create device and security records when you sign in. These records help us identify unusual access while you switch between the lobby, Super Bingo and your account area.

Cookie choices

Cookies and similar browser storage can keep a session active and remember selected settings. You can clear them through your browser controls, although account entry may then require phone verification again.

Payment matching

We use payment references to check the status linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Wallet credentials are not required for this matching step.

Retention period

We keep account, security and transaction records only while needed for account operations, dispute checks or legal duties. When a record is no longer needed, our process removes or anonymises it.

Your requests

You can ask for a copy, correction or clarification through account help. We may confirm your identity through the registered phone before changing or releasing personal account data.

Privacy Policy Answers for dewaslot

These Privacy Policy answers cover the searches we hear most often before account access. They focus on the data attached to your dewaslot profile, the mobile path, payment references and the steps for contacting us. Where eligibility or access is relevant, it depends on local law.

It covers account, phone verification, device session, cookie and payment-reference data connected with your use of dewaslot. It also explains retention, security checks and how you can request access or correction.

We use phone verification to confirm account access and match a privacy request with the correct profile. This helps prevent another person from receiving or changing your account data.

Yes. The policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to check status without requesting your wallet password.

We may record browser, device and session details linked with sign-in activity. These records help identify unusual access when you move between a mobile browser, desktop session and account area.

Open account help and send a data request through the policy contact route. Include the registered account detail, then complete any phone confirmation we request before we respond.

Yes. Send a correction request through account help and identify the field that needs changing. We verify the account first and explain whether the requested change can be made.

We retain account, security and transaction records only for operational, dispute or legal needs. The period can differ by record type, and we remove or anonymise data when that need ends.