Reference

jecktoto Privacy Policy For Your Account

jecktoto Privacy Policy explains how we handle the details used to open your account, verify your phone and connect DANA, OVO, GoPay or QRIS.

Clear data purposesWallet-linked account recordsPhone verification contextPolicy access on mobile
Browse Our Lobby Read FAQ
jecktoto jecktoto Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Your Account Route

A direct support route helps when a Privacy Policy question concerns your login, wallet status or a data request. Start from the support link connected to your account and include the phone number or account identifier you use, without sending a password or one-time code. Our team can explain a stored transaction reference, point you to the relevant policy section and record a request for correction or deletion where local law permits. This same route works from a mobile browser in Semarang or from desktop.

Team online

Account data request

Use the account support path to ask what personal details are connected to your jecktoto profile. Include your account identifier and the subject of the request; we may ask for phone verification before discussing records.

Wallet record question

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the transaction reference through support. We can explain which account record it relates to without asking you to share a wallet PIN, password or verification code.

Policy correction route

For an incorrect phone number, profile detail or consent record, contact us through the same support route. We review the request against your account and explain whether a correction, restriction or deletion is available under local law.

DATA HANDLING

What We Protect Across Your Devices

Privacy begins at the account boundary: we use the details needed to provide access, confirm ownership and keep wallet records connected to the right profile.

Account creation

When you open an account, we collect the required contact details and create a profile record. Phone verification helps confirm that the account route belongs to you before account access is enabled or sensitive support questions are handled.

Login protection

Sign-in activity can include device type, session timing and security signals. We use these details to identify unusual account access and protect the profile; do not send us your password or one-time code through support.

Cookie choices

Cookies can keep your session active, remember a language or device preference and help the account route function. You can manage cookie controls in your browser, although blocking some cookies may require another sign-in.

Wallet matching

A DANA, OVO, GoPay or QRIS reference may be stored with account and cashier records so we can identify a deposit or status query. We do not need your wallet PIN to explain a transaction entry.

Retention period

We keep account, security and transaction records only for operational, dispute and legal needs. When a record is no longer required, we remove it or separate it from direct account identifiers where local law permits.

Your request

You can ask for access, correction, restriction or deletion of eligible personal data through support. We verify the account holder first, describe any legal or operational limit and confirm the action taken or the reason it cannot proceed.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the questions we expect before you open an account or connect a local wallet. They explain what jecktoto collects, how device and payment records are used, and where to send a request. If your situation is not covered, use the account support path and mention the exact record or policy point you want us to check.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use those records, how they support account security and transaction matching, and how you can request access or correction where local law permits.

We may store a wallet or QRIS reference, account link, amount and status needed to identify a cashier event. We do not need your wallet PIN or one-time code for support. Bank transfer and virtual account references can be handled in the same account record.

Device and session signals help us recognise unusual sign-in activity and protect your account. They can include browser type, session timing and security events when you move from phone verification to the lobby. We use them for account operation and protection, not as public profile content.

Open the support route connected to your account and ask for a personal data access request. Include your account identifier and the records you want checked. We verify ownership before sharing account details, then explain the available data and any restriction required by local law.

Yes, send a correction request through account support and identify the field that is wrong. We may require phone verification before changing contact details because the phone route protects account access. We then confirm the correction or explain why a record must remain unchanged.

We retain records for the time needed to provide account service, protect access, resolve payment disputes and meet applicable legal duties. The period can differ by record type. When retention is no longer needed, we remove or separate the record where local law permits.

You can request deletion through the support path, and we assess the request against account, security and transaction duties. Some records may need to remain for dispute or legal reasons. We explain the result, the records affected and any reason a limited retention period applies.

Related Pages

jecktoto Indonesia jecktoto Casino About Us FAQ prototo