Reference

jek33 Privacy Policy for Your Account Path

jek33 Privacy Policy explains how we use account, device and payment details when you open the lobby, select Lightning Roulette Room or check a wallet status.

Account dataWallet recordsDevice choicesAccess depends on local law

Explore Our Lobby Read FAQ

Open the Privacy Policy Before Account Access

jek33 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies when you create an account, complete phone verification, sign in, contact support or use a payment route. We may process your account name, phone number, verification result, sign-in events, device details and transaction references so we can connect your request to the

1
correct account. A DANA, OVO, GoPay or QRIS reference helps us match a deposit or withdrawal status; bank transfer and virtual account records serve the same purpose for those routes. We use this information for account security, payment reconciliation, service messages and requests made through our
2
contact path. Access depends on local law, and where local law permits, we may restrict an account or request additional checks before access continues. The current policy applies to the data handling described on this page, while any specific notice shown during an account step also
3
matters.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT THE DESK

Reach Support About Privacy Policy Requests

A clear contact path helps you ask about the Privacy Policy without guessing which team handles your record.

DATA PRACTICE

Explore How jek33 Handles Your Data

The Privacy Policy is supported by ordinary account controls rather than vague promises. Phone verification helps us connect a request to the right account, while sign-in and device signals help us investigate…

Collected details

We may receive your phone number, account settings, verification outcome, sign-in time, device type and support messages. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we also receive the reference needed to match the account action.

Cookie choices

Browser storage can keep a session active, remember a selected lobby route and support security checks on mobile or desktop. You can adjust cookie permissions in your browser. If necessary storage is blocked, sign-in or the move from login to the lobby may not function correctly.

Account security

Phone verification is part of account access, and device or sign-in signals can help us spot an unusual request. Never send a wallet PIN or account password to support. For a suspicious sign-in, contact us through the account path and describe the event time.

Payment records

A payment reference is used to reconcile the requested action, not to obtain your private wallet credentials. DANA and QRIS confirmations, along with OVO or GoPay status details, can remain available while a transaction, dispute or accounting duty requires a record.

Retention choices

We keep each category only for the operational, security or legal purpose connected to it, subject to applicable requirements. When you ask for deletion or restriction, we assess the request against open transactions, account security needs and where local law permits.

Request changes

You can ask us to access, correct or delete eligible personal data through the support route. State the account phone number, the precise field to change and your preferred reply path. We may verify ownership before making a change or disclosing a record.

Browse Answers About Privacy Policy

These Privacy Policy answers address the account questions most likely to arise before you open access. They cover phone verification, device storage, local wallets, correction requests and account closure without turning the page into a general lobby description. If your question involves a specific record, use the account support path and include only the details needed to identify it. Access depends on local law.

The jek33 Privacy Policy covers personal data used for account creation, phone verification, sign-in security, support requests, cookies and payment reconciliation. It explains why we use those details, how retention works and how you can request access, correction, restriction or deletion where local law permits.

We use your phone number to create and identify your account, complete the required verification step and connect a Privacy Policy request to the correct record. It can also help us investigate a sign-in issue. Do not share your verification code or wallet PIN with support.

Yes. The Privacy Policy covers the payment references and status details needed to match an account action through DANA, OVO, GoPay or QRIS. We do not need your wallet password or PIN for reconciliation. Bank transfer and virtual account references are handled for the same purpose.

You can request access to eligible personal data through the account support path. Include your verified phone number, the account detail you want and a safe reply route. We may confirm ownership first, then explain the available record and any limit required by local law.

Send a correction request through support and identify the exact field, such as a phone number or account name. We may ask for a verification step before changing it. A payment reference should remain unchanged when it is needed to preserve an accurate transaction record.

Retention depends on why the data was collected, including account security, payment reconciliation, support handling and legal duties. We remove or restrict eligible records when the purpose ends or a valid request applies, subject to open transactions and where local law permits.

You can ask for deletion through the verified account contact path. We assess which records can be removed and which must remain for security, unresolved payment matters or legal requirements. The Privacy Policy request should name your account phone number and the data categories concerned.

jek33 Privacy Policy for Your Account Path

Reach Support About Privacy Policy Requests

Explore How jek33 Handles Your Data

Collected details

Cookie choices

Account security

Payment records

Retention choices

Request changes

Browse Answers About Privacy Policy

01 What does the jek33 Privacy Policy cover?

02 Why does jek33 need my phone number?

03 Does the Privacy Policy cover DANA, OVO, GoPay and QRIS?

04 Can I ask jek33 for a copy of my data?

05 How do I correct an error under the Privacy Policy?

06 How long does jek33 keep personal data?

07 Can I request deletion of my jek33 account data?

Related Pages