Reference

Privacy Policy For Your arizona99 Account

Our arizona99 Privacy Policy shows what account, wallet and device data we use, why we need it, and how you can ask about it.

Account dataWallet referencesCookie choicesPolicy requests
arizona99 Privacy Policy For Your arizona99 Account
HELP PATHS

Get Privacy Policy Help Near Account Support

A clear support path helps when you want to understand a data entry, correct an account record, or ask why a wallet reference appears in your history. Send your request through the account support route and include the phone number linked to your profile, the relevant date, and a short description of the issue. We use those details to locate the correct record without asking you to send a password or wallet PIN.

Team online

Account data request

Ask us which account details are connected to your phone verification and login record. We may request enough profile detail to confirm that the request comes from you before discussing or changing personal data.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the payment reference and date. We can check the matching status while keeping your wallet password and PIN outside the request.

Correction request

If your phone number, account name or contact detail is inaccurate, tell us what needs changing. We may pause the update until phone verification confirms the request and protects the account from an unapproved edit.

HANDLING PRACTICE

What We Do With Your Policy Data

We handle Privacy Policy matters through the same account controls used for sign-in and payment checks.

Account records

Your phone number, verification result and login events help connect the right person to the right arizona99 account.

Payment references

A DANA, OVO, GoPay or QRIS reference can help match a cashier event with your account.

Cookie settings

Cookies can remember session preferences and help the account path work between login and the lobby.

Device security

We may record browser type, device signals and sign-in time to spot an unusual session.

Retention period

We keep account, support and transaction records only while they serve an operational, dispute or legal need.

Your request

You can ask about stored data, request a correction, or ask for deletion through account support.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers focus on the questions you may have before opening or using an arizona99 account from Indonesia. We explain the records linked to phone verification, the way wallet references are checked, browser cookie choices, account security events, retention and requests for correction or deletion. If your question is not covered, use the account support path with your linked phone number and the relevant date, and we will route it to the right policy contact.

It covers data connected with account creation, phone verification, sign-in, browsing, support requests and payment checks. That can include account identifiers, device signals, cookie settings, login events and transaction references for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access to the person opening the profile and helps us protect changes to personal data. We may use the verification result for sign-in checks, correction requests and questions about account records, without asking for your wallet PIN.

The policy describes payment references and status checks, not collection of your DANA or QRIS password. The same approach applies to OVO, GoPay, bank transfer and virtual account records. Keep wallet credentials private and include only the reference needed for a support request.

Use the account support path and state which profile entry is inaccurate, such as your phone number or account name. Include the linked phone number and request type. We may verify ownership before changing the record, so another person cannot edit your account.

You can submit a deletion request through account support. We first confirm ownership and then assess which records can be removed under the Privacy Policy. Transaction, dispute or legal records may need to remain where local law permits or requires retention.

Cookies may remember session preferences and help keep the route from login to the lobby consistent on a mobile browser or desktop. Your browser controls can limit them. If cookies are disabled, you may need to repeat settings or verification steps.

Yes. Send a data access request through account support with your linked phone number and a clear request description. After ownership checks, we can explain the relevant account, device, cookie, support or payment-reference records covered by the Privacy Policy.