Reference

kiwi288 Privacy Policy For Your Account

Your account records, wallet details and device choices stay connected to a clear Privacy Policy on kiwi288, so you can understand what we collect before opening the lobby.

Account dataWallet checksDevice controlsCookie choices
kiwi288 kiwi288 Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help Beside Your Account Path

A privacy question should not require you to search through the lobby. We provide a support route through the account area for requests about personal data, phone verification or a login record…

Account privacy request Use the account support route to ask what personal details are connected with your kiwi288 profile. We may ask for a phone verification step before discussing account data, helping us avoid sharing records with the wrong person.
Wallet data question If a DANA, OVO, GoPay or QRIS receipt appears in your account history, contact us through the cashier support path. Share the transaction reference only; keep your wallet PIN, one-time code and full bank credentials private.
Access and correction For a correction, deletion request or concern about a device record, send the account phone number and the change you want considered. We will explain any identity check and tell you when the request cannot be completed under local law.
HANDLING DETAILS

Inside kiwi288 Data And Cookie Controls

We keep this policy practical by separating account protection from payment matching and site measurement.

Account records

We use your phone number, verification result and login events to create and protect your account. These records help us confirm an access request and investigate a sign-in that does not match your usual device pattern.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the reference and status needed to match the request to your account. We do not need your wallet PIN to check whether a payment reached the cashier.

Device signals

A mobile browser or desktop session may provide device type, browser details and security signals. We use these details to maintain a login session and flag unusual access, not to inspect unrelated files or contacts on your device.

Cookies

Cookies can keep a session active and preserve a setting such as language or a recently opened policy page. Browser controls let you remove or restrict them, although some account and security functions may then need to be repeated.

Retention period

We keep personal data only for the period needed for account security, payment reconciliation, support handling and legal duties. When a record is no longer needed for those purposes, our process is to remove it or separate it from your account.

Changes and requests

You can ask us to access, correct or delete eligible personal data through the account support path. We may verify your phone first, explain any restriction, and provide the next step where a request depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account steps you are most likely to meet when using kiwi288 from Indonesia. We keep the wording tied to actual records, including phone verification, device sessions, cookie settings and payment references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. If your question is not listed, use the account support path.

It covers the personal data we use for account creation, phone verification, login security, payment matching, cookies and support. It also explains retention, correction and deletion requests, including situations where access depends on local law or where local law permits.

Your phone number links the account to a verification step and helps us confirm an access or privacy request. It can also help support locate the correct account when you ask about a login record or a DANA, OVO, GoPay or QRIS payment status.

Yes. We may keep the payment reference, selected rail and status needed to match a DANA or QRIS request with your account. We do not ask for your wallet PIN, one-time code or unrelated wallet content to perform that check.

A browser session may provide device type, browser details, session timing and security signals linked to a login. We use these details to keep access working and identify unusual activity; we do not inspect unrelated files, contacts or messages on your device.

Send the request through the account support path and include your account phone number, the data request and the correction you want. We may complete phone verification before responding, then explain what can be supplied or changed under local law.

We retain records for the time needed to protect account access, reconcile payment references, answer support requests and meet applicable legal duties. After that need ends, our process is to remove the record or separate it from direct account details.

Yes. Your mobile browser settings can restrict or remove cookies used for sessions, language choices and page preferences. If you clear them, you may need to repeat a login or verification step, while essential security checks may still operate.