Reference

Privacy Policy for Your arena303 Account

Our Privacy Policy explains what we collect when you open an arena303 account, use the mobile lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet checksDevice accessPolicy requests
arena303 Privacy Policy for Your arena303 Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet-status record. We handle privacy questions separately from general lobby requests, while still using the account step and payment reference you provide to locate the right record. Send only the details needed for the request, and do not include a password or full payment credentials. Where access is discussed, it remains available where local law permits. Our support path is also suitable for questions from Denpasar and other Indonesian locations.

Team online

Policy questions

Use our support contact path to ask how the Privacy Policy applies to your account, device record or payment reference. Include your registered contact detail so we can identify the correct account without asking you to send a password.

Correction requests

If your account detail is outdated or recorded incorrectly, tell us which field needs attention and why. We may ask you to complete phone verification before changing information linked to account access or wallet status.

Payment records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, provide the payment reference and date rather than sensitive wallet credentials. We use that limited context to check the record and explain the next step.

HANDLING DETAILS

What We Do With Privacy Requests

Privacy work follows the same account path you use to reach the lobby: we identify the account, check the request, and apply the relevant action without exposing unrelated records.

Account details

We use contact details and phone verification to create and protect your account. These details support login recovery and account requests, while the account path helps us avoid changing a record for the wrong person.

Device signals

The browser and device path may produce technical signals such as access time, operating context and security events. We use them to identify unusual login behaviour and keep mobile access connected to the correct account.

Cookies

Cookies and similar storage can remember a session, preserve basic preferences and help the account path work between login and the lobby. You can manage browser storage through your device settings, although some account steps may then need repeating.

Wallet activity

Payment references show whether a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event matches your account. We use the reference for status checks and do not ask for your wallet password.

Retention

We retain account, security and payment records only for the period needed for account operation, dispute handling, security checks and applicable legal duties. When a record is no longer needed, our handling follows the removal or protection process available to us.

Your requests

You can contact us to ask for access, correction or clarification about personal details connected with your account. We may confirm ownership through phone verification, then explain what can be changed and any reason a record must remain.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the records most likely to matter when you open an account from Indonesia. We explain account access, device activity, local wallet references and request handling in plain terms. If your question is not covered, use the support path and include the relevant account step or payment reference. Eligibility depends on local law, and we only discuss account access where local law permits.

The arena303 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support requests and payment references. It applies when you create an account, sign in, use the mobile lobby or ask us to check DANA, OVO, GoPay or QRIS activity.

Phone verification helps us connect an account request with the right account holder before access or a detail change is processed. It also supports login recovery and reduces the chance that someone using another device can alter your account information.

Yes. The Privacy Policy covers the payment reference and status connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to check a transaction, but you should never send a wallet password or full payment credentials.

We may receive technical signals from the browser or device used for login, such as access time, operating context and security events. These signals help us recognise unusual access and keep the correct account connected when you move between mobile and desktop.

Contact us through the support path and identify the account detail you want corrected. We may ask you to complete phone verification before making a change. Give us the minimum necessary context, and do not include a password or private wallet credential.

We keep account, security and payment records for as long as needed to operate the account, answer disputes, protect access and meet applicable legal duties. When a record is no longer needed, we follow our available removal or protection process.

Yes. You can ask us to clarify the personal details connected with your account, including account, device or payment-reference data. We may confirm ownership first, then explain the available access, correction or deletion action and any record that must remain.