Reference

Privacy Policy For Your cozebet Account

Our Privacy Policy shows how we collect, use and protect the details connected with your cozebet account, from phone verification to wallet activity.

Account dataWallet recordsCookie choicesAccess requests
cozebet Privacy Policy For Your cozebet Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact route helps you act on this Privacy Policy instead of searching through account screens.

Account help request Open the help path from your signed-in account and select the privacy request option. We use your registered phone number to locate the correct record, then reply with the next account-check step.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, include the date and amount shown in your account. We can check the payment record without asking you to share a wallet PIN.
Security concern If a login, device session or phone verification looks unfamiliar, tell us through the account help path as soon as possible. We can review the access record and explain the steps available for securing your account.
DATA HANDLING

Six Practical Privacy Controls

Our approach focuses on the moments where account privacy matters most: creating access, using a mobile device, checking a wallet record and asking for a change.

Account creation

We collect the account details needed to create your profile and complete phone verification. Providing accurate details helps us connect your request with the correct record when you later ask to view or correct account data.

Cookie choices

Cookies can keep a session active and remember selected settings on your browser. You can review cookie controls in your browser settings; changing them may require another login or affect how privacy preferences are saved.

Device signals

We may record device type, browser version, session time and approximate access signals to identify unusual sign-ins. These details help us check a security concern without needing access to your private phone contents.

Wallet matching

A DANA, OVO, GoPay or QRIS reference can be linked to your account transaction record so a payment question reaches the right request. We do not ask for your wallet PIN or full banking password.

Record retention

We keep personal and transaction records for the period needed for account operation, security checks or legal duties. When a record is no longer needed, we remove it or reduce its connection to your identity.

Change requests

You can ask us to correct account details, explain a stored record or discuss deletion where local law permits. We may request phone verification before making a change that could affect account access.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we receive most often about cozebet accounts, local wallet references, cookies and personal records. If your situation is different, use the account help path and describe the specific record or access event. We will use the details you provide to route the request correctly.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, wallet references, support messages and activity records connected with your account. It also explains retention, security checks and how you can ask to view or correct information where local law permits.

Yes. The Privacy Policy covers transaction references linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match a payment question with your account, without requesting your wallet PIN.

Open the help path from your signed-in account and choose the privacy request route. State whether you want access, correction or an explanation of a record, and include your registered phone number. We may complete a phone verification check before sharing personal details.

You can request a correction through the account help path. Tell us which detail is inaccurate and what the correct value should be. We may compare the request with your phone verification record before changing the account, where local law permits.

On a mobile browser, cookies may keep your login session and privacy choice available between pages. Browser controls let you clear or restrict them, although you may need to log in again. Device signals used for security are handled separately from cookie settings.

We retain account, security and wallet records for operational needs, payment matching, dispute handling or legal duties. Once a record is no longer required, we remove it or reduce its connection to you. The period can vary by record type and local law.

Yes. Use the account help path and describe the unfamiliar session, device or phone verification event. Do not send a password, wallet PIN or full banking credentials. We can review the access record and explain the available account-security steps.