Reference

hinototo Privacy Policy for Your Account

The hinototo Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account clarityWallet recordsDevice controlsPolicy requests
hinototo hinototo Privacy Policy for Your Account
CONTACT ROUTES

Ask About Privacy Beside Wallet Help

A clear contact route helps when your Privacy Policy question sits beside a login or wallet issue. Tell us the account step involved, such as phone verification, a QRIS receipt, or a pending DANA status, without sending passwords or full payment credentials. We use the details you provide to locate the relevant record and keep the request focused.

Team online

Account request

Ask which account data we hold, how it was collected, or why phone verification is required. Include your registered contact detail so we can locate the correct record without asking for your password.

Wallet query

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and approximate time shown on your receipt. We can compare the wallet status with the account record while limiting unnecessary payment data.

Access concern

If a sign-in or device path raises a privacy concern, describe the handset and browser step you used. We will use that report to check account protection signals and explain the next request step.

HANDLING PRACTICES

What We Do With Your Data

Your Privacy Policy rights are easier to use when our handling steps are clear. We separate account access records from the payment references needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer…

Collected for account steps

We collect registration details, phone verification results, sign-in events and selected account activity so we can connect a request to your account. We avoid asking for unrelated details when handling a Privacy Policy request.

Payment references

Wallet and bank records can include a method name, reference, amount status and timestamp. We use these fields to reconcile DANA, QRIS or virtual account activity, not to create a separate profile about you.

Cookies and sessions

Cookies and similar session tools help remember sign-in state, language choices and page continuity. You can manage browser storage through your device settings, although clearing it may require phone verification again.

Device protection

We may assess device and session signals when an account opens from a changed handset or browser. These checks help us identify unusual access without treating your device model as a payment credential.

Retention decisions

We keep records only for the period needed for account protection, transaction reconciliation, dispute handling and legal duties where local law permits. When a record no longer serves those purposes, our process can remove or de-identify it.

Changes and requests

You can request a copy, correction, restriction or deletion assessment through our contact route. We may ask for account verification before making a change, so private data is not released to the wrong person.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account and wallet questions you are most likely to search before opening an account. They cover access, device records, payment references, cookies, retention and the steps for asking us to change or remove data where local law permits.

It covers account registration, phone verification, sign-in activity, device signals, cookies, wallet references, support requests and records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account use.

Phone verification helps connect account access to the correct person and supports account protection when a new device or browser appears. We use the result for that access purpose and related security checks.

Yes. The Privacy Policy covers payment references such as method, transaction reference, status and time for QRIS, DANA, OVO and GoPay, so we can reconcile an account record without needing your wallet password.

You can contact us through the privacy support route and ask for the account data connected to your registered contact. We may verify your identity first before preparing a copy or explaining any restriction.

Send a correction request with the account step and field that appears wrong, such as a phone detail or wallet reference. We may ask for verification, then assess the change against active account and payment records.

Retention depends on the purpose: account protection, payment reconciliation, dispute handling or legal duties. Where local law permits, records are removed or de-identified when they are no longer needed for those purposes.

You can ask us to assess deletion through the contact route. Some records may need to remain for account security, transaction reconciliation or legal duties, and we will explain the applicable reason where local law permits.