Reference

Privacy Policy For Your ciptawin Account

Our Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
ciptawin Privacy Policy For Your ciptawin Account
HELP WITH DATA

Where To Ask About Privacy Policy

A clear contact route matters when your account record or wallet reference needs attention. Use the account help path for requests about the Privacy Policy, and include the sign-in detail or payment reference that helps us locate the correct record. We will use the details you provide only to handle the request and explain the next step.

Team online

Account access

If phone verification, sign-in history or a device change looks unfamiliar, contact account help from the same account path. Tell us what happened and when, so we can separate a genuine access issue from a normal session change.

Wallet records

For a DANA, OVO, GoPay or QRIS reference, send the relevant transaction detail through the cashier support path. We can use that reference to locate the record without requesting unrelated account details.

Privacy requests

Ask us to access, correct or remove personal data through account support. State the request clearly, and we may ask for an account check before changing a record or disclosing details.

SIX DATA PRACTICES

How We Handle Your Account Data

Privacy Policy choices should match what happens during a real account session. We separate sign-in checks from wallet references, use device signals to spot unusual access, and keep policy requests tied to…

Data collection

We collect details you provide during account opening, including contact details and phone verification data. We also receive session, device and wallet references when you sign in or ask us to trace a payment status.

Cookie control

Cookies and similar storage help keep your sign-in session active and remember policy choices on your device. You can manage browser settings, though removing necessary cookies may interrupt account access or require another sign-in.

Account security

Phone verification and device signals help us check whether an access attempt fits your account pattern. If a new device or sign-in event seems unfamiliar, use account help before sharing further wallet or contact details.

Payment references

A DANA, QRIS, bank transfer or virtual account reference helps us match a cashier event to your account. We use the reference for status handling and do not need unrelated game or browsing details.

Data retention

We keep personal data only for the operational, account, security or legal purpose connected with its collection. When that purpose ends, records are deleted, anonymised or retained only where a continuing obligation applies.

Policy changes

If the Privacy Policy changes in a way that affects your account data, we will place the revised text on this page. Check the page before using the account path, and contact us if a change needs explanation.

Privacy Policy Questions From Indonesia

The questions below address the practical points you may search before opening a ciptawin account. We cover account access, cookies, wallet references, correction requests and deletion in plain terms, so you can decide what to share before using DANA, OVO, GoPay, QRIS or a bank transfer path. Where eligibility matters, access depends on local law.

The ciptawin Privacy Policy explains how we collect, use, protect and retain account data, device signals, cookies and payment references. It also explains how you can ask for access, correction or deletion, and how we check a request before changing or disclosing account records.

It covers details you provide during account opening and phone verification, plus sign-in events, device signals and support messages. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, related references may be used to match the account event.

We use necessary cookies and similar storage to keep your session working, remember relevant choices and understand which policy page is opened. Browser controls can remove them, but account access may then require another sign-in or may not work until necessary storage is allowed.

Yes. Send a correction request through account support and identify the record that needs changing. We may ask for a phone or account check before editing it, because the Privacy Policy requires us to protect your details from an unrelated request.

You can ask us to delete personal data through the privacy support path. We first check the account request, then assess whether the record is still needed for security, payment tracing, account handling or a legal obligation before confirming what can be removed.

Only teams handling account, security, payment status or your support request should need that reference. We use it to match a DANA or QRIS event with the correct account and do not require unrelated game details to answer a wallet question.

No. The Privacy Policy describes data handling; it does not create eligibility. Account access depends on local law, and where local law permits, you can use the stated account path while keeping your data choices and contact rights available.