Reference

Open kiwibet Legal terms with clarity

kiwibet Legal sets out how we handle account access, identity checks, local wallets and policy requests before you enter the lobby.

Account rulesData requestsLocal access
kiwibet Open kiwibet Legal terms with clarity
POLICY CONTACT

Contact support about Legal questions

A clear contact route matters when a Legal question affects your account or payment record.

Account access If phone verification blocks account access, send the account identifier through the support route shown beside your account area. We can explain which Legal condition applies and what account step is still required, while access remains subject to local law.
Wallet records For DANA, OVO, GoPay or QRIS questions, include the wallet name and payment reference rather than sharing a password. Our support path can connect the Legal request with the relevant cashier record and explain what can be checked.
Policy requests To ask about data access, correction or removal, identify the account and describe the request plainly. We use the contact path in your account to confirm ownership before discussing records, cookies or retention connected with your Legal request.
DATA PRACTICES

Explore how Legal safeguards your account

Legal handling is practical rather than hidden behind broad wording. We separate account credentials from payment references, use phone verification before account access, and keep security records when they are needed to…

Account data

We use the account details needed to create access, complete phone verification and respond to a policy request. Your account area is the starting point for corrections, and we may ask for matching details before changing records tied to your identity.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us trace a transaction without asking you to reveal a wallet password. Legal handling keeps the payment reference connected to the correct account and support request.

Cookies

Cookies can keep a signed-in session and remember choices made during account access. If you clear them on your phone or desktop, you may need to verify your account again. Our policy explains their role and how to raise a cookie question.

Security checks

Phone verification and account matching help us distinguish an owner from an unauthorised request. Never send a password through support. When a withdrawal or wallet record needs checking, we use the account and transaction details already linked to the request.

Record retention

Some account, security and payment records may need to remain available after a request because they support dispute handling or a legal obligation. We do not treat every record alike; ask through the policy contact route for the category and reason involved.

Change requests

You can ask us to correct account details, explain a stored record or clarify a policy condition through the support route in your account. We confirm ownership first, describe the next step, and apply access rules where local law permits.

Get answers about kiwibet Legal

These Legal answers address the questions you may search before opening an account or sending a policy request. We keep the wording tied to real account steps, Indonesian wallet references and the access rule that depends on local law. If your situation is not covered, use the account support route with the smallest useful set of details.

kiwibet Legal covers account opening, phone verification, account security, cookies, payment references, data requests and record retention. It also explains how to contact us about a policy concern. The page is intended to help you understand the conditions before using account access or the cashier path.

Access depends on local law and your location. Before opening an account, confirm that the service is permitted for you in Indonesia and that your account details are accurate. We may require phone verification before account access, and we cannot advise you to bypass a local restriction.

Phone verification helps connect an account request to the person who controls the stated contact detail. It can be required before account access and may also help us assess a data-change request. If the step fails, contact support through the account route rather than sending a password.

We use the payment reference, wallet name and account details needed to check a DANA or QRIS status. You should not send wallet passwords or private access codes. If you question a record, the support route can explain which payment detail is relevant to the Legal request.

Yes, you can ask about access to stored account data or request a correction through the policy contact path in your account. We confirm ownership before discussing records, then explain what can be changed, what may remain for a stated reason, and what step follows.

Cookies can keep your session active and retain choices made while you use the account on a phone or desktop. Clearing cookies may require another sign-in or phone check. If you want a cookie explanation or change, contact us through the account support route.

Send the account identifier, the decision wording and any relevant payment reference through the support route shown in your account. We can review the policy question against the available record and explain the outcome. Eligibility and access still depend on local law and account verification.