Reference

Privacy Policy for Your jproyal Account

jproyal Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests

Browse Our Lobby Read FAQ

How Privacy Policy Applies Locally

jproyal Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details supplied during account creation, including contact information, verification records and security events connected with your sign-in. It also covers payment references when you use DANA, OVO, GoPay, QRIS, a virtual account or bank transfer, including BCA, BRI, Mandiri and BNI routes.

1
We use these records to match account activity, investigate unusual access and keep transaction histories accurate. Device type, browser settings and approximate network details can be recorded when you enter the lobby. Access depends on local law, and we may update this policy when our data
2
practices change. The current page explains the practical request routes available to you.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT YOUR WAY

Get Privacy Policy Help Without Guesswork

A clear contact route helps when you need to ask about account records, cookie settings or a verification detail.

Account contact Send a Privacy Policy question through the contact route connected to your account. Include your registered phone or email, the type of data involved and the action you want us to take, such as access, correction or deletion.

Wallet record query If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, identify the payment rail and approximate date. We can then locate the related account record without asking you to share a wallet password or full security code.

Sign-in assistance When a privacy request follows a failed login, tell us whether you are using a mobile browser or desktop browser. We may request account verification before discussing personal data, helping keep the request separate from an unverified access attempt.

DATA HANDLING DETAILS

What We Do With Account Data

Privacy Policy choices are easier to understand when each data use has a practical reason. We use account and device records for sign-in checks, wallet matching, support replies and security investigation rather…

Account creation

When you open an account, we record the details needed to create and maintain it, including your contact route and verification status. Clear phone verification can be required before account access, so we can distinguish an account holder from an unknown sign-in attempt.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, amount, status and timestamp in account records. For bank transfer or virtual account activity, we use the available reference details to reconcile the account without storing your wallet password.

Device signals

Your phone or desktop browser may provide device type, browser version, language and network signals during sign-in. These details help us spot unusual access and troubleshoot a page that behaves differently on mobile, but they do not replace the account verification step.

Cookies

Cookies may keep a signed-in session available, remember a selected setting or show us how a page loads. You can manage cookie permissions through your browser. Blocking some cookies may affect account access or require you to sign in again on the same device.

Security controls

We use account checks, sign-in records and verification prompts to reduce unauthorised access. Never send us a password, wallet PIN or one-time security code. If you notice an unfamiliar session, contact support from the account route and describe the device or time involved.

Retention and changes

We keep records for as long as needed for the stated service, security, dispute and legal purposes, then review whether continued storage is necessary. You can ask what we hold, request a correction or ask about removal; access depends on local law and the record involved.

Privacy Policy Answers for jproyal

These Privacy Policy answers address the searches we hear most often before account creation. They explain what may be collected, how wallet references are handled, what happens on a mobile device and how to send a request. If your situation is unusual, contact us with the account detail you can safely share, and we will route the question to the right support path.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. That includes activity linked to DANA, OVO, GoPay, QRIS, virtual accounts and bank transfers. We explain each purpose so you can understand why a record may exist.

We use the available payment reference, status, amount and time to connect a DANA or QRIS action with the correct account and resolve a status question. We do not ask for your wallet password or PIN. The Privacy Policy also describes related OVO and GoPay records.

Yes, you can contact us through the account support route and ask which personal records we hold about you. Include your registered phone or email so we can verify the request. We may limit or refuse part of a request where local law permits or requires it.

Yes. When you sign in from a phone, the site may record device type, browser version, language and network signals for security and troubleshooting. Cookie settings can also affect the mobile session. You may be asked to verify your phone before account details are discussed.

We retain payment references for the period needed for account administration, security checks, disputes and legal duties, then review whether storage remains necessary. The period can vary by record and applicable rules. Ask support about a specific DANA, QRIS or bank transfer reference.

Send a correction request through the contact route linked to your account and identify the inaccurate field. We may ask for verification before changing contact, phone or payment-related details. This protects your account from an unauthorised change and lets us explain any restriction.

You can ask about deletion through account support, but removal depends on local law and the record's purpose. Some details may need to remain for security, transaction reconciliation, disputes or legal duties. We will explain what can be removed and what must be retained.

Privacy Policy for Your jproyal Account

Get Privacy Policy Help Without Guesswork

What We Do With Account Data

Account creation

Payment references

Device signals

Cookies

Security controls

Retention and changes

Privacy Policy Answers for jproyal

01 What does the jproyal Privacy Policy cover?

02 How does jproyal use my DANA or QRIS data?

03 Can I request a copy of my jproyal account data?

04 Does the Privacy Policy cover mobile browsing?

05 How long does jproyal keep payment records?

06 How can I correct information in my Privacy Policy record?

07 Can I ask jproyal to remove my personal data?

Related Pages