Reference

Open kiwibet with a clear Privacy Policy

Your account details, device signals and wallet references are handled under the kiwibet Privacy Policy, so you can see what we collect and why before opening access.

Account data explainedWallet references clarifiedCookie choices availableMobile access supported
kiwibet Open kiwibet with a clear Privacy Policy
REQUEST HELP

Reach us about a privacy request

A clear contact route matters when you want to ask about your personal data, correct an account detail or question a wallet reference.

Account data request Use our account-help channel to ask what personal details are linked to your kiwibet account. Include your registered contact detail and the specific record you want checked, so we can identify the request without exposing another account.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks incorrect, send the payment date and reference shown in your account. We use that operational detail to locate the record while avoiding a request for your wallet password or security code.
Access correction When login or phone verification blocks a privacy request, explain the step that stopped you and the device path you used. We can direct the request through account help without asking you to publish private details in a public message.
DATA HANDLING

Browse kiwibet privacy controls

We keep this policy practical by linking each privacy topic to an account action you can recognise.

Account details

We use details entered during account opening, such as your contact information and phone verification status, to create and protect access. We do not need your DANA, OVO or GoPay password to match a wallet-related reference with the correct account.

Device signals

When you move from login to the lobby on a phone, tablet or desktop, technical signals such as browser type, operating system and connection details may be recorded. These signals help us investigate unusual access and explain device-specific privacy questions.

Cookie choices

Cookies can keep an account session working and help us understand whether a page loads correctly. Your browser controls can restrict or remove them, although changing those settings may affect login continuity and the way policy pages open on your device.

Account security

Phone verification and account checks help us distinguish your request from an unauthorised attempt. If you access Live Roulette Prestige from a new device, we may use the related security signal to review the access event before discussing account data.

Record retention

We retain account, security and transaction references only for the period needed for account operations, dispute handling, security checks or legal duties. Retention can differ by record type, and a deletion request may be limited where a record must remain available.

Changes and contact

You can ask us to correct contact details, clarify a data category or explain a cookie choice through the account-help route. Include the affected account step, such as phone verification or QRIS status, so our reply addresses the right record.

Check Privacy Policy answers

These Privacy Policy answers address the searches we expect before an Indonesian customer opens an account or sends a wallet-related request. They cover the data used at login, device behaviour, cookies, payment references, correction requests and access wording. If your question is not answered here, use the account-help route with the smallest set of details needed to identify your request.

The kiwibet Privacy Policy covers account details, phone verification, device and browser signals, cookies, security records and payment references. It explains why we use each category, how retention works and how you can ask for correction or clarification.

Our policy distinguishes wallet references from wallet credentials. A DANA or GoPay transaction reference may help us match an account event, but you should not send a wallet password, one-time code or private security credential through account help.

A QRIS reference, amount status and related account detail may be used to check whether a payment request matches your account. We use those operational records for support and security checks, while the retention period can depend on the record type.

Yes. Send a request through the account-help path and identify the registered phone or email, then specify whether you want access, correction or an explanation. We may complete phone verification before discussing private account records with you.

Cookies can preserve a session and help us identify whether login or a policy page loads correctly. You can change cookie settings in your browser, but blocking some cookies may require another login or interrupt the path from account access to the lobby.

We keep each record for the period needed for account operation, security checks, dispute handling or legal duties. Account details, device signals and transaction references can have different retention periods, so a deletion request may not remove every record immediately.

The policy is written for Indonesian account access, but eligibility and access depend on local law. Where local law permits, we apply the stated data practices; if a local rule affects your request, account help can explain the relevant limitation.