Reference

betpaus Privacy Policy for Your Account

The betpaus Privacy Policy explains how we collect, use and protect your account, phone verification and wallet records before you open the lobby.

Account clarityWallet recordsCookie choicesContact path
betpaus betpaus Privacy Policy for Your Account
CONTACT THE TEAM

Use Our Support Route for Policy Questions

A clear contact path helps when your Privacy Policy question concerns account access, a wallet status or a data change.

Policy question Send the section or sentence you want clarified through our support route. We can explain how the Privacy Policy relates to phone verification, cookies, account access or wallet records.
Data request Ask us to review, correct or remove eligible account details through the account support path. We may request phone verification before discussing records connected with your betpaus account.
Wallet record For DANA, OVO, GoPay, QRIS or bank transfer questions, include the payment rail and reference number. Do not send your wallet PIN, password or full security code in a message.
HANDLING YOUR DATA

Explore How betpaus Handles Policy Details

We keep the Privacy Policy practical by describing the points where data enters the account journey.

Account data

We use details such as your account identifier and verified phone status to connect you with the correct account area. Phone verification can be required before we discuss account records or make a requested change.

Payment details

A DANA, OVO, GoPay or QRIS transaction can create a reference used to check payment status. Bank transfer and virtual account records help us match a request without asking for your wallet PIN.

Cookies

Cookies can keep a mobile session linked to the selected account path and remember basic preferences. You can manage cookies through your browser settings, although some account steps may then need to load again.

Security checks

We may use phone verification, session checks and account details to reduce mistaken access. If your login looks unusual, contact support through the account route and avoid sharing a password or one-time code.

Retention period

We retain account and transaction records for the period needed to provide the requested service, resolve disputes and meet applicable legal duties. When a record is no longer needed, our handling follows the policy process.

Change requests

You can ask us to correct eligible details, explain a data use or address a deletion request through support. We check account ownership first, then confirm what action is available under local requirements.

Browse Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the questions we expect before account access: what we collect, why wallet references appear, how cookies work on mobile and how to request a change. If your case involves a specific DANA, OVO, GoPay or QRIS reference, use the support route with that reference available.

It covers account details, phone verification, cookies, security checks, payment references, retention and requests to correct or remove eligible data. Access remains where local law permits.

Phone verification helps connect you with the right account and protects account discussions. We may complete this check before explaining records or processing a requested account change.

Yes. The policy covers references created through DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account records used to check a payment request.

Cookies can remember a session and basic settings so your mobile browser returns to the expected account step. Browser controls can remove them, but some steps may reload.

You can contact support through the account route and ask us to correct eligible details. We first verify account ownership, then explain the available action under applicable requirements.

We keep records for as long as needed for the requested account service, payment checks, dispute handling and applicable legal duties. The policy process guides later deletion or retention.

Use the support route linked from your account area and mention the relevant section. For wallet questions, add the payment rail and reference, but never send a password or wallet PIN.