Reference

arena369 Privacy Policy For Your Account

Our arena369 Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
arena369 arena369 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps you ask what data we hold or why a record appears beside your account. Use the support path connected to your login and include the account identifier shown there; this lets us locate the correct record without asking you to send a wallet password. If you are in Makassar or elsewhere in Indonesia, the same privacy request path applies where local law permits.

Team online

Account support

Use the support link after signing in when you want to ask about profile data, a verification record, or a correction. We may request account details that help us confirm you are asking about your own information before discussing the record.

Payment receipt

For a DANA, OVO, GoPay or QRIS question, send the transaction reference shown in your account rather than a wallet PIN. We can use that reference to check the recorded status and explain which payment detail is held.

Privacy request

Ask for access, correction, deletion where available, or a retention explanation through the same support contact. Include the request type and your account email or phone so we can apply the right identity check.

HANDLING DETAILS

How We Handle Your Account Data

Privacy choices work best when each data use has a clear reason. We separate account access records from payment references, use device signals to notice unusual sign-in patterns, and keep cookie controls…

Account records

We use the details tied to your account to support sign-in, phone verification, profile corrections, and requests made through the account path. Keeping those details accurate helps us distinguish your request from another account with a similar contact detail.

Wallet references

A deposit or withdrawal record can include a rail name, amount reference, timestamp, and status. For BCA, BRI, Mandiri or BNI bank transfer activity, we use the reference needed to reconcile the request, not your full banking login.

Device signals

When you sign in on mobile or desktop, we may record browser, device, connection, and security-event details. These signals help us investigate an unfamiliar session without treating your phone as permission to read unrelated files or applications.

Cookies

Cookies can keep a session open, remember selected settings, and help us understand whether a page loads correctly. You can manage browser cookie controls on your device, although disabling some cookies may affect sign-in or policy-page access.

Retention checks

We keep records for the period needed for account support, payment reconciliation, security review, or a legal requirement. If you ask why a record remains, contact us with its date or reference and we will explain the applicable retention reason.

Change requests

You can ask us to correct inaccurate account data or explain available deletion options where local law permits. We first verify the request, then confirm what can be changed and whether a record must remain for a stated operational or legal reason.

Privacy Policy Questions For arena369

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. They explain the practical route for checking records, changing details, managing cookies, and asking about information linked to a local wallet or bank transfer.

It covers account details, verification records, sign-in and device signals, cookie use, support messages, and payment references. It also explains why we retain selected records and how you can request access, correction, or an available deletion option where local law permits.

No. We use payment references and status details needed to match an account event, but you should never send a wallet PIN or banking password through support. For DANA or OVO questions, provide the transaction reference shown in your account.

Sign in, open the support contact path, and ask for an account-data access request. Include the email or phone connected to your account and complete any identity check we require. We will explain the available records and any limits that depend on local law.

Yes, ask through the account support route and identify the field that is wrong. We may verify your identity before changing a phone number or email because those details affect account access. We will confirm the result or explain why a record cannot be changed.

On a mobile browser, cookies may support your sign-in session, remember settings, and help us diagnose page loading. You can adjust cookie controls in the browser settings. Turning some off may require another login or limit parts of the account path.

Retention depends on the record and its purpose, such as support, reconciliation, security review, or a legal requirement. A QRIS, GoPay, virtual account, or bank transfer reference may remain for that reason. Ask support with the date or reference for a specific explanation.

Use the support link connected to your signed-in account and state whether you need access, correction, deletion where available, or a retention explanation. Include only the requested account identifier, not a password or wallet PIN. Requests are handled where local law permits.