Reference

wincheez Privacy Policy In Plain English

The wincheez Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check DANA and QRIS status.

Account dataWallet checksDevice accessPolicy requests
wincheez wincheez Privacy Policy In Plain English
ASK OUR TEAM

Three Ways To Reach Policy Support

A clear contact path matters when a privacy question affects your account or wallet status. We ask you to use the account support route shown beside the cashier area, include the phone or email connected to your account, and describe the exact policy request. That lets us match your message without asking for a wallet password or a full payment credential. If access is unavailable, keep the receipt reference and device type ready; we can then explain which data we need to check and how the request proceeds.

Team online

Account help route

Use the support path beside your account and cashier pages for questions about collected data, phone verification, or a stored contact detail. Include your account identifier and request type, but never send your DANA, OVO, GoPay, or QRIS password.

Payment status query

For a privacy question linked to a deposit or withdrawal record, share the payment reference, rail name, and approximate time. We use those markers to locate the relevant entry without requesting your complete bank card or wallet credentials.

Access fallback

If you cannot sign in from your phone, tell us the device type, browser path, and contact detail attached to the account. We can separate an access issue from a data request and explain the next identity check before making changes.

DATA HANDLING

Six Practical Privacy Commitments

Privacy work is part of each account step, from the first phone check to a later request about stored records.

Account creation

When you open an account, we collect the contact and verification details needed to create that account and respond to…

Wallet references

DANA, OVO, GoPay and QRIS activity can create a payment reference, amount, status, and time record.

Device sessions

A phone, tablet, or desktop session can produce technical details such as browser type, access time, and security signals.

Cookies and settings

Cookies may remember a session, language setting, or security preference so you do not repeat the same account step on…

Retention choices

We retain account, support, and payment records only for the period needed for the stated account, security, service, or legal…

Requesting changes

To ask for access, correction, or another privacy action, use our support route and identify the account contact, request, and…

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or connecting a local wallet. They explain the account path, device records, payment references, cookies, retention, and your contact options without turning the page into general lobby material. If your situation is not covered, send the request through account support with the relevant contact detail and payment reference. We will explain the next step and any identity check needed.

The wincheez Privacy Policy covers account details, phone verification, device and session records, cookies, support messages, and payment references. It applies when you create an account, sign in, check wallet status, or contact us about a record, where access depends on local law.

Phone verification helps us connect the right contact detail to your account before we discuss private data or change access settings. It also helps separate an account request from an unrelated message. We do not ask you to provide a DANA or OVO password.

No. The Privacy Policy covers payment references such as a rail name, status, time, and account match. When you use QRIS or GoPay, we use those operational details to reconcile the cashier record, not to collect your wallet password, PIN, or complete banking credentials.

Use the account support route and state whether you want access, correction, or another Privacy Policy request. Include the account contact and relevant date or payment reference. We may verify your identity first, then explain the available action and any record that must remain.

We keep records for the period needed for the stated account, support, security, service, or legal purpose. The exact outcome can depend on the record and local requirements. Ask through support for a retention explanation connected to your account or payment event.

Yes. Your mobile browser settings can restrict or remove cookies, including those that help maintain a session or remember a page preference. The Privacy Policy explains their role; restricting them may interrupt login continuity, so check the account path after changing settings.

Start with the support path beside your account and cashier pages. Give us your account contact, the concern, and any relevant DANA, QRIS, bank transfer, or virtual account reference. If you cannot sign in, add your device type so we can explain the fallback.