Reference

cun33 Privacy Policy For Your Account

cun33 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between casino and sports areas.

Clear data purposesWallet record handlingAccount access requestsCookie choices
cun33 cun33 Privacy Policy For Your Account
REQUEST PATHS

Three Ways To Ask About Privacy

A privacy question should not require you to search through your account. We provide a clear route for questions about stored details, cookie settings and wallet references, with enough account context for us to find the right record. Start from the account help path when you are signed in; if login or wallet status stalls, use the support route beside the cashier area. Tell us whether your request concerns DANA, QRIS, phone verification or device access, and we can direct it to the relevant privacy handling path.

Team online

Account privacy request

Use the signed-in account path to ask which phone, device or verification details are linked to your profile. Include the account identifier shown to you, rather than sending a password or wallet PIN. We use that step to match your request to the correct record.

Wallet record question

For a DANA, OVO, GoPay or QRIS question, include the transaction reference and date visible in your cashier history. We can check the recorded status without asking you to share a wallet password, card secret or one-time security code.

Access and correction

If a phone number, device detail or account name needs attention, send the requested change through our account support path. We may ask for phone verification before making an edit, so another person cannot redirect your account data.

DATA PRACTICE

How cun33 Handles Policy Details

Privacy work is tied to everyday account events, not kept as a separate abstract process.

Data collection

We collect details you enter for account creation and phone verification, together with technical signals from the browser or device used to sign in. These details help connect a session to the right account and help us identify access that does not match your normal account pattern.

Cookies and sessions

Cookies can keep an account session working, remember selected settings and support security checks between pages. If you clear browser cookies, you may need to verify your phone again before account access returns. Your browser controls can manage cookie storage on the device.

Wallet references

We record transaction references and status details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We do not need your wallet PIN to match a cashier event. The reference lets us check whether an entry is pending, completed or under review.

Account security

Phone verification is an account step before access, and device signals can support checks when a session looks unusual. Keep your password and one-time codes private. If you lose control of your phone, contact support through the account path so we can address the access concern.

Retention periods

We retain account, security and transaction records only for the period needed for the stated service, dispute handling, security checks or legal duties. A deletion request may therefore remove some active profile details while a required cashier reference remains stored for its necessary period.

Changes and contact

You can ask for a copy, correction or clarification of data connected with your cun33 account. Include your account identifier and the specific field or event, such as a QRIS reference or device entry. We may verify ownership before responding or applying a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the searches we hear around account access, local wallets and data requests. They explain the practical next step without asking you to disclose private codes in a support message. Where a question concerns eligibility or access, the answer remains subject to local law and the details shown in your account.

The cun33 Privacy Policy covers account details, phone verification, device and session signals, cookies, wallet references and support requests. It also explains correction, access and deletion requests. The policy applies to your use of the site where local law permits and does not ask you to share wallet PINs.

We use your phone number to create and protect the account, including a verification step before access. It helps us distinguish your request from another person’s request. If the number changes, use the account support path and be ready to confirm ownership before we edit it.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match a cashier event and answer a status question, while your wallet PIN and one-time code should remain private.

Start with the signed-in account privacy path and provide your account identifier plus the data category you want, such as phone, device or transaction records. We may complete an ownership check before responding. If you cannot sign in, use the support route beside the account or cashier area.

Yes. Send the specific correction through account support, naming the field and the accurate replacement. A phone-number change can require verification before it is applied. For a wallet record, include the reference and date so we correct the right event without changing unrelated account details.

On a mobile browser, cookies can maintain your session, retain selected settings and support security checks. Clearing them may sign you out or trigger phone verification again. You can manage cookie storage in your browser settings, while essential session controls may be needed for account access.

We keep each record for the period needed for account security, service handling, disputes or legal duties. Active profile details may be removed after an approved request, while a transaction reference can remain when retention is required. Ask support about the category and reason for a specific record.