Reference

Privacy Policy for Indonesia accounts

Account creation on hawkbets uses one clear data set for your profile, device, wallet choices and session safety, with payment context for DANA, OVO, GoPay and QRIS.

DANA dataOVO walletGoPay sessionsQRIS receipts
hawkbets Privacy Policy for Indonesia accounts
HELP ROUTES

Privacy help through live channels

Privacy questions need a direct route, not a maze. Our live chat is open 10:00-02:00 WIB, and email requests can be sent to [email protected] with your account ID, phone number and the data request you want us to check. We may ask you to confirm a recent QRIS reference or the device used at login before changing personal details.

Team online

Live chat privacy queue

Use live chat from 10:00-02:00 WIB when you need help reading this Privacy Policy or checking a data request. We ask for your account ID first so private details are not shared with the wrong person.

Email record requests

Send privacy requests to [email protected] if you want a written trail. Include your account email, phone number and whether the request concerns profile data, device sessions or payment references from DANA, OVO, GoPay or QRIS.

Account security path

Open Account, then Security, then Sessions to check recent device access before contacting us. If a login looks unfamiliar, tell us the time, device type and payment rail used near that session.

ACCOUNT CARE

Data controls inside your account

Privacy controls work when you can see what is happening inside your own account. We keep the policy tied to real account steps: login checks, wallet records, cookie choices, device sessions and…

Data we collect

We collect the details you give during account opening, plus login time, IP area, device type and wallet references. This helps us match your profile with DANA, OVO, GoPay or QRIS activity when you ask for help.

Cookie choices

Cookies help keep your session open, remember language choices and flag repeated login attempts. You can clear cookies in your browser settings, then sign in again so the account can build a fresh session record.

Account access checks

When you sign in from a new phone, we may check device signals and recent payment activity. The Account > Security > Sessions path lets you compare login times before you ask us to close a session.

Payment references

DANA, OVO, GoPay and QRIS records are used to match deposits and withdrawals with your account. We keep payment references separate from public lobby activity so wallet checks stay tied to your profile only.

Retention period

We keep personal data only for account service, security checks, payment tracing and legal record needs. When data is no longer required, we remove it or reduce it so it no longer points back to you.

Change requests

You can ask us to correct profile details, check stored data or explain a payment record. We verify your identity first, usually through account ID, phone confirmation and a recent wallet reference.

Privacy questions before you join

This FAQ answers the privacy questions we hear before you open an account and after your first wallet activity. It focuses on account data, payment references, cookies, access checks and how to reach us. If your question involves eligibility, remember that access depends on local law and is available only where local law permits.

We collect the details needed to create and secure your account, such as name, contact data, login records, device type and payment references. We also record wallet context when you use DANA, OVO, GoPay or QRIS.

Payment references help us match deposits and withdrawals with your account and respond if you report a missing transaction. We use those references for wallet tracing, account safety and record checks, not for public display.

Yes. Contact live chat or [email protected] with your account ID and the detail that needs correction. We may confirm your phone number, recent login device or a QRIS reference before making the change.

Cookies keep your login session active, remember site choices and help us detect repeated access attempts. You can clear cookies in your mobile browser, but you may need to sign in again and confirm the device.

We keep data for account service, payment tracing, security checks and legal record needs. When a record is no longer needed for those reasons, we remove it or reduce it so it no longer identifies you.

Only team members who need the request to handle account service, wallet tracing or security review can access it. We keep privacy requests within controlled channels such as live chat records and privacy email records.

Open Account > Security > Sessions and check the time, device and location signal. Then contact live chat from 10:00-02:00 WIB or email [email protected] with the session details so we can check it.