Reference

ayobet Privacy Policy For Your Account

ayobet puts your account, wallet and device privacy choices in one clear path, covering DANA, OVO, GoPay and QRIS records before you open the lobby.

Account dataWallet recordsCookie choicesMobile and desktop
ayobet ayobet Privacy Policy For Your Account
REQUEST A HAND

Privacy Help Through Your Account Path

A clear support route helps you ask about Privacy Policy matters without sending payment details into an open message.

Account help Use the account help path when you need to ask what personal details are held, why a phone verification record appears, or which Privacy Policy section applies to your request.
Wallet status If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the transaction reference through the account support path rather than sending a full wallet password or secret code.
Policy requests For a correction, access request or deletion question, identify your account and describe the change clearly. We may ask for an account step that confirms the request belongs to you.
HANDLING DETAILS

What We Do With Your Privacy Choices

Our Privacy Policy is designed around practical account handling rather than broad promises. We separate information needed for account operations from optional device signals, explain cookies in plain language and use account…

Account details

We use details such as your contact information and phone verification result to create, secure and maintain your account. We do not ask you to place wallet passwords or one-time codes in a policy request.

Cookies and devices

Cookies and device signals can help keep a sign-in session working and remember relevant choices. You can review cookie controls in your browser, although changing them may affect the policy page or account path.

Wallet records

For DANA, OVO, GoPay and QRIS activity, we retain transaction references and status details needed to reconcile an account request. We do not need your wallet secret to investigate a displayed status.

Account security

We use sign-in activity, device context and phone verification checks to identify unusual account behaviour. If a security detail changes, we may request confirmation through the account path before processing a related data request.

Retention approach

We keep personal records only for the purpose they serve and for periods required by applicable rules, then remove or anonymise them when appropriate. A retention question can be sent with your account identifier.

Change or access

You can ask us to access, correct or clarify personal details connected with your account. Send the request through account help, state the change you want, and complete any identity check needed to protect your records.

Privacy Policy Answers For ayobet Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the information linked to your sign-in, wallet references, device use and requests for changes. If your situation is not listed, use the account help path and give us enough detail to locate the correct record.

The ayobet Privacy Policy covers account and contact details, phone verification, sign-in activity, device signals, cookies, support requests and payment references. It also explains why we use those details, how retention works and how you can ask for access or correction.

For DANA, OVO, GoPay and QRIS, we may store a transaction reference, amount status and matching account details needed for reconciliation. We do not ask for your wallet password or one-time code when handling a Privacy Policy request.

Yes. Use the account help path and ask for access to the personal details connected with your account. Include your linked email or phone number, then complete an account check if needed so we do not disclose records to the wrong person.

Send a correction request through account help and name the exact field or record that needs attention. We may ask you to confirm the account step or phone detail involved before changing contact, verification or wallet-reference data.

Cookies and related device signals may support sign-in continuity, security checks and saved choices on your phone or computer. You can adjust browser controls, but blocking some cookies may change how the Privacy Policy page or account path behaves.

Retention depends on why a record was collected, account activity and applicable local requirements. We remove or anonymise details when they are no longer needed where appropriate. Ask through account help if you need clarification about a particular record.

Yes. Account access and eligibility depend on local law, and our Privacy Policy applies where local law permits. Before opening an account, check the current policy link and make sure your use of the service is permitted in your location.