Reference

Open Your kirbet Privacy Policy Path

kirbet Privacy Policy sets out how we collect, use and protect the details connected with your account, including phone verification and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
kirbet Open Your kirbet Privacy Policy Path
CONTACT ROUTES

Browse Privacy Help Before Contacting Us

A clear support path helps you resolve a privacy question without repeating your account history. Start from the support route available after you sign in, and include the email or phone detail linked to your account. We may ask for an account step or verification detail before discussing records. That check protects you when a wallet receipt, QRIS reference or device session needs attention. If you are in Medan or elsewhere in Indonesia, use the same account privacy route; local access still depends on local law.

Team online

Account privacy request

Use the signed-in support path to ask what account data we hold, why we use it or which records relate to your phone verification. We respond through the contact route attached to your account and may request a matching detail before sharing private records.

Wallet data check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference through support rather than posting wallet details in a public message. We can compare the payment record with your account while limiting disclosure to the person who passed verification.

Security concern

Tell us promptly if a sign-in, device session or account change was not yours. We can review the relevant access record, guide you through an account check and place the privacy request with the right support contact without asking you to share a password.

DATA PRACTICE

Switch Through kirbet Privacy Controls

We handle privacy as part of each account step, from the first phone check to a later wallet status query.

Collection

We collect details needed for account access, security checks, support and payment matching.

Use of data

We use account data to authenticate you, protect sessions, investigate wallet status and answer privacy requests.

Cookie control

Cookies can preserve a sign-in session, remember a selected setting or help us detect unusual access.

Account security

Phone verification, sign-in records and device checks help us distinguish your account activity from an unauthorised attempt.

Retention

We retain different records for different periods according to their purpose, including security, payment reconciliation, dispute handling and legal duties.

Change request

Ask us to correct, access or delete eligible data through the account privacy support route.

Check Your kirbet Privacy Policy Answers

These Privacy Policy answers cover the questions we expect you to ask before opening an account or contacting support. They explain the data connected with wallet activity, browser access, game pages and account security. If your request concerns a specific record, include its date, reference or account step so we can locate it without asking for a password. Where a legal rule affects access, our response will explain that the outcome depends on local law.

The kirbet Privacy Policy covers data used for account creation, phone verification, sign-in security, support and payment matching. It also explains cookies, retention and your request rights. The policy applies when you access pages or account functions from an Indonesian device where local law permits.

We may keep payment references and status details needed to match your account activity with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those records for reconciliation, support and security checks, rather than asking you to send a wallet password.

Use the privacy support route connected with your signed-in account and state that you want an access request. Include the account contact detail and the type of record you need. We verify your identity first, then explain what can be provided under applicable law.

Yes, you can request correction when a contact detail, verification status or payment reference is inaccurate. Send the request through account support with the relevant account step or receipt reference. We may ask for a matching check before changing data tied to your account.

The Privacy Policy explains that cookies can support sign-in continuity, selected settings and unusual-access checks. Your browser provides controls for cookie storage. If you remove or block cookies, you may need to repeat phone verification or sign in again to submit a privacy request.

You may ask us to delete eligible personal data through the privacy support route. We first verify the request and check whether a record is still needed for payment reconciliation, security, disputes or legal duties. If deletion is limited, we explain the reason and next available step.

Yes. Some access, correction or deletion outcomes depend on local law. We assess your request against the rules that apply to the account and region, confirm your identity and tell you which action we can take. The same wording applies when account eligibility is discussed.