Reference

ara288 Privacy Policy for Your Account

The ara288 Privacy Policy explains what we collect when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
ara288 ara288 Privacy Policy for Your Account
HELP PATHS

Get Privacy Help Beside Wallet Status

A clear contact path helps when a privacy question sits beside an account or wallet issue. We ask you to sign in where possible, then send the relevant account step, receipt reference or device path through the support contact shown in your account. For requests from Surabaya or elsewhere in Indonesia, we use the details you provide only to locate the record and answer the Privacy Policy question.

Team online

Account contact

Use the support contact inside your account to ask what personal data we hold, why a record exists, or which step produced a DANA, OVO, GoPay or QRIS reference.

Receipt matching

Include the payment receipt or status reference when your request concerns a wallet action. We can then separate a QRIS confirmation from a bank transfer record without asking for unrelated details.

Access concern

If sign-in stalls after phone verification, tell us the device path and account email or phone detail used. We use that context to investigate access without requesting your wallet password.

DATA PRACTICE

Your Account Data Across Mobile and Desktop

Privacy choices should remain understandable whether you open the lobby on a phone, tablet or desktop browser.

Data we collect

We collect account details you submit, phone verification results, sign-in events, device and browser signals, payment references, support messages and activity needed to display records for Live Baccarat, Bingo or other selected areas.

Cookie settings

Cookies can remember session state and account preferences on your device. You can manage browser cookie controls, though restricting them may require another sign-in before your account history or Privacy Policy choices appear.

Account protection

Phone verification is an account step before access. We use sign-in signals and payment status checks to detect unusual activity, and we do not ask you to disclose your wallet password through support.

Record retention

We retain account, payment and support records for the period needed to operate the account, resolve disputes, protect against misuse and meet applicable duties. Retention can differ by record type and local law.

Correction requests

You can ask us to correct inaccurate account details through the support contact shown after sign-in. State the field that needs changing and provide enough account context for us to verify the request.

Who to contact

Our account support route handles Privacy Policy questions, data access requests and deletion enquiries. Include your registered contact detail, but never send a DANA PIN, OVO code, GoPay password or banking credential.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the account, device and payment questions you may search before opening access. We keep each response tied to the records we actually use, and where eligibility is relevant, access depends on local law.

The ara288 Privacy Policy covers account details, phone verification, device signals, cookies, payment references, support messages and activity records connected with areas such as Live Baccarat or Fishing God.

Phone verification helps connect account access to the contact detail you provide and supports unusual sign-in checks. We use the result for account protection and do not need your DANA or GoPay password.

Yes. The Privacy Policy covers DANA and QRIS references, status confirmations and account matching details needed to identify a transaction. Your wallet provider remains responsible for its own records and privacy terms.

You can request access through the support contact shown in your account. Include your registered phone or email detail so we can verify the request before discussing account, cookie or payment records.

Send a correction request through account support and name the field that is inaccurate. We may ask for an account step or contact detail to confirm the request before changing the record.

We keep payment references for the period needed to match wallet or bank activity, resolve account questions, prevent misuse and meet applicable duties. The period can vary by record type and local law.

Yes. Ask through the account support contact or adjust cookie controls in your mobile browser. Restricting cookies may end a session or require phone verification again before account access continues.