Reference

jktwind Privacy Policy for Your Account

Our jktwind Privacy Policy explains what we collect when you create an account, verify your phone, open Live Dealer Lobby or use local wallets.

Account dataPhone verificationWallet recordsCookie choices
jktwind jktwind Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Cashier

A clear contact path matters when a wallet status or login record looks unfamiliar. We place the support route inside your account area and close to the cashier path, allowing you to ask about a Privacy Policy request without sending payment credentials. Include your account identifier, device type and the relevant DANA, OVO, GoPay or QRIS reference so we can locate the correct record.

Team online

Account data request

Use the account support link to ask which personal data is connected with your profile. We may request phone verification before discussing account-specific records.

Wallet record check

For a DANA, OVO, GoPay or QRIS query, share the transaction reference and date. We use those details to trace status without asking for your wallet password.

Device access concern

If a mobile browser or desktop session appears unfamiliar, contact us through the account support route. We can review the access record and explain the next account step.

ACCOUNT SAFEGUARDS

How We Handle Your Privacy Choices

We keep the policy practical by connecting each data use to an account action you can recognise. Phone verification supports account access, device checks help identify unusual sessions, and payment references let…

Data collection

We collect details you enter during account creation, phone verification and support contact, plus technical signals from the mobile browser or desktop session used to reach the lobby.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI records are used as transaction references. We use status and reconciliation details, not your wallet password.

Cookies and sessions

Cookies help keep a login session active and remember selected settings. You can clear or restrict them in your browser, though some account functions may then need another login.

Account protection

Phone verification, session checks and device signals help us respond to unusual access. Never send a one-time code, wallet password or full banking credentials through support.

Retention periods

We retain account, support and transaction records only as long as needed for the stated purpose, dispute handling, account safety and legal duties that apply to the service.

Changes and requests

Ask us to access, correct or remove eligible personal data through the account support link. We may verify your identity and explain any limit required by local law.

Privacy Policy Questions for jktwind

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the account step, wallet records, device behaviour, cookies and contact process in plain English for Indonesian access. If your case involves a specific transaction, use the support route beside the cashier and include its reference.

The jktwind Privacy Policy covers details you enter during account creation, phone verification, support contact and payment reconciliation. It also explains technical session data, cookie use, retention and requests to correct eligible records.

Phone verification links the account to the correct access step and helps us respond to unusual login activity. We may use the verified number when checking an account-specific Privacy Policy request.

Yes. The Privacy Policy covers transaction references and status for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We do not ask for your wallet password to reconcile a payment.

We may record device type, browser details, session time and security signals from your mobile browser or desktop access. These records help identify unusual sessions and maintain the correct account connection.

You can contact us through the account support link to request access or correction. We may verify your identity first, and the response depends on local law and any record-keeping duty that applies.

Use the cookie controls in your browser to clear, restrict or block cookies. Session cookies may be needed for account access, so changing them can require you to log in again.

Open the support route near the cashier path and provide your account identifier, date, device type and transaction reference when relevant. Do not send a wallet password or one-time code.