Reference

Open Your Privacy Choices With juliet4d

juliet4d Privacy Policy shows what we collect when you open an account, verify your phone, enter the lobby from a mobile device and use DANA or QRIS.

Account dataCookie choicesPayment recordsSecurity requests
juliet4d Open Your Privacy Choices With juliet4d
PRIVACY HELP

Switch To Our Account Privacy Route

A clear support path helps when your privacy question concerns login, a wallet record or a correction request.

Account help path Use the account help route for access, correction or deletion questions.
Wallet record check For DANA, OVO, GoPay or QRIS concerns, attach the transaction reference and date rather…
Login privacy request If a phone verification or sign-in event looks unfamiliar, use account support promptly.
DATA PRACTICE

Browse Security Steps Before Login

We keep this policy practical: you should be able to see what enters our records, why it is used and how to ask for a change.

Account details

We use your registered phone number, login details and verification responses to create and protect account access. Check your account path before sending a request, because an accurate contact detail helps us respond to you.

Device signals

When you move from a mobile browser to desktop, we may record device, browser and session signals. These details help us examine unusual sign-ins without treating the device itself as your identity.

Cookie controls

Cookies can retain a session and support page settings. You can review cookie controls in your browser, although removing necessary cookies may require you to sign in again before reaching your account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference records. We use those references to match status and account activity, not to request your wallet password.

Retention choices

We keep records only for the account, security, support or legal purpose that requires them. When a retention period ends, the record is removed, anonymised or restricted where that process applies.

Change requests

Ask us to correct eligible personal details through account support. We may confirm your phone verification or another account step first, then explain whether the requested change can be made under local law.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the account questions you are most likely to have before opening access. Each response points back to a practical step, from checking cookies on your phone to requesting a correction through account support.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references. The policy explains how we use those records for account access, security, payment reconciliation and support, where local law permits.

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain transaction references, dates and status details. We do not need your wallet password to investigate a payment record or receipt.

Sign in, open the account help area and describe the correction clearly. Include the registered phone number or relevant account detail. We may complete a phone verification step before changing personal data tied to your account.

Yes. Your mobile browser provides cookie controls, including options to remove stored cookies or restrict some categories. Necessary session cookies may be required for login, so changing them can sign you out or reset saved settings.

We use login records, phone verification and device or session signals to assess unusual access. If a sign-in looks unfamiliar, use the account support route and avoid sharing your password or full wallet credentials.

Retention depends on why the record exists, such as account support, payment reconciliation, security or a legal duty. When the purpose ends, we remove, anonymise or restrict the record where that process applies.

Use the signed-in account help route and state that your request concerns the Privacy Policy. For DANA, OVO, GoPay or QRIS records, add the date and transaction reference, while keeping passwords and full wallet credentials private.