Reference

Open cunjp With Clear Data Terms

Your account, wallet, device, and table-session records sit under one Privacy Policy before you open an account with us.

Account dataWallet recordsCookie choicesSupport requests
cunjp Open cunjp With Clear Data Terms
CONTACT ROUTES

Reach Us About Privacy Requests

Fast privacy contact matters when your wallet or login data needs attention.

Live chat inside your account Open Help, choose Privacy Request, then describe whether the issue concerns account details, cookies…
Email privacy contact Send your request from the email linked to your account and include your username…
Account verification step Before changing or releasing personal data, we may ask you to confirm a recent…
ACCOUNT CONTROLS

Control Your Account Data Trail

Useful privacy control starts inside your account, not in a separate form you never see. After login, open Account, then Security, to view active sessions, update your password, and check saved contact…

Account setup records

When you join, we store the details needed to create your login, protect your password, and connect your profile to support. Keeping those fields accurate helps us verify privacy requests without asking for extra files.

Device and session checks

We log device type, browser signals, IP range, and session timing when you enter the lobby or load games such as Gonzo's Quest, Mega Fishing, or Live Baccarat. These records help spot account misuse.

Cookies and site storage

Cookies keep you signed in, remember language choices, and measure page errors. You can clear them through your browser path, usually Settings, Privacy, Site Data, then cunjp.bet, though doing so may log you out.

Payment privacy handling

Wallet data linked to DANA, OVO, GoPay, and QRIS is used to match your transaction with your account. We keep payment references, timestamps, and status codes rather than asking for sensitive app credentials.

Retention and deletion

You can ask us to delete data that is no longer needed for service, payment records, security checks, or legal duties. Some records may stay for a required period before removal is allowed.

Correction requests

If your email, phone, or wallet label is wrong, contact us before your next withdrawal request. We may confirm recent account activity first, then update the field and record the change in our privacy log.

Ask About Your Privacy Choices

Privacy questions are easier when the answer points to the account step you can take next. The answers below cover the data we collect, wallet records, cookies, correction requests, deletion requests, and contact routes. If your question involves a specific DANA, OVO, GoPay, or QRIS transaction, include the date and account name when you contact us so we can trace the record faster.

We collect the details needed to create and protect your account, such as login name, contact channel, password signals, device data, and wallet method selection. We also log support chats and payment references tied to your profile.

We keep wallet records to match deposits, confirm withdrawal requests, resolve payment questions, and detect duplicate or unusual activity. The record usually includes rail name, timestamp, status code, and account reference, not your wallet app PIN.

Yes. Contact us through live chat or the email path after login, then tell us which field needs correction. We may confirm your recent login device or wallet rail before changing contact details.

You can ask us to delete data that is no longer needed. Some records may need to remain for account security, payment matching, dispute handling, or legal duties before we can remove them.

Cookies help keep your session active, remember basic site choices, and track technical errors. You can clear them in your browser under Settings, Privacy, Site Data, then cunjp.bet, but you may need to log in again.

Your privacy request is handled by staff who need access to answer it, verify your account, or escalate a technical issue. We keep chat records so your request can be tracked and not repeated.

Yes. Account access, service use, and privacy actions connected to eligibility depend on local law and are available only where local law permits. We may apply location and account checks before acting on certain requests.