Reference

Privacy Policy for Your juliet4d Account

juliet4d Privacy Policy explains how we collect, use and protect the details linked to your account, wallet status and lobby access.

Account clarityWallet record careCookie choicesPolicy requests
juliet4d Privacy Policy for Your juliet4d Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A privacy question should not be mixed into a general cashier request, so we keep the route clear. Use the account support path when you need help finding a stored detail, checking a phone-verification record or asking why a payment reference is attached to your profile. If you are using a mobile browser, open the account menu first and select support; on desktop, use the same account support link. Include your registered contact detail and the specific request, but do not send a wallet password.

Team online

Account request

Ask us to access, correct or explain personal details connected with your account. Include the registered phone contact and the exact record you mean, such as a QRIS receipt or phone-verification entry, so we can route the request accurately.

Wallet query

For DANA, OVO, GoPay, bank transfer or virtual account records, describe the payment reference and date without sharing a password or one-time code. We use those details to check the account trail while keeping your wallet credentials private.

Access help

If a cookie setting, device change or login check blocks your policy request, contact support from the account menu. We may ask for a verification step before discussing personal data, which helps prevent disclosure to the wrong person.

DATA HANDLING

The Practical Privacy Steps We Follow

Our privacy process follows the same account path you use to reach the lobby: identify the account, verify the request, check the relevant record and then apply the permitted change.

Account details

We may collect your registered contact details, verification status and account activity needed to provide access and answer a privacy request. We use the minimum context required to locate your record rather than asking you to repeat unrelated personal details.

Payment matching

DANA, OVO, GoPay and QRIS references can identify which account activity needs checking. Bank transfer and virtual account records may be handled in the same way. We do not ask you to reveal wallet passwords, PINs or one-time codes.

Cookie control

Necessary cookies can keep your session open and remember basic access settings on your device. Optional cookies, where used, can be managed through the browser controls available on your phone or desktop, without sending us your account password.

Account security

Phone verification, login signals and device checks help us confirm that a privacy request comes from the account holder. If activity looks unusual, we may pause discussion of personal records until an additional account check is complete.

Retention period

We keep personal and payment records only for the period needed for account operation, security checks, dispute handling or a lawful obligation. When a record is no longer needed, our handling process can remove it or separate it from direct account identifiers.

Change requests

You can ask us to correct inaccurate details, explain how a record is used or request removal where applicable. Send the request through account support, name the exact data involved and complete verification before we discuss or change it.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the requests we expect from someone opening or maintaining a juliet4d account in Indonesia. They explain the records behind phone verification, wallet matching, cookies, device access and account support. If your question involves a specific receipt, login event or data correction, use the support route above and identify the record clearly. Requests are handled where local law permits and may require proof that you control the account.

The Privacy Policy covers personal details, phone verification, login and device signals, cookies, payment references and support messages connected with your account. It also explains retention, security checks and how to request access, correction or removal where local law permits.

Phone verification helps us connect an account request with the correct account holder and reduce mistaken disclosure. We may use the verification status when you ask about DANA, QRIS, OVO or GoPay activity, but we will not ask for your one-time code.

Yes. The Privacy Policy covers payment references from DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity when those records are connected with your account. We use them to match receipts, investigate status and answer data requests.

Open account support from your mobile browser or desktop account menu and request access to your personal data. State the registered contact detail and the records you want, such as phone verification or a payment reference. We may verify account control first.

You can request correction when a personal detail is inaccurate or incomplete. Tell us which field needs changing and provide the correct value through account support. We may compare the request with your phone-verification record before applying an update.

Necessary cookies can support login sessions and basic device access, while other cookie settings may depend on your browser. You can check cookie controls on your phone or desktop. Clearing necessary cookies may require you to sign in and complete access checks again.

We retain account, security and payment-related records for the time needed to operate the account, investigate disputes, protect access or meet a lawful obligation. When retention is no longer needed, records may be removed or separated from direct identifiers where local law permits.