Reference

jewel4d Privacy Policy, Made Clear

Our jewel4d Privacy Policy explains what account details we collect, why wallet records matter, and how you can ask about your data before opening an account.

Account dataCookie choicesLocal access rules
jewel4d jewel4d Privacy Policy, Made Clear
DATA HELP ROUTE

Where To Ask About Your Data

A clear support path helps when a login record, wallet reference, or account detail needs attention. Contact us through the account support route and describe the request in plain English, with the email or phone detail attached to your account. For payment questions, include the DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference without sending a password or security code. We use the details you provide to locate the relevant record, confirm ownership, and respond to the specific Privacy Policy request.

Team online

Account request

Ask us to check, correct, or explain account data by using the support route connected with your jewel4d account. We may confirm the phone or email already attached before discussing records.

Wallet record

For DANA, OVO, GoPay, QRIS, or bank transfer questions, share the transaction reference and date. We can use those details to locate payment records without asking for your wallet password.

Security concern

If a sign-in or phone verification record looks unfamiliar, tell us through account support as soon as possible. We can review the account event and explain the next verification step.

SIX DATA CONTROLS

Six Controls Behind Your Account Data

We keep this Privacy Policy practical by linking each data use to an account action you recognise.

Data collection

We collect details you submit during account creation, phone verification, support contact, and payment status checks. This can include contact details, account events, device signals, and transaction references.

Cookie choices

Cookies and similar browser signals can help keep a mobile login active, remember selected settings, and measure page function. Your browser controls can limit cookies, though some account steps may then need repeating.

Account security

Phone verification and sign-in records help us confirm account ownership and examine unusual device activity. Never send us a password, one-time code, or wallet security credential in a support message.

Record retention

We retain account, payment, and support records for the operational, security, dispute, or legal reason that requires them. When a record is no longer needed for that reason, our process allows removal or secure disposal.

Your requests

You can ask us to explain, correct, or review eligible account data through support. Include the account phone or email and a clear request; we may verify ownership before making a change.

Policy access

You can return to this Privacy Policy from the policy area of our site on mobile or desktop. If access or eligibility is discussed, it depends on local law and the rules applicable to your location.

Privacy Policy Questions For Indonesia Accounts

These Privacy Policy answers focus on the account and wallet questions you are most likely to check before joining. We explain the data connected with phone verification, mobile browsing, cookies, payment references, support requests, and account changes. If your situation involves a local restriction or a particular legal right, the available response depends on local law, so include your location and account context when contacting us.

It covers account details, phone verification, device and login events, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps confirm that you control the account during access and selected account requests. We use the related record for account security and do not ask you to share the verification code in support messages.

Yes. It explains how browser cookies or similar signals can support a mobile login, remember settings, and assess page function. Your browser controls can limit them, although some steps may need repeating.

We may retain a payment reference, route, amount status, date, and account connection needed for reconciliation or support. We do not need your DANA or QRIS wallet password to check that record.

Use the account support route and state which detail needs correction. Include the phone or email attached to your account, explain the change, and complete an ownership check where we request one.

You can send a removal request through support. We assess which records are eligible and whether operational, security, dispute, or legal needs require retention; the result depends on local law.

Yes, where local law permits, you can ask for an account data explanation through support. Give us your account contact and a specific period or activity, such as a QRIS status check.