Reference

jet366 Privacy Policy for Your Account

Our jet366 Privacy Policy explains what we collect when you create an account, verify your phone, browse from mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
jet366 jet366 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route matters when you want to ask about a phone number, wallet reference or stored account detail. We handle privacy questions through the support path available after login, and you can point us to the relevant account step rather than explain your whole activity. If access is unavailable, use the contact route shown on the jet366 site and include only the details needed to locate your request.

Team online

Account help chat

Ask about account data, phone verification or a login record through the support chat linked to your account path. We may request confirming details before discussing private information, so your account data is not disclosed to the wrong person.

Wallet status path

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment reference through the cashier support route. We use that identifier to check the matching account record without asking you to share a wallet password or full private credentials.

Privacy request route

For access, correction or deletion questions, state the request clearly and include your account contact detail. We will explain the next verification step, any legal reason a record must remain, and how the change will be reflected in your account.

DATA PRACTICES

Phone, Device, Cookies and Retention

We treat privacy as an account operation, not a decorative page. The details below explain how we handle the signals created when you move from phone verification to the lobby, return on…

Account details

We use the contact details and verification information you submit to create and protect your account. A confirmed phone step can help us recognise an authorised request, while inaccurate details may prevent us from completing an access or correction request.

Device signals

Your browser, device type, session time and security signals may be recorded when you log in from mobile or desktop. These details help us identify unusual access and connect a support question to the correct account without reading unrelated device content.

Cookie choices

Cookies and similar storage can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can adjust cookie controls in your browser, although some account steps may then require another login.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references, amounts and status timestamps. We use those records to reconcile your account and respond to payment questions; we do not need your wallet PIN.

Security checks

We may compare login behaviour, phone verification and transaction references to protect account access. If a check pauses a request, support can explain the next step after confirming that you are the account holder.

Retention and changes

We retain records for as long as needed for account operation, security, dispute handling or legal duties, then remove or restrict them when appropriate. You can request access, correction or deletion through our privacy contact route.

Privacy Policy Answers for jet366 Accounts

These Privacy Policy answers cover the searches we expect before you open an account or ask us to change one. We focus on the practical details: what is collected, why a phone or device check appears, how DANA and QRIS references are handled, and where to send a request. If your situation involves access eligibility, it depends on local law.

The jet366 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and wallet transaction references. It explains why we use those records for access, security, reconciliation and legal duties, including activity connected with DANA, OVO, GoPay and QRIS.

Phone verification helps us connect an account request to the person who controls the registered contact detail. We may use the result during login assistance, privacy requests or security checks. If you cannot complete the step, contact support through the account path for the next verification option.

Yes. The Privacy Policy covers references, status details and timestamps linked to DANA and QRIS activity, as well as OVO, GoPay, bank transfer and virtual account records. We use them to match a transaction to your account and investigate a status question without requesting your wallet PIN.

You can send an access request through the privacy contact route shown on the site. We may ask you to confirm your account and phone details before releasing private records. Our response can include account data, support history or transaction references that we are permitted to provide.

Tell support which detail is incorrect, such as a contact number or account identifier, and use the registered account path where possible. We may verify your identity before making a change. Some transaction or security records may need to remain accurate for legal or dispute reasons.

We keep account, security and wallet records for the period needed to operate access, reconcile transactions, address disputes and meet legal duties. When a record is no longer needed, we remove or restrict it according to our retention process, subject to applicable local requirements.

You can ask for deletion through the privacy request route, and we will explain what can be removed. We may retain limited account, security or transaction records when required for legal duties, fraud prevention or dispute handling. Eligibility and available rights depend on local law.