Reference

beta168 Legal Rules For Your Account

beta168 Legal pages explain how account access, wallet records, privacy and site use work before you open an account.

Terms before accessPrivacy and cookiesLocal-law wording
beta168 beta168 Legal Rules For Your Account
POLICY HELP

Get Help With Legal Account Questions

A clear support route matters when a Legal question affects your account or wallet status. We ask you to include the account phone number, the relevant policy heading and any payment receipt reference, without sending a password or full wallet credentials. Use the support path displayed on our site so the request reaches the team handling account access and policy queries.

Team online

Terms clarification

If a clause about account access, phone verification or local eligibility is unclear, send the exact wording through our support route. We can point you to the relevant policy section and explain which account step remains, while access still depends on local law.

Wallet status check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the receipt reference and account phone number. We use those details to locate the record without asking for your password or private wallet sign-in data.

Change request

To ask about correcting account details, privacy choices or stored contact data, identify the requested change and the account phone number. We may request a verification step before changing records, helping keep the request tied to the correct account.

RECORDS AND CONTROL

How beta168 Handles Legal Duties

Legal handling is easier to assess when each record has a clear purpose. We separate account access details from payment references, keep policy links available for checking, and use verification before changing…

Account data

We use the phone number and account details you submit to identify your account, complete the stated access checks and respond to policy requests. Do not place passwords, wallet PINs or full payment credentials in a support message.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account receipt can help us match a transaction record. We ask for the reference needed for checking, not your wallet password, PIN or unrelated personal details.

Cookies

Cookies may keep a policy page, login route or account session working on your device. Your browser controls can manage cookies, but turning them off may affect account access or require you to repeat the phone verification path.

Account security

Phone verification is part of the account access path, and we may ask for an additional check before changing sensitive details. Keep your login details private and contact support if you see an account action you do not recognise.

Record retention

We retain account, support and transaction references only according to the purposes and periods described in the current policy text or required operational records. A retention question can be sent through support with the relevant account phone number.

Policy requests

For a copy request, correction request or question about how a record is used, name the policy area and identify your account through the support route. We verify the request before discussing or changing information connected to the account.

Legal Questions Indonesian Accounts Ask

These Legal answers focus on the account, data and access questions you may check before opening an account with beta168. If your situation is specific, use the support route named on the site and include only the details needed to locate your account.

beta168 Legal covers account access, phone verification, privacy, cookies, payment records, policy requests and local eligibility wording. Access depends on local law, so you should read the current terms before opening an account or using DANA, OVO, GoPay, QRIS or another listed payment route.

Yes. Our Legal wording does not treat access as universal. Eligibility depends on local law and the account checks shown during registration. If you are unsure whether access is available to you, check the current policy text and contact support before continuing.

Phone verification links an account access request to the contact detail you submit. It also helps us handle changes to sensitive records. Complete the verification step shown on screen, and never send your password, wallet PIN or full payment credentials to support.

DANA and QRIS references may be used to locate a payment record or resolve an account-status question. We request the receipt reference and account phone number where needed, not private wallet credentials. The applicable terms and privacy wording explain the handling purpose.

You can send a correction or change request through the support route shown on the site. State the policy area, the requested change and your account phone number. We may complete a verification step before changing information tied to your account.

Cookies can keep a policy page, account session or access route working across your device. Your browser provides cookie controls, but disabling them may require repeated verification or affect account access. The current privacy wording explains the relevant cookie purposes.

Retention depends on the purpose of the record and the periods described in the current policy text or required operational records. Ask support about a particular account or payment reference, and we will first verify that the request belongs to you.