Reference

indojp Privacy Policy Explained Clearly

The indojp Privacy Policy explains what we collect when you open an account, verify your phone and use the lobby, including records linked to DANA, OVO, GoPay and…

Account dataWallet referencesDevice choicesPolicy requests
Explore Our Lobby Read FAQ
indojp indojp Privacy Policy Explained Clearly
REQUEST A HAND

Where To Ask About Privacy

A clear support route helps when you want to ask about a record, correct an account detail or understand why a wallet reference appears in our systems. Start from your signed-in account support path and include the phone number linked to your account, the relevant date and the payment reference, while leaving out any password or one-time code. If you cannot sign in, use the account-access support path and identify yourself with details we can verify. We handle requests about the Privacy Policy as data questions, not as general lobby enquiries.

Team online

Account support path

Use the support link inside your account to ask what data we hold, why a phone check was requested or how to correct a profile detail. Include your account phone number and a short description, but never send your password or one-time verification code.

Payment record query

For a DANA, OVO, GoPay or QRIS record, send the date, amount reference shown in your account and the wallet route used. We can compare that reference with the account event without asking you to disclose your wallet password or private security code.

Sign-in privacy request

If device activity or a failed phone verification looks unfamiliar, contact us through the account-access support route. Tell us which device and approximate time were involved so we can check the security event and explain the next account step.

DATA CONTROL MAP

Six Ways We Handle Your Details

We keep the Privacy Policy practical by linking each data type to an account action you recognise.

Account creation

When you open an account, we use details such as your phone number and chosen account credentials to create the profile and complete the phone verification step. We do not need your wallet password to connect a DANA, OVO, GoPay or QRIS reference.

Device signals

Browser type, device identifiers, approximate network details and sign-in times can help us spot an unusual access pattern. These signals are reviewed alongside account events, especially when a new device attempts to enter the account or repeat a failed verification.

Cookie choices

Cookies can keep a session active, remember a language or preserve a setting on the device you use. You can clear browser cookies through your device settings, although doing so may require another sign-in and may remove saved preferences.

Payment references

A wallet, bank transfer or virtual account event may create a reference, status and timestamp in our records. We use those details to match the account action, investigate a receipt question and check whether the requested transaction reached the correct account.

Security controls

We limit account data access to the operational purpose involved, use verification before discussing private records and inspect unusual sign-in patterns. Keep your password and phone verification codes private; our support path should not require either one from you.

Change requests

You can ask us to correct inaccurate profile data, explain a processing purpose or request removal where the law allows. Send the request through account support with enough detail to identify the record, and we may need to verify that you control the account.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the questions we expect when you are deciding whether to open an account or connect a local wallet. They explain the account step, the records created by DANA, OVO, GoPay, QRIS and bank routes, and the practical way to contact us. For access or eligibility matters, the applicable position depends on local law.

It covers data collected when you open an account, complete phone verification, sign in, use the lobby or request a payment action. It also explains cookies, device signals, wallet references, retention, security, sharing with necessary service providers and how to send a privacy request.

We use your phone number to create and identify the account and to complete the phone verification step before account access. It can also help support locate the correct record. Do not send your password or one-time code when asking about the Privacy Policy.

Yes. The Privacy Policy covers references, statuses and timestamps returned by DANA, OVO, GoPay and QRIS when you request an account payment action. We use those records to match activity and investigate receipt questions, not to request your wallet password.

We may receive browser type, device signals, approximate network details and sign-in times. These details help us inspect unusual access, such as a new device or repeated failed verification. They are considered alongside account events rather than treated as a full personal profile.

We retain each record for as long as needed for its stated purpose, account security, payment questions, dispute handling or legal duties. A request to remove eligible data can be sent through account support, and we will explain if a record must remain.

You can ask us to correct inaccurate account details, explain a data use or remove eligible records through the signed-in support path. Include your account phone number and the specific request. We may verify account control before changing or releasing private data.

Use the account-access support path and provide the phone number linked to the account, the approximate sign-in time and the device involved. We can check the request after verification. Access or eligibility depends on local law, and private security codes should never be shared.

Related Pages

indojp Indonesia Register Mahjong Ways Live Dealer Lobby FAQ