Reference

Open arena333 Privacy Policy Before Account Access

arena333 Privacy Policy explains what we collect when you open an account, sign in on mobile, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet referencesDevice choicesContact route
arena333 Open arena333 Privacy Policy Before Account Access
CONTACT OPTIONS

Check Privacy Questions Through Support

A clear contact path matters when your account record or payment reference looks unfamiliar.

Account access If you cannot reach your account, tell us the sign-in email or phone detail and the device path you used. We may ask for account checks before discussing personal records.
Wallet reference For DANA, OVO, GoPay or QRIS questions, send the transaction reference only. Do not include a wallet PIN, password or full payment credential in your support message.
Policy request Ask us to explain, correct or remove eligible account data through the displayed contact route. We will verify that the request comes from the account holder before responding.
HANDLING DETAILS

Explore How arena333 Handles Your Records

The Privacy Policy is practical: it connects each data use to an account action you can recognise.

Account data

We handle details needed to create and maintain your account, respond to requests and complete verification. Fields that are not needed for those purposes should not be sent through support.

Device signals

A phone or desktop may provide browser, session and security signals when you sign in. These help us recognise unusual access without asking you to disclose private wallet credentials.

Cookies

Cookies and similar storage can keep your session working, remember selected settings and support security checks. You can manage browser storage, although removing it may require another account sign-in.

Account security

Before we discuss personal data, we may compare your account step, sign-in details and recent device context. This protects your records when a request comes from an unfamiliar session.

Retention

We keep records only for the account, payment matching, dispute handling, security or legal purpose that requires them. When a record is no longer needed, our process addresses deletion or safe disposal.

Change requests

You can ask us to correct eligible details or explain how a record is used. Include the account contact detail and the specific request, then complete any ownership check we provide.

Ask About Privacy Policy and Login Data

These answers focus on the questions you may have before opening an account from Indonesia. They cover wallet references, device behaviour, account requests and the limits that apply where local law permits access. If your situation is not listed, use the policy contact route rather than sending sensitive credentials.

The arena333 Privacy Policy covers account details, verification responses, device and session signals, cookies, payment references and support messages used to operate or secure your account.

Yes. The Privacy Policy includes references for DANA, OVO, GoPay and QRIS transactions. We use those references to match payment status and investigate account questions, not to request your wallet PIN.

A phone or desktop session can create browser and security signals that help us maintain login continuity and identify unusual access. Those records are handled under the arena333 Privacy Policy.

Use the contact route shown on the account help page, identify the account detail involved and state whether you want an explanation or correction. We verify account ownership before discussing personal records.

We retain account information only while it supports account service, payment matching, security, dispute handling or a legal duty. The applicable purpose determines when deletion or safe disposal can occur.

Yes. Cookies can support login sessions, selected settings and security checks. You can manage them in your browser, but removing storage may sign you out or require fresh device verification.

Yes. Account access and eligibility depends on local law. If you are in Indonesia, read the current policy and use the contact path shown to ask how a local requirement affects your request.