Reference

Privacy Policy For Your dynabet Account

Our Privacy Policy explains how dynabet collects, uses, stores and protects the details connected with your account, device and payment activity.

Account dataWallet referencesCookie choicesPolicy requests
Browse Our Lobby Read FAQ
dynabet Privacy Policy For Your dynabet Account
HELP WITH REQUESTS

Get Clear Answers About Your Data

If you have a Privacy Policy question, use the support route shown in your account and include the phone number linked to your profile. This helps us locate the correct record without asking you to send a password or wallet PIN. Our team can explain a data-access request, clarify a DANA or QRIS reference, and tell you what identity checks are needed before we change account details. If you are in Surabaya or elsewhere in Indonesia, the same account support path applies where local law permits.

Team online

Account support route

Open the support path beside your account and describe the Privacy Policy request in plain English. We may ask for your registered phone number and a verification step before discussing personal data, while keeping your password and wallet PIN out of the conversation.

Wallet data question

When a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt detail through the account support route. We can match the reference to the relevant account event and explain what was recorded without requesting your wallet password.

Correction request

To correct a phone number, name or other account detail, tell us which field is wrong and what it should say. We verify the request against your account before making a change, so another person cannot alter your profile through a simple message.

DATA HANDLING

How dynabet Handles Privacy Choices

We apply this policy to the practical moments you encounter: opening an account, signing in from a new device, checking a wallet reference or asking us to remove an outdated detail.

Account records

We collect details needed to create and maintain your account, such as your phone number and verification status. Login events help us identify unusual activity, while profile data lets support answer a request about the correct account rather than a similar record.

Device signals

The site may record browser, device and connection signals when you sign in from mobile or desktop. These details help us recognise a changed device and investigate an account-access concern; they are handled as technical security data, not as your wallet PIN.

Cookies

Cookies can keep your session working and help us remember basic site choices. You can manage cookie settings through your browser, although turning some cookies off may require you to sign in again or repeat a preference step.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain a reference, status and timestamp rather than your wallet password. These records help us trace a receipt question and connect it to the right account event.

Storage period

We retain personal data only while it serves account administration, security, dispute handling or a legal requirement. When a record is no longer needed for those purposes, we remove it or separate it from direct account identifiers where the process allows.

Policy changes

If this Privacy Policy changes in a meaningful way, we will place the updated wording on this page and show the relevant date. Check the page before opening an account or continuing after a major change, especially when your data choices matter.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain what we collect, how you can ask for a copy or correction, and why a verification step may appear when you contact us. For a case tied to your own profile, use the support route shown after login and follow the identity checks requested by our team.

The dynabet Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references and support requests. It also explains retention, security handling, policy changes and the steps available when you want to ask about, correct or access your personal data.

We may collect your name, phone number, verification status, account activity and technical details such as browser, device, IP address and login time. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may record transaction references and statuses.

Yes, you can ask for details linked to your account through the support route shown in your profile. Include your registered phone number and describe the request. We may complete an identity check first, because a data copy must go to the correct account holder.

Tell our support team which account field is inaccurate and provide the corrected value. We compare the request with your account and may ask for phone verification before changing it. This protects your profile from changes made by someone using an unrelated contact address.

It does. Cookies can keep your session active and retain basic site choices, while technical signals help us identify unusual sign-ins. You can adjust cookies in your browser, but switching some off may cause repeated login steps or remove saved preferences.

We keep records for the time needed to administer your account, protect access, handle payment or account disputes and meet applicable legal duties. After that need ends, we remove the record or separate it from direct identifiers where our process allows.

Use the support path connected to your dynabet account and state whether you need access, correction, deletion or an explanation of a recorded event. Do not send a password or wallet PIN. Account eligibility and access depend on local law, including where local law permits.

Related Pages

dynabet Indonesia About Us dynabet Casino Access guide La Liga Handicap Odds