Reference

deltatogel Privacy Policy for Your Account

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

Account dataWallet recordsDevice choicesPolicy requests
deltatogel deltatogel Privacy Policy for Your Account
CONTACT DATA HELP

Contact Us About Your Policy Data

A clear contact path matters when a Privacy Policy question affects your account or wallet record. We ask you to include the account detail connected to the request, the relevant payment reference and the change you want considered. Our support route stays close to the cashier path, so a question about DANA, QRIS or phone verification can be checked against the right record without guesswork.

Team online

Account requests

Use our support route to ask which account details we hold, why phone verification is needed, or how to correct a sign-in record. Include your registered contact detail so we can locate the request.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and visible status. We use those details to trace the relevant record without asking for your wallet password.

Privacy changes

Ask us to change, clarify or remove eligible personal details through the same support path. We may first confirm account ownership before acting, helping prevent another person from changing your data.

DATA HANDLING

See How deltatogel Handles Account Data

Privacy protection works through practical account steps rather than vague promises. We separate sign-in checks from payment references, explain cookie use, and keep requests tied to the account record they concern.

What we collect

We may handle your account contact details, phone verification result, sign-in events, device signals and payment references. Each category supports access, security, transaction matching or a direct request you send to us.

Cookie choices

Cookies and similar browser storage can help retain a session or remember a selected setting. You can check browser controls on your phone or desktop, while changing them may affect sign-in continuity.

Account security

Phone verification before account access helps us distinguish your sign-in from an unfamiliar attempt. Never send a wallet password through support; payment references are enough for a status check.

Retention approach

We retain records for the period needed for account security, transaction matching, dispute handling and legal duties. When a record is no longer needed for those purposes, our process addresses its removal.

Change requests

You can ask us to correct account details or explain the reason for a data field. We may request an account check first, especially when the request could affect phone or wallet-linked records.

Policy contact

Send a Privacy Policy question through our account support route and describe the exact section or data field involved. We can then address the request directly instead of giving a broad reply.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers cover the searches we hear most often before account creation. They explain the practical link between your account, device, wallet reference and contact request, while access remains subject to local law and the wording available on our current policy page.

It covers account details, phone verification, sign-in and device signals, cookies, wallet references, retention, security handling and requests to change or remove eligible personal details.

Yes. The policy explains how DANA, OVO, GoPay and QRIS references may be connected to an account for payment matching, receipt checks and status questions.

Phone verification supports account security before access. It helps us connect a sign-in to the correct account and gives our support route a clearer way to assess an access request.

You can send a correction request through support and identify the account field involved. We may confirm account ownership before changing contact, phone or wallet-linked details.

Records remain while needed for account security, transaction matching, dispute handling or legal duties. The policy process addresses removal when a record no longer serves those purposes.

Check cookie controls in your mobile or desktop browser, then contact support if you need clarification about a setting. Changing cookies can affect session continuity and sign-in behaviour.

Access depends on local law. Before opening an account, confirm that use is permitted in your location, then read the current Privacy Policy and contact support about any data question.