Reference

Privacy Policy for Indonesia Accounts

Your account privacy controls sit beside the sign-in flow: we explain how carikodepos handles profile details, device signals, payment records from DANA, OVO, GoPay and QRIS, and lobby…

DANA data handlingOVO and GoPay recordsQRIS scan logsCookie controls
carikodepos Privacy Policy for Indonesia Accounts
CONTACT ROUTES

Privacy Help Across Chat and Email

Fast privacy contact matters when your phone changes, a device looks unfamiliar, or a receipt needs checking.

Live chat privacy desk Use chat after you sign in when your question involves login records, DANA receipt…
Email request channel Send privacy requests to [email protected] when you need a written record.
WhatsApp account check Use WhatsApp from the help panel for quick identity checks tied to profile edits.
ACCOUNT CARE

Account Data Controls You Can Check

Practical privacy starts with settings you can see. We show cookie choices on your first device session, record sign-in device type, and keep payment references separate from game activity such as Great…

Data we collect

We collect profile details, phone verification status, device type, IP range, cookie choices, wallet action times, and lobby activity. Those records help us run account access, payment matching, security checks, and privacy replies.

Payment privacy

DANA, OVO, GoPay and QRIS records are used to match receipts with your wallet actions. We keep rail name, timestamp, reference details, and account link status, not full wallet balances from your provider.

Cookie choices

Cookies remember sign-in status, language, device session, and basic site measurement. You can clear browser cookies on Chrome through Settings, Privacy and security, then Cookies, but sign-in checks may repeat.

Account security

Password changes, phone edits, and new device sign-ins create security records. If an action looks unusual, we may pause the privacy change until you confirm the request through chat or email.

Retention periods

We keep account and payment records only as long as needed for service, dispute handling, legal duties, and fraud checks. When a record no longer has a valid reason, we remove or anonymise it.

Correction requests

If your name, phone, or payment reference is wrong, open Account, Profile, then Privacy Request. Tell us what needs changing, attach a clear receipt when relevant, and we will verify before editing.

Privacy Policy Questions You May Ask

Privacy questions usually come up before you open an account, after a device change, or when a payment receipt needs matching. The answers below explain what we collect, why we use it, and how you can contact us. For anything tied to your account, we verify your identity before sharing or changing data.

We collect the details needed to create and protect your account, including username, registered phone, password status, device type, IP range, cookie choices, and wallet action records tied to DANA, OVO, GoPay or QRIS.

We keep payment rail records to match receipts, handle wallet questions, trace disputed actions, and meet legal duties. The record may include rail name, timestamp, reference code, and linked account status.

Yes. Sign in, open Account, choose Profile, then select Privacy Request. We verify your registered phone or email before sending account data so the reply does not go to the wrong person.

Send the correction through the Privacy Request path or email [email protected]. Tell us the field that is wrong, the correct detail, and any DANA, OVO, GoPay or QRIS receipt involved.

Cookies help remember sign-in status, language, session safety, and basic site use. We may connect activity such as Live Dealer Lobby or Tennis Betting visits to your account for security and service records.

Only staff who need the request for support, security, payment matching, or legal handling can access it. We record the reason for access and avoid sharing account details outside the required task.

Retention depends on the record type and legal need. Payment references, security logs, and account history may be kept for dispute or compliance reasons, then removed or anonymised when no valid reason remains.