Reference

Privacy Policy For Your hura500 Account

hura500 Privacy Policy sets out what we collect when you open an account, sign in from a mobile device, or check wallet status for DANA, OVO, GoPay and…

Account dataDevice choicesWallet recordsYour requests
hura500 Privacy Policy For Your hura500 Account
CONTACT PATHS

Ask About Privacy Policy Through Support

A clear contact route matters when you need to understand or change personal data held by your account.

Account desk For a copy of account data or a correction request, contact support through the account help channel during the published support hours. We may ask you to complete phone verification before discussing records, so a request is connected to the right hura500 account.
Wallet status If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference and date through support. We use the reference to locate the status record, while you should keep wallet PINs, passwords and one-time codes private.
Access questions For questions about a sign-in event, device record or account closure, use the support contact shown beside the account path. We can explain the relevant Privacy Policy section and tell you what verification is needed before changing stored details.
DATA PRACTICES

What We Keep And Why It Matters

Privacy Policy choices are easier to assess when each data use has a practical reason. We separate account access records from wallet references, limit staff access to the task being handled, and…

Account details

We collect the details needed to create and maintain your account, such as contact data and phone verification status. This lets us connect your sign-in to the correct account and respond to a data request without relying on a public display name alone.

Device signals

When you sign in from a phone or desktop browser, we may record device and session signals such as browser type, time and security events. These records help us investigate unusual access; they are not a request for access to your photos or device files.

Cookies

Cookies and similar storage can keep a session active, remember a selected language or connect a sign-in step. You can manage browser storage through your device settings, though clearing it may require phone verification again before account access continues.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use transaction references and status details to reconcile the account record. We do not ask you to provide a wallet PIN, password or one-time code to our support team.

Retention checks

We keep account, support and transaction records only for the period needed for account operation, dispute handling, security checks and legal obligations. When a record no longer has a valid purpose, our process removes it or separates it from direct account identifiers.

Change requests

You can ask us to access, correct or clarify personal data connected with your account. Include the phone number and request in your message; after verification, we will explain the available action, any necessary exception and the next step for completing it.

Privacy Policy Answers For Indonesia

These Privacy Policy questions cover the account and device situations most often raised before opening or using hura500. Each answer stays focused on personal data, wallet references, access records and the support path available where local law permits.

The hura500 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and transaction references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use each category and how you can ask about it.

We may collect the contact details needed for account creation, your phone verification status, sign-in events and security records. The exact fields depend on the account step and local requirements. We use them to connect access to your account and handle requests about your data.

Our Privacy Policy does not require you to send a wallet password, PIN or one-time code to support. We may retain a payment reference, status and related account context for reconciliation. If a message asks for secret wallet credentials, do not provide them through the support path.

Contact the account help channel with the phone number linked to your hura500 account and state whether you want access, correction or clarification. We may complete phone verification before responding. A transaction reference can help with wallet records, but it should not include a password or PIN.

Device and browser signals help us identify unusual sign-ins, keep a session connected and investigate account access concerns. They can include browser type, session time and security events. We do not need access to your photos or device files for the account process described in this Privacy Policy.

We retain records for the period needed to operate the account, answer a support request, investigate security events, resolve a transaction dispute or meet a legal obligation. After that purpose ends, our process removes the record or separates it from direct account identifiers.

You can contact support to ask about account closure and deletion of personal data. We will verify the request, explain which records can be removed, and identify any information that must remain for security, dispute handling or legal obligations. Access still depends on local law.