Reference

Privacy Policy for Your kiwi33 Account

Our Privacy Policy explains how kiwi33 handles the account, device and payment details you provide before you enter the lobby.

Clear data purposesWallet detail contextAccount request path
kiwi33 Privacy Policy for Your kiwi33 Account
PRIVACY HELP PATH

Get Policy Help Beside Account Access

A clear contact path matters when you need an answer about the Privacy Policy rather than a wallet status update.

Policy request Send a Privacy Policy question through our account help path and tell us whether…
Wallet reference For DANA, OVO, GoPay or QRIS questions, include the payment reference rather than a…
Access check If a privacy request follows a login concern, we may ask you to confirm…
DATA HANDLING

What Our Privacy Process Covers

The Privacy Policy is supported by practical controls across account access, device use and payment records.

Account details

When you open an account, we use the details you submit to create the profile and support phone verification before account access. The Privacy Policy explains the purpose of each requested field.

Device signals

A mobile browser may send device and login signals that help us recognise a returning session or investigate an unusual sign-in. These signals are handled for access and security purposes described in the policy.

Cookies

Cookies and related storage can remember a session choice or help us understand whether a page request completed. You can ask how a particular cookie is used and whether an available browser control affects access.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may appear in account records. We use those references to match status and receipts, not to request your wallet password.

Retention

We keep records for the period needed for the stated purpose, account support and applicable legal duties. The Privacy Policy explains retention categories, and you can ask which category applies to your record.

Change requests

To request access, correction or removal of personal details, contact us through the policy help path with your account identifier. We may verify ownership before changing or disclosing a record.

Privacy Policy Answers For kiwi33

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data connected with login, mobile access, payment references, cookies, retention and requests for correction or removal. If your question concerns a particular record, include the account detail or payment reference that identifies it, while leaving out wallet passwords. Access depends on local law and applies where local law permits.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention and the way you can request access or correction.

We use phone verification before account access to help confirm that the person requesting entry matches the account record. The Privacy Policy explains this purpose and the related handling. If a detail is inaccurate, contact us through the policy request path.

Yes. The policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a status or receipt with your account. We do not need your wallet password for that matching process.

You can request access to the personal data connected with your account by using the policy help path. Include your account identifier and the record you want clarified. We may complete an ownership check before discussing private details or sending a copy.

Send a correction request through account help and identify the field that needs changing, such as a contact detail or account record. We may ask for verification before editing it, then explain whether the requested change can be made.

Retention depends on the type of record and the reason it was collected, including account support, payment matching and applicable legal duties. Our Privacy Policy sets out the relevant categories. You can ask us which retention category applies to your information.

Yes. It covers data created when you sign in through a mobile browser, including session details, device signals and cookie choices. Access depends on local law. If you want a device record clarified, mention the affected account session in your request.