Reference

jokerscm Privacy Policy for Your Account

Our Privacy Policy explains how jokerscm collects, uses and protects the details you provide when opening an account, signing in and checking wallet status.

Clear data purposesWallet record controlsPhone verification detailCookie choices
jokerscm jokerscm Privacy Policy for Your Account
PRIVACY CONTACTS

Get Help With a Privacy Request

A clear contact path helps you ask about the data connected with your jokerscm account. Use the support route shown after sign-in and include the phone number or account detail needed to locate your record. We may ask for a verification step before discussing private account data, while payment references can help us separate a DANA or QRIS query from another account.

Team online

Account privacy

Ask which account details we hold and why they are used. Send the request through the signed-in support path so we can match it with your phone verification record.

Wallet records

For DANA, OVO, GoPay or QRIS questions, include the relevant payment reference without sharing your wallet password. We use the reference to locate the correct transaction record.

Access concerns

If a login or device signal appears unfamiliar, contact support from the account route shown on the site. We may confirm account details before discussing security-related events.

DATA HANDLING

What We Protect and Retain

Privacy is handled through practical account controls rather than broad promises. We limit internal access to data needed for account service, payment reconciliation, security checks or support work, and we keep records…

Account details

We may hold your name or contact details, phone verification status and sign-in history so we can maintain the correct account and answer a request about your personal data.

Device signals

Mobile and desktop access can create technical records such as browser type, session time and device indicators. We use these signals to identify unusual account activity.

Cookie controls

Cookies can preserve sign-in state and basic site preferences. You can manage cookie settings in your browser, though changing them may affect account access and saved sessions.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained for matching deposits, resolving disputes and confirming the account connected to a payment.

Account security

Phone verification and sign-in checks help us distinguish you from an unknown person requesting account data. Never send a password or one-time code through support.

Change requests

You can ask us to correct, access or clarify eligible personal data through the signed-in support route. We verify the request before changing or disclosing account records.

Privacy Policy Questions for jokerscm Accounts

These Privacy Policy answers focus on the account actions you are most likely to take: opening access, signing in on a device, checking a wallet reference and contacting us about stored data. If your question is not covered, use the account support path and mention the specific record or request you want us to assess.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect account access with the correct person and to reduce mistaken disclosure of private records. A verification step may be required before support discusses your account.

Yes. The policy applies when you sign in through a mobile browser or desktop device. Technical records such as session time, browser type and device indicators may support account security checks.

We may retain payment references and status details needed to match an account, reconcile a transaction or answer a support request. We do not ask you to send a wallet password or one-time code.

You can submit a correction or access request through the signed-in support route. We first verify that you control the account, then assess the request under applicable requirements and available records.

We retain data for as long as needed for account service, payment reconciliation, security review or applicable legal duties. The period can differ by record type and the reason it was collected.

Yes. Account access and eligibility depends on local law. Our Privacy Policy is applied with the requirements relevant to your location, and support can clarify how a request is handled.