Reference

Check live draw lotto Privacy Policy

The live draw lotto Privacy Policy explains what we collect when you open an account, verify your phone, browse on mobile and use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesContact requests
live draw lotto Check live draw lotto Privacy Policy
REQUEST A RESPONSE

Reach support about privacy requests

A clear support path helps when your account record, wallet status or privacy request needs checking.

Account access If you cannot reach your account, tell us the registered phone number and the device path you used, such as a mobile browser. We can match the access issue to the correct privacy request without asking you to send a wallet password.
Wallet record For a DANA, OVO, GoPay or QRIS record, include the rail name and transaction reference. Our support route can check whether the entry is pending, completed or linked to the wrong account before we discuss a correction.
Data change To request an update or deletion, state which personal detail you mean and why it is inaccurate or no longer needed. We confirm account ownership first, then explain any records we must retain under applicable local requirements.
HOW WE HANDLE IT

Explore the privacy controls on your account

Our privacy process follows the journey from phone verification to account access, wallet activity and support follow-up.

Account data

We use your account details to create the profile, complete phone verification and connect requests to the right account. If your name, phone number or other stored detail is wrong, ask us to correct it through the logged-in support path.

Cookie settings

Cookies can help remember a session and show whether a mobile browser has already passed an account step. You can clear browser cookies from your device settings, though clearing them may require you to verify your phone again.

Security checks

We use sign-in records, phone verification and unusual activity checks to protect account access. Never send us your wallet password or one-time code. If a login looks unfamiliar, report the event through support with the affected device path.

Payment details

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain operational references rather than asking for private wallet credentials. A receipt or transaction code helps us locate the correct entry when you request a status check.

Retention period

We keep personal and transaction records while they support account operation, dispute handling, security checks or duties that apply where local law permits. When a record is no longer needed, we remove it or use a form that no longer identifies you.

Your request

You can ask what data we hold, why we use it, whether it was changed, or how to correct or delete it. Send one request per account through support and include enough detail for us to verify ownership safely.

Browse answers about Privacy Policy

These Privacy Policy answers focus on the account steps you are most likely to question before opening an account from Indonesia. We cover phone verification, mobile browser cookies, wallet references, account access and the route for requesting a copy, correction or deletion of your data.

The live draw lotto Privacy Policy covers account details, phone verification, mobile browser cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains security checks, retention and your requests to access or change stored data.

We use your phone number to create and verify the account, connect support requests to the correct profile and help protect access after an unusual sign-in. We do not ask you to send a wallet password. Any eligibility question depends on local law.

Yes. The Privacy Policy covers the payment rail selected, transaction reference, status and receipt details linked to DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records. These details help us trace a request without needing private wallet credentials.

Cookies can keep a mobile browser session active and show whether an account step has already been completed. If you clear them in your device settings, we may ask you to sign in and complete phone verification again. Cookie handling is part of this Privacy Policy.

Yes. Use the logged-in support path, identify the account detail or transaction record concerned and include your registered phone number for ownership checks. We can explain the data held, correct inaccurate details and tell you if a record must remain under applicable requirements.

We retain account, security and transaction records only while they support account operation, dispute handling, fraud checks or duties that apply where local law permits. After that need ends, we remove the record or change it so it no longer identifies you.

After login, use the account support route and write Privacy Policy request in your message. Include your registered phone number, the device path if access is involved, and a DANA, OVO, GoPay or QRIS reference when your request concerns a payment record.