Reference

Privacy Policy for Your Wallet And Account

DANA, OVO, GoPay and QRIS details stay connected to the account steps you choose, and our Privacy Policy explains how kiwi123 handles that data.

Account clarityWallet data scopeMobile accessPolicy contact path
kiwi123 Privacy Policy for Your Wallet And Account
CONTACT THE DESK

Where Privacy Questions Meet Account Support

A clear support route helps you ask about Privacy Policy records without explaining your full account history in public.

Account privacy request Use the support path inside your account when you want to ask what personal…
Wallet record check If your question concerns DANA, OVO, GoPay or QRIS, name the wallet and the…
Access and device help When a privacy request follows a sign-in problem, tell us whether you used a…
SIX CONTROL POINTS

Inside kiwi123 Data Handling And Security

Privacy Policy choices are easier to understand when each control has a practical purpose.

Account details

We use the details you provide during account opening and phone verification to create access, connect your account to requested…

Wallet references

DANA, OVO, GoPay and QRIS references are treated as payment context rather than public profile content.

Cookies and sessions

Cookies or related browser storage can keep a sign-in session working, remember selected settings and help identify unusual access.

Account security

We use session signals, phone verification and access checks to reduce the chance of another person entering your account.

Retention purpose

We retain account, support and payment records only for operational, security or legal purposes described by our Privacy Policy.

Change requests

You can ask us to correct an inaccurate account detail, explain a data use or review a request connected with…

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the account and wallet questions you may have before opening access on kiwi123. We keep the wording practical: what is collected, how mobile sessions work, what payment references mean and where to send a request. For eligibility or access, the relevant position is always that access depends on local law and is available where local law permits.

The Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use each category, how security checks work and how you can ask about, correct or request changes to information linked with your account.

Yes. Privacy Policy handling includes the references needed to identify a DANA, OVO, GoPay or QRIS payment status. It can also cover bank transfer and virtual account records. We use those references for account matching, status checks, support and required record keeping, not for wallet PIN access.

When you sign in from a phone or desktop browser, we may record session and security signals needed to keep access working and identify unusual activity. Clearing browser storage can end a session. The Privacy Policy explains how these technical records support account protection.

Send a correction request through the account support path and describe the detail that appears wrong. Include the account contact used for access so we can check ownership before changing anything. We assess requests under the Privacy Policy and applicable local requirements.

Retention depends on the record and its purpose. Account, payment and support records may be kept for security, service operation or legal reasons described in the Privacy Policy. We do not promise one period for every category, and removal requests may have limits.

Yes. Ask through account support and identify the wallet type, such as DANA or QRIS, without sending a PIN or one-time code. We can explain the relevant Privacy Policy purpose, including payment matching, status checks, security review or required record keeping.

The Privacy Policy is written for account and data handling where local law permits. Access depends on local law, and certain requests or services may follow rules connected with your location. Contact account support if you need the policy position checked for your access route.