Reference

indohoki4d Privacy Policy Explained Clearly

Our Privacy Policy explains what indohoki4d collects when you open an account, sign in from a phone, or check wallet status through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice signalsCookie choices
indohoki4d indohoki4d Privacy Policy Explained Clearly
CONTACT YOUR WAY

Get Privacy Help Near Your Account

A privacy question should not require searching through the lobby. Use the support path shown inside your account to ask about a data record, cookie choice, phone verification or wallet receipt. We keep the request connected to the correct account so our team can check the relevant status without asking you to post private details publicly. The same route is available when you are signing in from Surabaya or elsewhere in Indonesia.

Team online

Account privacy request

Send a request through the account support path and include the email or phone detail linked to your profile. We use that step to locate the correct record before responding.

Wallet data question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the receipt reference rather than wallet credentials. We can trace the status while limiting exposed payment data.

Sign-in concern

If a phone verification prompt or unfamiliar device blocks account access, contact support through the sign-in path. We may ask account details to confirm that the request is yours.

DATA HANDLING

What We Do With Your Account Data

Our privacy process follows the account journey rather than treating every record the same. Registration data supports account setup, device signals help identify unusual sign-ins, and payment references help match a receipt…

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification before account access. We use those details to maintain the correct account record.

Device behaviour

A phone or desktop sign-in can create technical records such as browser type, session time and security signals. These help us detect unusual access without reading private content on your device.

Cookie choices

Cookies can keep a session active, remember a language or preserve a page setting. You can remove or restrict them in your browser, although some account steps may then need repeating.

Wallet references

We retain payment references and status results for DANA, OVO, GoPay, QRIS and bank rails, not your wallet password. This lets support match a receipt while reducing sensitive payment exposure.

Retention periods

We keep account and support records for the period needed for security, service administration or a legal request. When a record is no longer needed, our process removes or separates it.

Your requests

You can ask for a copy, correction or deletion assessment through the account support path. We may verify your identity first, then explain what can be changed under applicable local law.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account, device and wallet questions we hear before registration. They also explain the practical path for contacting us, checking a record or changing a preference. If your request concerns eligibility or access, the answer depends on local law and the location connected with your account.

It covers account details, phone verification, sign-in and device records, cookie settings, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank rails.

Phone verification helps connect account access to the correct person and identify unusual sign-in requests. We use the result for account protection, not to request your wallet password.

Yes. The policy covers payment references and status results linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. It does not require your private wallet credentials.

Use the support path inside your account and ask for a data copy. Include the account email or phone detail so we can verify the request before returning records where local law permits.

Yes. Send a correction request through account support and identify the field that needs changing. We may confirm your identity, then update eligible records or explain the applicable restriction.

Cookies can keep your session active and remember device settings. Browser controls let you remove or restrict them, but signing in again or repeating phone verification may be required afterward.

Retention depends on the purpose of the record, including account security, support handling and legal duties. When a record is no longer needed, we remove it or separate it from active account use.