Reference

jkt555 Privacy Policy And Your Data

Our Privacy Policy explains what we collect when you open a jkt555 account, use DANA, OVO, GoPay or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesSecurity requests
jkt555 jkt555 Privacy Policy And Your Data
HELP WITH DATA

Get Privacy Policy Help Directly

A clear contact route matters when your account record or wallet history does not look right.

Policy questions Use our account support chat when you need the Privacy Policy explained or want…
Receipt checks For a wallet record that needs checking, send the payment reference and method, such…
Account access If phone verification blocks access to a privacy request, tell us the registered number…
DATA PRACTICE

How We Handle Privacy At jkt555

We keep our Privacy Policy practical: each data category has a purpose linked to account access, security, support or wallet reconciliation.

Data purpose

We use registration details and phone verification to create and protect your account. Login events and device signals help us investigate unusual access, while payment references help us match a wallet or bank instruction without treating a receipt as a password.

Cookies

Cookies and similar session tools help keep your signed-in path working between the account page and lobby. You can manage cookie settings in your browser, although blocking required cookies may interrupt login, phone verification or the display of a saved session.

Account security

We may use phone verification, login records and device signals when a security question reaches support. Do not share a password or one-time code in chat. If your phone changes, contact us before requesting a change to the account contact details.

Retention

We retain account, support and transaction records only for the period needed for the purpose described in the Privacy Policy, account protection and applicable local requirements. A retention question can be sent through support with your registered phone number.

Your requests

You can ask us to access, correct or delete eligible personal details, or ask why a record is used. We may request account and phone verification first, then explain any limits that depend on local law before completing the request.

Policy changes

When our Privacy Policy changes, we update this page and identify the revised policy date or wording. Check the page before opening an account or changing wallet details, especially when you return from a mobile browser in Indonesia.

Privacy Policy Questions From jkt555

These Privacy Policy answers cover the questions we hear before account access: what we collect, why wallet details appear in a record, how cookies affect a mobile session and how to contact us. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, include the method and receipt number so our team can identify the correct account event.

The jkt555 Privacy Policy covers registration details, phone verification, login and device signals, cookies, support messages and payment records. It explains why we use each category, how retention works, what security steps apply and how you can request access, correction or deletion where local law permits.

We use your phone number to create an account, complete the phone verification step and help protect access when a request reaches support. If you ask to change it, we may confirm the existing account context first. Keep passwords and one-time codes private.

Yes. The Privacy Policy covers the payment reference and status details needed to match an account instruction through DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. We use those records for reconciliation, support and security rather than requesting your wallet password.

Contact account support through the available support chat and ask for a data access request. Include your registered phone number and the email or account detail connected with the request. We may verify ownership before responding, and the result depends on local law.

You can ask us to correct eligible account details by contacting support from your registered account path. Tell us which field is wrong and provide the corrected value without sending a password or one-time code. We confirm the request before changing the record.

Cookies help maintain a mobile or desktop session, remember consent choices and support the path from login to the account page. Your browser controls optional cookies. Required cookies may still be needed for phone verification and account security, so blocking them can interrupt access.

We keep personal data for the period needed for the purpose stated in the Privacy Policy, account security, support handling and applicable local requirements. Ask support about a specific category, such as a wallet receipt or login event, and we will explain the relevant retention basis.