Reference

Privacy Policy for cicak win Accounts

cicak win Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and site access.

Account dataWallet recordsCookie choicesSecurity steps
cicak win Privacy Policy for cicak win Accounts
CONTACT THE DATA TEAM

Privacy Help Beside Your Account Path

A clear contact route helps you ask about personal data without sending sensitive details through random channels.

Account support Use the support path shown after login for a Privacy Policy request. We can locate your account using the registered phone number, then explain which details support access, phone verification or a DANA, OVO, GoPay or QRIS status check.
Payment record help When your question concerns a bank transfer or virtual account reference, send the transaction date and visible reference only. We use that context to investigate the record while avoiding passwords, one-time codes and complete wallet credentials in ordinary messages.
Policy questions For questions about cookies, retention, correction or access, quote the section that concerns you and describe the requested change. We will use the account contact route to confirm that the request comes from the person connected with the data.
DATA HANDLING PRACTICE

What We Do With Your Details

Privacy Policy choices matter most when they match the way an account actually works. We separate details used for login and phone verification from transaction references used to trace a wallet or…

Account details

We use your registered phone number and related account details to create the correct account path, complete phone verification before access and respond to requests made through support. We do not need your password or one-time code in a Privacy Policy conversation.

Wallet and payment data

A payment record can include a DANA, OVO, GoPay or QRIS reference, plus a bank transfer or virtual account reference when supplied. We use these details to match status questions with the right account and reduce mistaken changes to transaction records.

Device signals

Your browser, device type, IP address and session events can help us detect unusual access and keep the account path working from a mobile browser or desktop. These signals support security checks; they are not a request for contacts, photos or unrelated device content.

Cookies

Cookies may keep your login session, remember a selected setting or provide basic traffic measurements. You can clear or restrict them in your browser. If a restriction interrupts account access, we may ask you to sign in again rather than bypassing your browser choice.

Retention and deletion

We retain account, support and transaction records only for as long as they serve account security, dispute handling, legal duties or a documented request. A deletion request may not remove records that must remain for those purposes, and we will explain the applicable reason.

Changes and requests

To request access, correction or another change, contact us through the account support path and identify the record clearly. We may verify your registered phone details before acting. If access is discussed, it depends on local law and the policy in force when we receive your request.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the questions you may have before opening or using a cicak win account from Indonesia. They explain the practical steps for data access, wallet records, cookies, corrections and contact requests. When a question involves eligibility or account access, the answer depends on local law and the details available through your account support path.

The cicak win Privacy Policy covers account creation, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can ask about, correct or otherwise manage personal details connected with your account.

It can cover your registered phone number, account details, device and browser signals, IP address, session events and support history. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, related references may also appear so we can identify a payment status.

Phone verification helps us connect account access with the correct registered contact and helps prevent an unknown person from changing account details. We may use the verified phone path when you ask about a wallet record or request a Privacy Policy change, but we will not ask for your one-time code.

We use payment references to match a status question with the correct account and transaction, not to request unrelated wallet content. A support request should include the date and visible reference only. Do not send a wallet password, PIN or one-time code when asking about Privacy Policy.

Yes, contact us through the account support path and state whether you want access to a record or correction of a specific detail. We may confirm your registered phone information before responding. We will explain if a record must remain for security, dispute handling or legal duties.

Cookies can preserve a session, remember a setting and provide basic site-use measurements on a mobile browser. You can restrict or clear them through browser controls. Restricting cookies may require another login or affect a session, but it does not give us access to unrelated device content.

Use the support path connected with your account and describe the Privacy Policy question, such as access, correction, retention or cookies. Include only the details needed to locate the request. For account eligibility or access questions, the outcome depends on local law and the applicable policy.