Reference

dobleslot Privacy Policy

Our Privacy Policy explains how dobleslot handles the details connected to your account, including phone verification, wallet records and device access.

Phone verificationCookie choicesWallet recordsPolicy requests
dobleslot dobleslot Privacy Policy
CONTACT THE TEAM

Where Privacy Questions Meet Support

A clear contact path matters when your account record or wallet status needs attention. Start from your signed-in account support route and describe the exact privacy question, rather than sending payment details through an unrelated channel. We use the details you provide to locate the relevant record, check the request and explain the next account step. If you cannot sign in, keep your message limited to the contact detail needed to identify your account.

Team online

Account privacy request

Use the support route attached to your account when you want to ask what personal details we hold or why a phone verification record appears. Include your registered contact detail and a short request; do not send your password or one-time access code.

Wallet record question

For DANA, OVO, GoPay or QRIS records, tell us the wallet name, date and reference shown to you. We can then separate a payment-status question from a personal-data request without asking you to repeat your full account history.

Access problem

If the account page does not open on your phone, contact us through the available account support path and state the device type and browser. We will use that information to help with access while keeping the privacy request focused on your data.

HANDLING DETAILS

What Our Privacy Process Covers

We treat the Privacy Policy as an operating process, not a page kept apart from the account flow.

Account data

We may handle your registered contact detail, phone verification result, login activity and account settings. These fields help us return you to the correct account when you move from the login screen to the lobby, while access remains subject to local law.

Cookies

Cookies can remember a language choice, session state or device preference so the privacy page and account screens behave consistently. You can manage available cookie choices in your browser, though changing them may affect sign-in or saved settings.

Account security

We use phone verification and sign-in records to check whether an access request fits your account pattern. Never share a password or one-time code. If a new device shows an unexpected sign-in, contact support and describe the event.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored to match a wallet event with your account. We use that reference for status checks and support, not as a reason to request your wallet password.

Retention

We retain account and transaction records for the period needed to operate access, resolve disputes, protect the service or meet applicable obligations. When a record is no longer needed for those purposes, our handling process moves it toward deletion or restriction.

Change requests

Ask us to correct an incorrect phone detail, explain a stored record or consider an eligible deletion request through account support. We may ask for verification before changing data, so one person cannot alter another person’s account.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a wallet payment. We explain what can appear in our records, how you can reach us and why verification may be needed for a change. Keep the policy page bookmarked on your phone so you can return to it while checking account access, QRIS references or a device session.

The dobleslot Privacy Policy covers account details, phone verification, sign-in events, device information, cookies and payment references. It also explains how we respond to access, correction, deletion and policy questions. The same policy applies whether you read it on a phone or desktop.

We may collect the contact detail you submit, your phone verification result, account settings, sign-in events and technical details from your device or browser. If you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account, related references may also enter the account record.

Phone verification helps us connect an access request with the correct account and investigate sign-in problems. It can also reduce the chance of an unauthorised person changing account details. We will not ask for your password or one-time code through a privacy request.

Use the support path inside your account and state whether you want a correction, an explanation or an eligible deletion. Include the affected contact detail without sending secret credentials. We may verify your identity first, because a data change must not expose another person’s account.

Yes. The Privacy Policy explains how DANA, OVO, GoPay and QRIS references can be used to match a payment status with your account. A bank transfer or virtual account reference may be handled in the same way for receipt checks and support.

We keep information for the time needed to operate your account, investigate security events, resolve payment questions or meet applicable obligations. The period can differ by record type. When a record is no longer needed, our process moves it toward deletion or restricted access.

Yes. You can read this Privacy Policy before completing the account path or phone verification. Access to the service depends on local law, and where local law permits, you can contact us through the available support route with questions before providing additional account details.