Reference

Privacy Policy for Your hujanwd Account

hujanwd Privacy Policy explains how we collect, use and protect the details connected to your account, wallet status and access to the lobby.

Account recordsWallet activityCookie choicesContact requests
hujanwd Privacy Policy for Your hujanwd Account
PRIVACY CONTACTS

Get Help With a Privacy Policy Request

A clear contact route helps when your Privacy Policy question concerns a phone check, wallet reference or stored device session.

Account message Send a privacy request through the signed-in account path when you can access it. We use the account step to connect your request with the correct phone verification record and reduce the chance of changing another person’s details.
Email request Email our support channel when sign-in is unavailable. Include your account identifier and the request type, but do not send a wallet PIN or full bank credentials. We reply during the stated 09:00-22:00 Jakarta service window.
Status assistance If a DANA, OVO, GoPay or QRIS reference appears incorrectly, tell us the date, amount reference and account identifier. We check the payment record and privacy log together before explaining what can be corrected or removed.
DATA CONTROL POINTS

What You Can Check Inside Our Privacy Policy

Privacy Policy choices are easier to use when each data purpose has a clear route. We separate account security records from preference cookies, and we use access checks before discussing a private…

Data collection

We collect account details you submit, phone verification results, sign-in timestamps, device indicators and payment references needed to operate the account. A DANA or QRIS reference helps us reconcile activity without displaying your wallet credentials to another account.

Cookie settings

Cookies can keep a mobile session active, remember language or display preferences, and help us identify repeated sign-in failures. You can request details about these cookies and ask support how to change settings without sending your wallet PIN.

Account security

We record security events such as a new device sign-in or a phone verification attempt. When a sensitive change is requested, we may require an account step before updating contact data, wallet status or access credentials.

Payment references

Our records may show a transaction reference, status and matching account for DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity. We do not ask you to place a wallet PIN or full banking password in a support message.

Retention checks

We keep records for the period needed for account operation, security checks, dispute handling or legal duties. When a record no longer serves one of those purposes, our process removes it or changes it so it no longer identifies you.

Change requests

You can ask us to access, correct or delete eligible account data, or ask why a record is retained. We may verify your identity through the account path or phone step before completing the request and will explain any limit clearly.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the questions we hear before an Indonesian account is opened or used on mobile. They explain how hujanwd connects account security, device behaviour and payment references without turning a support request into a request for sensitive wallet credentials. If your situation is not covered, contact us through the account or email route and state the exact privacy action you want.

The hujanwd Privacy Policy covers account details, phone verification, sign-in and device security events, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity. It also explains retention, access requests, corrections and deletion requests.

We use phone verification to help confirm account ownership and protect changes to sensitive details. A verification result can be linked to sign-in security and support checks, but you should never send a wallet PIN or full banking password in a message.

Yes. Our Privacy Policy covers payment references and status details used to match DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity with your account. These records help resolve a status question without requiring us to store your private wallet PIN.

Send a request through the signed-in account path, or use our email support route when you cannot sign in. State that you want an access request and provide the account identifier needed to locate your record. We may complete a phone or account check first.

Yes. You can ask us to correct eligible contact, phone or account details through support. Explain which field is wrong and what should replace it. We verify the request before making a sensitive change, so another person cannot redirect your account or wallet status.

We retain records only while they support account operation, security checks, dispute handling or legal duties. Retention can differ by record type. When the purpose ends, we remove or anonymise the record under our process, subject to duties that require continued storage.

Our Privacy Policy applies to the personal data handled through the account and related support routes. Access or eligibility depends on local law and the location linked to your account. Contact us if you need a privacy answer for your specific access situation.