Reference

aretabet Privacy Policy for Your Account

aretabet Privacy Policy explains how we handle your account details, wallet records and device activity before you open the lobby.

Account clarityWallet recordsCookie choicesLocal-law access
aretabet aretabet Privacy Policy for Your Account
REQUEST ROUTES

Where To Send a Privacy Request

A clear request path helps you act on the Privacy Policy without searching through the lobby. Start in account help, select the privacy or data request route, and include the phone number attached to your account. If wallet status is part of the question, keep the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference visible. We may ask for account verification before releasing or changing records.

Team online

Account help

Use the account help route for access, correction or deletion requests. Include your registered phone number and explain which Privacy Policy record you want us to check.

Wallet reference

For a payment-data question, provide the relevant DANA, OVO, GoPay or QRIS reference. We use that detail to locate the correct transaction record.

Browser support

If cookies or device access are unclear, tell us whether you use a mobile browser or desktop browser. We can connect the request to the right session record.

DATA CONTROLS

Account Security and Data Controls

Privacy works best when the controls match the way you access your account. We separate account details from routine lobby activity, check phone verification before account access and use session signals to…

Account details

We use the phone number and account details you provide to create, verify and maintain access. Phone verification is checked before account access and may be revisited during recovery.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match a wallet event with your account. We do not treat a payment reference as your full identity.

Device signals

Browser type, device markers, login time and session events help us review unusual access. On mobile, these signals relate to the browser path rather than a separate installed application.

Cookies

Cookies can remember session settings and help the account path work between login and the lobby. You can adjust cookie behaviour in your browser, though some account functions may then need another login.

Retention period

We retain account, support and transaction records for the time needed for account administration, dispute handling, security checks or a legal requirement. When that need ends, records are removed or separated from direct account use.

Changes and access

You can ask us to access, correct or remove eligible data through account help. We may verify your account first, and access or eligibility depends on local law and the request type.

Privacy Policy Questions for aretabet

These Privacy Policy answers focus on the account actions you are most likely to take: opening access, checking a wallet record, changing browser settings or asking us to handle personal data. We keep the route practical for Indonesia, while legal access and eligibility depends on local law. If your question is not listed, use account help and include the relevant account or transaction reference.

The aretabet Privacy Policy covers account details, phone verification, wallet references, device and browser activity, cookies, support records, retention and data requests. It explains why we use each category and how you can ask for access, correction or removal where local law permits.

We record DANA, QRIS and other wallet references to match a payment event with the correct account, check a status question and prevent mistaken account changes. The reference supports reconciliation; it is handled as transaction data rather than a replacement for your identity.

Open account help and choose the privacy or data request route. State that you want an access request, add your registered phone number and describe the records involved. We may verify account control before responding, and the result depends on local law.

Yes, you can request a correction through account help. Identify the incorrect field, provide the updated value and explain why it should change. For a wallet record, add the DANA, OVO, GoPay, QRIS or bank reference so we can locate it accurately.

We keep records while they are needed for account administration, payment reconciliation, support, security review or a legal requirement. The exact period can differ by record type. After the purpose ends, we remove the record or separate it from direct account use.

Cookies can preserve a browser session and selected settings between login and the lobby. You can change cookie behaviour in your mobile or desktop browser. If cookies are blocked, you may need to log in again, and some account functions may not work as expected.

Use the account help route and select the privacy or data request option. Include your registered phone number, the request type and any relevant transaction reference. For access or eligibility questions, the applicable outcome depends on local law and your account status.