Reference

boya bet Privacy Policy, Made Clear

Your account data, wallet details and device choices receive a clear explanation in the boya bet Privacy Policy.

Account clarityWallet contextCookie choicesPolicy requests
boyabet.xyz page image
POLICY HELP ROUTE

Get Answers Without Sharing Extra Data

A direct support route helps you ask about the Privacy Policy without exposing more account data than needed.

Policy questions Ask how we collect, use or retain a specific detail through the account support route. We can explain the relevant Privacy Policy section without asking for your password, wallet PIN or full payment credentials.
Account access If phone verification or a device check blocks access, contact support from the account path and identify the verified phone reference. We use that step to reduce mistaken changes to your personal data.
Receipt matching For DANA, OVO, GoPay, QRIS or bank transfer questions, attach only the receipt fields requested by support. We use the transaction reference to locate the record and avoid collecting unrelated wallet details.
DATA CONTROL POINTS

What We Keep, Protect and Change

Privacy choices work best when they match the way your account is actually used. We separate sign-in checks, wallet records, device signals and support messages so a request can be handled with…

Account data

We may hold your name, contact detail and phone verification status to maintain the account path. When you request a correction, we compare the request with the verified account reference before making a change.

Wallet records

DANA, OVO, GoPay and QRIS references let us trace a payment status without storing your wallet PIN. Bank transfer and virtual account records may remain connected to the matching account transaction.

Device signals

Login time, browser type and selected device signals can help us identify unusual access. These checks support account security; they are not a request for your private device files or unrelated applications.

Cookie settings

Cookies can remember a session and preserve a selected language or account path. Your browser controls can clear or restrict them, although some sign-in functions may then require another verification step.

Retention periods

We retain account, payment and support records only for the period needed for the stated account purpose, dispute handling or a legal requirement. The policy route can explain why a particular record remains.

Change requests

Send a correction, access or deletion request through support with your verified phone or account email. We may ask for an account step before acting, so another person cannot change your records.

Privacy Policy Questions for Your Account

These Privacy Policy answers focus on the account actions Indonesian customers ask about most: phone verification, wallet records, cookies, device checks and data requests. Read them before opening an account, then use the support route if your situation needs a closer answer. Where local law permits, we will explain the available choice and the account step needed to confirm it.

It covers account details, phone verification, payment references, device signals, cookies, support messages, retention and requests to access or change eligible data. It also explains why each category is used.

Phone verification helps connect account access to the correct person and supports checks when a login or data request looks unusual. We use the verified reference rather than asking for your password.

Yes. It explains how DANA and QRIS transaction references help us match payment status to your account. We do not need your wallet PIN, and support will request only relevant receipt fields.

You can send a correction request through the account support route using your verified phone or account email. We may complete an identity check before changing records connected with your account.

The policy explains cookies used for sessions, language choices and account navigation. You can manage them through your browser, though restricting required cookies may trigger another sign-in or verification step.

Yes. We describe how browser, device and login signals can help identify unusual account access. These signals support security checks and are handled separately from private files stored on your device.

Use the support link beside the cashier area and state whether you need access, correction, deletion or an explanation. Include only the verified account reference and any receipt detail specifically requested.