Reference

cawan4d Privacy Policy: Your Account Data Path

Our cawan4d Privacy Policy explains what we collect when you open an account, sign in on mobile, or enter rooms such as Speed Blackjack and Mines.

Account dataDevice recordsWallet contextCookie choices
cawan4d cawan4d Privacy Policy: Your Account Data Path
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact path helps when you want to ask about a record, correct an account detail, or understand why a wallet reference is connected to your profile. Start from the support route linked to your signed-in account, or use the contact path shown beside the cashier area. Tell us the account step or receipt reference involved, and we will use that context to locate the right policy question without asking you to send a password.

Team online

Account support path

Use the signed-in support route for a privacy question about your name, phone verification, login record, or account access. We can match the request to the profile without requesting your password.

Wallet status help

If DANA, OVO, GoPay, or QRIS shows an unclear status, include the payment reference and date through support. We use those details to explain the related record and next privacy step.

Receipt questions

For a bank transfer or virtual account receipt, send the reference through our contact route rather than posting it publicly. We limit the request to details needed for account and policy checks.

DATA PRACTICES

How cawan4d Handles Account Records

We keep this policy practical: account records support sign-in, phone verification, wallet matching, and security checks across the mobile browser and desktop path.

Account data use

We use your account details to create access, complete phone verification, connect wallet status, and respond to policy requests. We do not need your wallet password to investigate a DANA or QRIS reference.

Mobile device records

Signing in from a mobile browser can produce device, browser, language, and security event records. These help us recognise unusual access while keeping the same policy path available on desktop.

Cookie controls

Cookies can remember sign-in state, security preferences, and page choices. Your browser settings let you remove or restrict them, although some account and policy functions may then require another sign-in.

Account protection

We use phone verification, sign-in records, and access checks to reduce account misuse. If a login looks unusual, support may ask for account details that confirm ownership without requesting a password.

Record retention

We retain account, payment reference, and support records for the operational, dispute, and legal periods connected to their purpose. When a record is no longer needed, our handling follows the applicable retention process.

Change requests

You can ask us to correct inaccurate account data, explain its use, or clarify a retention question through support. Include your account identifier and request type so we can route it correctly.

Privacy Policy Questions From Indonesia

These answers address the searches we hear most often about the cawan4d Privacy Policy. They cover account access, wallet references, cookies, device records, corrections, and the route to contact us when you need a clearer answer.

The cawan4d Privacy Policy covers account details, phone verification, sign-in events, device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

We record a DANA or QRIS reference so we can match wallet status to the correct account, investigate a missing receipt, and identify unusual activity. The reference is handled for account and payment checks.

Yes. Contact us through the account support route with your account identifier and the field that needs correction. We may verify ownership through the phone verification step before changing the record.

Yes. The Privacy Policy applies when you use the mobile browser path, including sign-in, lobby access, cookies, and security events. Device records can help us recognise unusual access from a new phone.

We use cookies for sign-in state, security preferences, and page choices. You can restrict or remove them in your browser, but doing so may require another login before you can access account policy tools.

We keep payment references for the operational, dispute, and legal needs connected to the transaction. Retention can differ by record type, and you can contact support to ask how a specific reference is handled.

Use the signed-in support route or the contact path beside the cashier area to ask about access, correction, deletion, cookies, or retention. Eligibility for a request depends on local law and the record involved.