Reference

Open the indoxx1 Privacy Policy

The indoxx1 Privacy Policy explains how we collect, use, protect and retain your account details while you access the lobby with DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPhone verification
Browse Our Lobby Read FAQ
indoxx1 Open the indoxx1 Privacy Policy
REQUEST A RESPONSE

Switch to the right privacy contact

A clear contact route helps you ask about the Privacy Policy without sending account details to the wrong place.

Policy contact form Use the support form beside our Privacy Policy to ask what account data we hold, why a field is needed or how a request is handled. Add your registered phone number only when necessary for account matching, and keep wallet passwords and one-time codes out of your message.
Account help path When a privacy question is linked to DANA, OVO, GoPay or QRIS status, open account help from the cashier path and describe the reference shown on your screen. We use that reference to separate a payment-status question from a request to change or remove personal data.
Security escalation If your sign-in looks unfamiliar, contact us through the account support path before sharing further details. We may ask for a phone verification step or recent account activity so we can protect the right record and keep another person from making a privacy request for you.
DATA HANDLING

Browse how indoxx1 handles privacy

We keep the Privacy Policy practical by linking each data category to a real account event: sign-in, phone verification, wallet selection, device access or a support request.

Account records

We use the details connected to your account to provide sign-in support, confirm phone ownership and match a request with the correct profile. If you open the lobby on a mobile browser, the session may also create device and access records used for account protection.

Payment references

A DANA, OVO, GoPay or QRIS request can create a reference, amount status and time record. Bank transfer and virtual account requests may carry a matching reference. We use these records to check whether the account action reached the intended wallet path.

Cookies and sessions

Cookies can keep a selected session, remember a consent choice and help us understand whether a sign-in page is working on your device. You can clear browser cookies through your device settings, although this may require another phone verification when you return.

Account protection

We use phone verification, sign-in events and device signals to help protect your account from access that does not match your normal activity. Never send a one-time code in the support form. Where local law permits, we may pause a request while ownership checks are completed.

Data retention

We keep records only for as long as they serve the account, payment, security or legal purpose described in the Privacy Policy. When a record is no longer needed for those purposes, we assess it for deletion or removal from active systems, subject to required records.

Changes and access

You can ask us to access, correct or clarify personal data through the policy contact form. Include the account phone number when needed for matching, describe the exact field, and tell us the change requested. We may verify ownership before responding or making an adjustment.

Ask about the Privacy Policy

These Privacy Policy answers focus on the account steps you are most likely to check before opening an indoxx1 account from Indonesia. They explain what we collect during phone verification, how wallet references are used, how cookies behave on mobile and how to request access or changes. If your situation depends on a local rule, access depends on local law and we will use the policy contact route to clarify the next step.

The indoxx1 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookie choices, support messages and payment references. It explains why we use each category, how we protect it, how long it may be retained and how you can request access or correction.

We use your phone number to create and locate the correct account, complete the phone verification step before access and respond to account requests. It can also help us check ownership when a privacy request concerns DANA, OVO, GoPay, QRIS or a transfer reference.

Our Privacy Policy does not make a wallet password or one-time code a support requirement. We may retain a payment reference, status and time for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, but you should never place secret credentials in a message.

Use the policy contact form and ask for an account data access request. State the registered phone number only when needed for matching, identify the data category you want checked and complete any ownership step we request. Handling remains subject to local law where applicable.

Yes. Send a correction request through the support form linked beside the Privacy Policy. Name the field that is wrong, provide the replacement detail and explain why it should change. We may verify your account first, especially when the request affects phone access or payment records.

Cookies may keep a session active, remember your privacy choice and help identify a technical sign-in issue. On a mobile browser, you can clear them in the browser settings. Clearing cookies may sign you out and can lead to another phone verification before account access.

We retain account, security and payment records for the period needed for the purpose described in the Privacy Policy, including account support, payment matching or required legal records. After that purpose ends, we assess the record for deletion or removal from active use.

Related Pages

indoxx1 Indonesia Account information FAQ Access guide indoxx1 Casino