Reference

Read colowin Privacy Policy Before Opening

colowin Privacy Policy explains what we collect when you create an account, verify your phone, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessYour choices

Explore Our Lobby Read FAQ

Check How Wallet Data Is Used

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

Our Privacy Policy covers the details needed to create and protect your account, including your phone number, verification result, sign-in records and device signals. When you choose DANA, OVO, GoPay or QRIS, we may record the selected payment rail, transaction reference, amount, status and related account

1
identifier so we can match a wallet event to your request. Bank transfer and virtual account records may include the bank reference and confirmation status, including rails connected with BCA, BRI, Mandiri or BNI. We use these records to resolve payment questions, detect unusual access and
2
keep a clear account history. We do not describe access as available everywhere; eligibility depends on local law and our service settings. Please read the full policy before you submit personal details or connect a payment method.

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

SUPPORT ROUTES

Contact Us About Your Privacy Policy

A clear support path helps when you want to ask about a record, correct an account detail or understand a wallet reference. Use the support route shown beside your account and cashier area, and include the phone number linked to your account without sending a password or full payment credential. We can then locate the relevant request and explain the next step.

Team online

Data access request

Ask us to explain the personal data connected with your account, including phone verification, sign-in history and payment references for DANA, OVO, GoPay or QRIS.

Correction request

If your account detail is inaccurate, contact support through the account path and identify the field to change; we may ask for a verification step before updating it.

Wallet query

For a missing or unclear wallet record, share the payment rail and reference shown in your account. Never send your wallet PIN, password or complete card details.

DATA PRACTICE

See How We Protect Account Data

We limit routine access to personal data to the account and payment tasks that need it, while your account remains protected by phone verification and sign-in checks.

Account collection

We collect details such as your phone number, verification result and account activity when those records are needed to create, secure or maintain your colowin account.

Cookie choices

Cookies and similar device storage can help remember session settings and measure account access. Your browser settings provide controls, although some account functions may then need repeated sign-in.

Device signals

A mobile sign-in may create device and security signals linked to your session. These checks help us identify unusual access without treating your phone as a permanent identity by itself.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we use reference and status data to match the payment event with your account.

Retention approach

We retain records for the period needed for account security, payment questions, dispute handling and legal duties. The Privacy Policy explains why a particular record may remain stored.

Change requests

To request access, correction or deletion, contact us through the support path with your account phone number and request details. We may verify ownership before taking action.

Find Privacy Policy Answers Quickly

These Privacy Policy answers address the account, device and payment questions you may search before opening an account with colowin. If your request concerns a specific record, use the support path and include its date, payment rail or account step.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, retention, security practices and the ways you can request access or corrections.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references, including the selected rail, transaction status and account details needed to match a payment request.

We use your phone number for account creation, verification and account recovery steps. It also helps us connect a support request with the correct account without asking for your password.

When you sign in on mobile, we may process session and device signals for security and service continuity. These signals help identify unusual access and are handled under the Privacy Policy.

You can contact support with your account phone number and ask for access to your personal data. We may confirm account ownership before preparing the relevant records.

Send a correction request through the account support path, name the inaccurate field and provide the relevant context. We may request phone verification before changing account information.

No. Reading the Privacy Policy does not change eligibility. Account access and processing may apply only where local law permits and after the required account steps are completed.

Read colowin Privacy Policy Before Opening

Contact Us About Your Privacy Policy

Data access request

Correction request

Wallet query

See How We Protect Account Data

Account collection

Cookie choices

Device signals

Payment matching

Retention approach

Change requests

Find Privacy Policy Answers Quickly

01 What does the colowin Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS records?

03 Why does colowin need my phone number?

04 How does the Privacy Policy treat mobile device data?

05 Can I request a copy of my colowin data?

06 How do I correct personal data in my account?

07 Does access to this Privacy Policy mean I can use the service?

Related Pages