Reference

jaya66 Privacy Policy for Your Account Data

Clear account data choices, wallet records and device access rules sit in the jaya66 Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet activityDevice accessPolicy requests
jaya66 jaya66 Privacy Policy for Your Account Data
CONTACT ROUTES

Where To Ask About Account Data

A direct policy contact helps when a phone number, wallet reference or device record needs clarification. Tell us the account step involved, such as phone verification before access or a QRIS status check, and avoid sending your password. Our team uses the account details you provide only to locate the request and respond through the available support route.

Team online

Policy request

Send a clear request about your Privacy Policy rights, including the account email or phone identifier connected with the record. We may ask for an account step to confirm that the request is yours.

Wallet question

For DANA, OVO, GoPay or QRIS records, include the transaction reference and approximate date rather than wallet credentials. This lets us trace the status while keeping sensitive wallet access details outside the request.

Login concern

If a new device, browser session or phone verification step appears unfamiliar, contact us through the account support path. We can examine access signals and explain which policy rule applies.

CONTROL CHECKS

Six Controls Behind Account Privacy

We keep the Privacy Policy practical by connecting each rule to an account action you can recognise.

Data collected

We may handle your account name, phone contact, verification result, login timestamps and transaction references. These records help connect account access with DANA, QRIS, bank transfer or virtual account activity.

Cookie choices

Cookies and similar browser storage can keep your session recognised and remember selected settings. You can manage browser permissions on your phone or desktop, although restricting them may interrupt account access.

Account security

Phone verification comes before account access, while device and login signals help us notice unusual sessions. Never share a password or wallet credential when asking about a Privacy Policy request.

Retention period

We retain account and transaction records only for the period needed for the stated account, security, dispute or legal purpose. A removal request is assessed against those active needs.

Correction request

You can ask us to correct an inaccurate phone contact, account detail or policy record. Include the old and corrected value, then complete any ownership check needed before changes are made.

Access request

You may ask what eligible personal records we hold and how they were used. We will identify the account step involved, verify the request, and explain any lawful reason a record remains.

Privacy Policy Questions For jaya66 Accounts

These Privacy Policy answers cover the searches we hear most often before account access. They focus on Indonesian wallet records, mobile devices, verification and requests for changes, so you can decide what to share and how to contact us.

It covers account details, phone verification, cookies, device signals, login records, wallet references and policy requests connected with our website. It also explains retention, corrections and access requests where local law permits.

No. Our Privacy Policy concerns transaction references and status details needed to match DANA, OVO, GoPay or QRIS activity with your account. We do not ask you to provide a wallet password.

Phone verification confirms the account step before access and helps us respond to login or ownership questions. The Privacy Policy explains how the phone contact and verification result are handled.

We may record browser, device and login signals when you use a mobile path or desktop session. These details help identify unusual access, while browser cookie controls remain available on your device.

Yes. Contact us with the account identifier, the inaccurate detail and the correction you seek. We may verify ownership before changing the record, as described in our Privacy Policy.

We keep transaction references for the account, security, dispute or legal purpose that requires them. The Privacy Policy explains that an eligible removal request is assessed against those needs.

Use our account support path and describe the exact record or account step, such as a GoPay status check or unfamiliar login. Do not include passwords or wallet credentials in your message.