Reference

36ox Privacy Policy For Account And Wallet Data

36ox Privacy Policy explains what we collect when you create an account, enter the lobby, or connect DANA, OVO, GoPay and QRIS.

Account recordsWallet activityCookie choicesAccess requests
36ox 36ox Privacy Policy For Account And Wallet Data
HELP WITH YOUR DATA

Get A Clear Privacy Policy Contact Path

A direct support path helps when a privacy question is connected to a login, wallet receipt or account correction. Start from the support contact shown inside your account area and include the phone number linked to your account, the request you are making and any relevant payment reference. We use those details to locate the right record without asking you to send an unnecessary password.

Team online

Account access

If you cannot enter your account, tell us the phone number linked to it and the device path you used, such as mobile browser or desktop browser. We may ask for verification before discussing personal records.

Wallet privacy

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date rather than your wallet password. We can check the record attached to your account and explain what we retain.

Policy requests

For a copy, correction or deletion request under this Privacy Policy, describe the exact data involved. We will respond through the support contact connected with your account where local law permits.

DATA HANDLING DETAILS

What We Do With Privacy Policy Requests

We keep this policy area practical: you should be able to see why a record exists, how an account request is checked and where to ask for a change.

Account data

We may hold your phone number, verification result, login timestamps and account preferences. These details help us connect a request to the correct account and reduce mistaken changes to your access.

Cookies and devices

Cookies and device signals can keep a session working, remember selected settings and help identify unusual login behaviour. You can manage browser cookie controls, although some account functions may then need another check.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be stored with transaction status. We use them to reconcile account activity, investigate a receipt and answer a payment dispute.

Security checks

Before we disclose or change personal records, we may ask you to confirm account details or complete phone verification. We do not need your password in a support message.

Retention timing

We keep records only as long as needed for the stated account, security, payment or legal purpose. Where local law permits, you may ask why a particular record still needs to remain.

Your request route

Send access, correction or deletion requests through the support contact shown after login. Include a precise request and matching account detail so we can check identity before replying.

Privacy Policy Answers For 36ox Accounts

These Privacy Policy answers address the searches we hear most often before account creation or a wallet request. They cover personal data, cookies, payment references, account access and the route for asking us to correct or remove a record. If your question is not listed, use the support contact shown in your account area.

It covers account details, phone verification, login and device signals, cookies, lobby activity linked to your account, wallet references and support messages. It also explains retention, security checks and requests for access or correction.

We use the phone number connected to your account to support access checks, confirm account ownership and match a privacy request to the right record. We may request another verification step before discussing personal data.

Yes. The policy covers transaction references and status connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use these records to reconcile account requests and investigate payment questions.

Cookies can maintain your signed-in session, remember selected settings and support security checks. Browser controls let you manage them, but turning some off may require another login or reduce account-area functions.

You can request a copy through the support contact shown in your account area. State which records you want, such as login activity or wallet references, and complete the identity check required where local law permits.

Send a correction request through account support with the inaccurate field and the correct detail. We check the request against your account before changing it, and we may retain the earlier record when required.

You can ask about deletion through the account support route. We assess the request under local requirements; records needed for security, payment reconciliation, disputes or legal duties may remain for the required period.