Reference

hawa303 Privacy Policy for Your Account Data

Our Privacy Policy explains how hawa303 handles the account details, device signals and wallet records connected with your access to Sic Bo, Rocket Crash and other lobby areas.

Account data explainedWallet records clarifiedDevice access coveredContact paths included
hawa303 hawa303 Privacy Policy for Your Account Data
CONTACT YOUR WAY

Get Privacy Policy Help Through Account Support

A clear contact route matters when you want to ask about your Privacy Policy rights or a record linked to your account.

Account help route Use the account help path for Privacy Policy questions, correction requests or access concerns. Include your registered contact detail so we can match the request with the correct hawa303 account.
Wallet status request If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, share the transaction date and status shown to you. Do not send your password or security code.
Device access query Tell us whether the request came from your mobile browser or desktop path and describe the sign-in issue. That context helps us check device records without asking for unnecessary personal details.
HOW DATA WORKS

Privacy Policy Details You Can Check

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Account collection

During account creation, we collect the contact and verification details needed to identify your profile. A clear phone verification step can be required before account access is completed.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain practical references such as status, time and route so wallet questions can be checked.

Cookie controls

Cookies can keep a session active and remember necessary browser settings. You can adjust cookie controls in your browser, although turning them off may affect account sign-in steps.

Device signals

We may record browser type, device signals and login times to spot unusual account activity. These signals help protect access and are not treated as a complete identity profile.

Retention approach

We keep records for as long as needed to provide account support, check transactions, resolve disputes and meet applicable obligations. When a record is no longer needed, we remove or restrict it.

Your change request

You can ask us to access, correct or clarify personal data linked to your account. Send the request through account support, and we may verify ownership before making a change.

Privacy Policy Answers for hawa303 Accounts

These Privacy Policy answers address the searches we hear most often from people checking account access in Indonesia. They explain what we collect, why wallet references appear, how device records work and which steps help us respond to a personal request. If your situation is unusual, use the account support path with only the details needed to locate your record.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with your use of the service. It also explains request, correction and retention processes.

When you use DANA or QRIS, our records can include a route, status, time and transaction reference. We use those details to investigate wallet questions without storing your private wallet password.

We do not ask you to send an OVO or GoPay password through support. Wallet-related records are limited to practical status and transaction references needed to check an account question.

Yes. Send a request through account support using the contact detail attached to your profile. We may confirm account ownership first, then explain which personal records can be provided.

Contact us through the account help path and identify the detail that needs correction. Include the registered phone number or email, but never include your password or one-time security code.

We may use browser type, device signals and login times to examine unusual access or repeated sign-in failures. These records support account protection and are handled separately from your payment password.

Yes. Where access or eligibility is discussed, it depends on local law. We apply this wording to account availability and can explain a policy question through the support path.