Reference

Open the kastawin Privacy Policy for Wallet Data

kastawin Privacy Policy explains how we use account, phone, device and payment records when you open an account, verify your phone or access the lobby.

Account dataWallet recordsDevice choicesPolicy requests

Explore Our Lobby Read FAQ

Explore How We Use Account Data

kastawin Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy sets out what we collect, why we use it and how you can ask about it. When you create an account, we may record your name, phone number, verification result and login events so we can connect access to the correct account. Payment

1
records can include a DANA, OVO, GoPay or QRIS reference, plus bank transfer or virtual account details needed to match a transaction. We also receive device, browser and security event data when you sign in or switch between the lobby and account area. We use these
2
records to provide access, check payment status, prevent account misuse and respond to policy requests. We retain records only for operational, dispute or legal needs, then remove or anonymise them under our internal process. Where local law permits, you may request access, correction or deletion, subject
3
to identity checks and records we must retain.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP

Browse Policy Support From Your Account

A clear request path helps you resolve a Privacy Policy question without sending payment details through an unrelated channel. Start from your account help area, state the email or phone linked to your account, and describe whether the request concerns access, correction, deletion or a wallet record. We may ask for verification before discussing personal data or changing account records.

Team online

Account help

Use the account help route when you need to ask what personal data is linked to your phone verification or when login records appear unfamiliar.

Wallet status

For a DANA, OVO, GoPay or QRIS record, include the transaction reference and date so we can match the payment entry without requesting your wallet password.

Policy request

Ask for access, correction or deletion through the policy request path. We confirm account ownership first and explain any record that must remain for legal or dispute needs.

DATA HANDLING

Switch Through Your Privacy Choices

We keep Privacy Policy decisions tied to practical account actions: phone verification, sign-in security, wallet matching and device access.

Account records

We use your phone number, verification result and sign-in history to associate access with one account and investigate unusual attempts to enter it.

Payment matching

A payment reference from DANA, OVO, GoPay, QRIS, bank transfer or virtual account helps us identify the correct transaction without storing your wallet password.

Cookies and storage

Your browser or mobile device may retain session settings and security tokens. You can manage cookies through browser controls, though some account steps may then need repeating.

Account security

Phone verification and sign-in event checks help us detect access that does not match your account pattern. Keep your verification code private and contact us if activity looks unfamiliar.

Retention period

We keep personal and transaction records for operational, dispute or legal needs, then remove or anonymise them through our internal retention process when no longer required.

Change requests

You can request access, correction or deletion by using the policy support path. We may check your account details before making a change or sharing a data copy.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers cover the account steps that matter before you open access: what we collect, how wallet records are matched, what your device stores and how to request a change. If your situation is not listed, use the policy support path with the phone or email attached to your account.

It covers account details, phone verification, device and browser records, cookies, sign-in events, payment references and requests to access, correct or delete personal data.

Phone verification connects access to the correct account and helps us respond safely to data requests. We may also use verification results when checking unusual sign-in activity.

Yes. We may handle DANA, OVO, GoPay and QRIS references, along with bank transfer or virtual account details, to match payment status and account records.

Your browser or mobile device may store session settings, cookies or security tokens. You can adjust browser controls, but some account steps may need repeating afterward.

Use the policy request path from account help and identify the phone or email attached to your account. We verify ownership before preparing a data copy.

You can request correction or deletion where local law permits. We check account ownership and explain any payment, dispute or legal record that must remain.

We retain records for operational, dispute or legal needs. When a record is no longer required, our process removes or anonymises it according to retention rules.

Open the kastawin Privacy Policy for Wallet Data

Browse Policy Support From Your Account

Account help

Wallet status

Policy request

Switch Through Your Privacy Choices

Account records

Payment matching

Cookies and storage

Account security

Retention period

Change requests

Check Privacy Policy Answers Before Opening

01 What does the kastawin Privacy Policy cover?

02 Why does kastawin need phone verification?

03 Does the Privacy Policy mention DANA and QRIS data?

04 What can my mobile device store?

05 How do I request a copy of my data?

06 Can I ask kastawin to correct or delete data?

07 How long does kastawin keep account records?

Related Pages