Reference

jackpot168 Privacy Policy for Your Account

Our Privacy Policy explains how jackpot168 handles the details connected with your account, mobile browser and wallet activity.

DANA recordsQRIS recordsMobile browser pathAccount request steps
jackpot168 jackpot168 Privacy Policy for Your Account
PRIVACY HELP ROUTE

Where to Ask About Your Privacy Policy

A clear support route helps when a privacy question and an account check meet.

Account help Open the account help path after login and describe the Privacy Policy request, including…
Payment reference For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date through…
Policy clarification If wording in this Privacy Policy is unclear, contact the support route before opening…
DATA CONTROL STEPS

Account Security, Cookies and Retention

We keep this policy area practical: your account record, device signals and cookie choices each have a defined reason.

Account records

We retain the account details needed to identify your profile, verify phone access and connect support replies with the correct…

Device signals

When you use a mobile browser, we may record device and login signals to detect unusual access.

Cookies

Cookies can keep your session, remember selected settings and help us understand whether a policy page loaded correctly.

Payment security

A DANA, QRIS, OVO, GoPay or bank reference is used to reconcile status.

Retention requests

We keep records only for the operational, security or legal period connected with their purpose.

Changes and access

You can ask for a copy, correction or clarification through the account support route.

Privacy Policy Questions About jackpot168

These answers address the searches we hear most often about the Privacy Policy, including account records, wallet references, cookies and access requests. If your situation is different, use the support path linked to your account and describe the exact record or device step involved.

It covers account details, phone verification, login and device signals, cookies, payment references, support records, retention and requests to access or correct information connected with your account.

No. We use payment references, confirmation results and account matching for DANA and QRIS checks. Do not send a wallet PIN, banking password or one-time code through support.

Device and login signals help us identify unusual account access, protect phone verification and investigate a support request. We use these signals for security and do not treat them as private device content.

Use the support path inside your account and ask for an access copy. Provide the phone number attached to the account and complete the identity check requested before records are released.

Yes. Send a correction request through account support and identify the affected detail, such as a phone number or payment reference. We may verify your identity before updating the record.

Retention depends on the purpose of the record, account security needs and applicable legal requirements. Ask support about a specific DANA, QRIS, bank transfer or virtual account reference.

Use the policy support route linked from your account and name the cookie or record involved. We will explain available controls, any required identity check and the applicable retention position.