Reference

Open jayabet Privacy Policy

Your jayabet Privacy Policy page explains what we collect during account creation, phone verification and wallet activity, so you can decide what to share before opening an account.

Clear data purposesPayment record detailAccount access choicesPolicy contact path
jayabet Open jayabet Privacy Policy
CONTACT ROUTES

Reach Policy Support From Your Account

A clear support route helps when you want to ask about a data field, correct an account detail or understand a payment record. We ask you to contact us from the account path where possible, because that lets us match the request without exposing private details to the wrong person. Keep your receipt reference ready when your question concerns DANA, QRIS or a bank transfer.

Team online

Account privacy request

Open the support path from your account and state whether you need access, correction or deletion guidance. We may ask for account details to confirm that the request comes from you.

Login and identity check

If phone verification or a login check blocks your request, tell us which account step stopped. Do not send your password; we use account details to locate the correct privacy record.

Payment record query

For a wallet or bank record question, include the payment method and receipt reference rather than unrelated personal details. This gives our support route a focused way to trace status.

DATA PRACTICES

Explore Your Data Controls

We keep this policy practical by connecting each data use to an account action you can recognise, from phone verification to a mobile-browser login.

What we collect

We may collect contact details, phone verification results, login events, device information and payment references. These details help us connect your account step with a request made through DANA, QRIS or another listed rail.

Why we use it

We use account data to provide access, check unusual login activity, match payment status and answer support requests. We do not describe a casino title such as Live Roulette as a reason to collect unrelated personal details.

Cookies and devices

Cookies and similar browser records can keep a login path, language choice or security check working. On a mobile browser, these signals help us recognise the same session without treating your device as a separate account.

Account security

Phone verification and login checks help protect your account from access attempts that do not match your normal details. Keep your password private, and contact support if a device or session looks unfamiliar.

How long records stay

We retain records only as long as needed for the stated account, security, payment or legal purpose. A receipt linked to GoPay or bank transfer may need to remain available while a status question is open.

Changes and requests

You can ask us to explain a field, correct inaccurate details, request a copy where available or ask about deletion. Send the request through your account support path so we can confirm your identity.

Browse jayabet Privacy Policy Answers

These answers cover the searches we hear most often about the jayabet Privacy Policy, including account creation, mobile access, payment references and requests to change stored details. Read the full policy wording before opening an account, and contact us when your situation needs a specific answer.

It covers data connected to your account, phone verification, login activity, device signals, cookies, payment references and support requests. It also explains purposes, retention, security steps and ways to request changes.

Phone verification helps connect account access with the correct person and supports security checks. We record the result and related account details for access handling, subject to local requirements and the stated policy purpose.

Yes. The policy covers payment references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are connected to your account.

Use the support path from your account, describe the field that needs correction and provide enough account detail for identity checking. Do not send your password or unrelated payment credentials with the request.

Yes. It explains that cookies and similar browser records may support login continuity, language settings and security checks. You can review browser controls on your phone, though changing them may affect account access.

Retention depends on the reason for holding a record, such as account security, payment status, support handling or legal requirements. Ask through your account support path for details about a specific record.

You can submit an access question through the account support route. We may verify your identity before responding, and some records may need to remain available when connected to security, payment or legal duties.