Reference

Open hebat303 Privacy Policy Before Account Access

Lightning Roulette, Aviator and Fish Hunter are available through an account path that also explains how we handle your data.

Account dataWallet recordsCookie choicesAccess requests
hebat303 Open hebat303 Privacy Policy Before Account Access
CONTACT ROUTES

Contact Us About Privacy Policy Records

A clear contact route helps you ask about the Privacy Policy without sharing sensitive details in an open message. From your account help path, include the registered phone number in partial form, the topic you are asking about and the relevant date. If a wallet record is involved, refer to the payment rail and receipt reference rather than sending a full password or security code.

Team online

Account help path

Use the account help path to ask how your personal details are stored, corrected or linked to a phone verification step. We can locate the request more accurately when you provide the account email or registered number in partial form.

Receipt and wallet query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the date, rail name and receipt reference. Keep passwords, one-time codes and complete wallet credentials out of your message.

Browser access request

If a mobile browser cannot reach the privacy contact path, switch to the account support panel and describe your device type, browser and last access time. We use those details to separate a technical issue from an account-data request.

DATA PRACTICES

Explore How Privacy Policy Controls Data

We apply the Privacy Policy to the information needed for account access, wallet matching and security checks, while keeping requests tied to a specific account record.

Account details

We may hold your registration details, phone verification status and sign-in history so we can connect an account request to the right record. We ask you to keep these details accurate when your account step changes.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account can be checked against an account record. We use the reference to resolve status questions without requesting your private wallet password.

Cookie controls

Cookies can remember a browser preference and help identify an unusual access pattern. You can manage browser cookie settings, but changing them may require another sign-in or limit the privacy contact path shown on your device.

Security checks

Phone verification and sign-in checks help us distinguish your account from an unfamiliar device. Never share a password or one-time code with support; describe the access problem through the account help path instead.

Retention period

We retain account, payment-reference and support records only for the period needed for account administration, security review and applicable local requirements. A deletion request may not remove records that must remain available for those purposes.

Change requests

You can ask us to correct personal details, explain a data use or request removal of eligible records. Include the account identifier and request type; we may verify ownership before making a change.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and wallet questions we hear most often from Indonesian customers. They cover what we collect, how you can reach us, what happens when you change devices and which account step may be needed before we disclose or alter a record.

It covers account details, phone verification, sign-in records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps us connect an access request to the correct account and detect an unfamiliar sign-in. We may ask you to confirm ownership before discussing personal details or changing a record.

Yes. Send a correction request through the account help path with the affected detail and account identifier. We may verify ownership first, then assess the request under this Privacy Policy and local requirements.

We use the payment rail, date and receipt reference to match a wallet status with your account. Do not send a wallet password, one-time code or complete private credential in a support message.

Yes. It explains that cookies can remember settings and help identify unusual access patterns. You can change cookie controls in your mobile browser, although another sign-in or a limited contact path may follow.

Retention depends on the record type and the time needed for account administration, security review and applicable local requirements. You may request clarification, though some records may need to remain available.

You can ask us to remove eligible data through the support route. Include your account identifier and request details; we first confirm ownership and then check whether any retention duty applies.