Reference

juragan999 Privacy Policy For Your Account

The juragan999 Privacy Policy explains what we collect when you open an account, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
juragan999 juragan999 Privacy Policy For Your Account
CONTACT OUR TEAM

Three Ways To Ask About Privacy

A direct contact route helps you understand the Privacy Policy before you open an account or when a wallet record looks unfamiliar. We ask you to include the account phone number, the relevant date and the payment reference, while leaving out any wallet PIN or password. Our team can then locate the right record, explain the reason for collection and send a correction or access request to the appropriate queue.

Team online

Account message

Use the account support message path for a copy of the personal details linked to your sign-in. Include your registered phone number and say whether you want access, correction or deletion guidance. We may request an account step to confirm that the request comes from you.

Payment receipt

For a DANA, OVO, GoPay or QRIS privacy question, attach the payment reference rather than a wallet password. We use the reference to separate transaction metadata from your private wallet credentials and can explain why the record is held or how a mismatch is corrected.

Login assistance

If a sign-in check stalls, contact support through the account help route and describe the device path you used, such as mobile browser or desktop browser. We use that detail to investigate access logs without asking you to send a password, PIN or full wallet screenshot.

DATA HANDLING DETAIL

Six Privacy Controls Behind Your Login

We keep the Privacy Policy practical by linking each data category to a clear account purpose.

Account identity

When you create an account, we collect the details needed to establish your profile and complete phone verification before account access. We use the registered contact to send account messages and to distinguish your request from another person asking about the same record.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, timestamp and status in our records. Bank transfer and virtual account activity may also show a BCA, BRI, Mandiri or BNI reference. These details help us trace a payment without storing your wallet PIN.

Device signals

A mobile browser or desktop browser may provide session, language and device signals around sign-in. We use them to keep the account path working and investigate access that does not match your normal pattern. Mobile APK Download pages should be reached through our stated account path.

Cookies

Cookies can remember a session choice, keep a page consistent and help us see whether a sign-in step completed. You can manage cookie settings in your browser, although removing some cookies may require you to repeat phone verification or other account checks.

Account protection

We do not ask for your wallet PIN or account password in a support message. Keep those credentials private, complete phone verification only through the account path and tell us promptly if an unfamiliar device or payment reference appears in your account history.

Retention requests

We retain a record only for its stated account, payment, security or legal purpose, subject to periods that may apply where local law permits. Contact support with the record type and date if you want a retention explanation, correction request or available deletion assessment.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you are most likely to have before opening an account or asking us to inspect an existing record. We explain the account step, payment references, device behaviour, cookies and request process in plain English for Indonesian customers. Service access depends on local law, and our support path is available for a question that needs account-specific checking.

The juragan999 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies and payment references. It explains why we collect each category, how we use it to support account access or payment checks, how retention is assessed and how you can ask for access or correction.

Yes. Privacy Policy treatment includes the reference, time, amount and status connected with a DANA, OVO, GoPay or QRIS transaction. We use those details to match a wallet event to your account. We do not need your wallet PIN, and you should never send it to support.

We use your phone number to create the account record, complete phone verification before account access and send account-related replies. It also helps us separate your request from another account. If the number is inaccurate, contact support with the correct detail and be ready for an account ownership check.

The Privacy Policy describes cookies as small browser records that can maintain a session, remember page settings and show whether a sign-in step completed. You can adjust them in your browser. Removing necessary cookies may sign you out or make phone verification repeat on your next account visit.

You can ask for a copy of account data or request correction of an inaccurate detail through support. Include your registered phone number, the category concerned and the reason for the request. We may verify account ownership first, and we will explain any limit that depends on local law.

Retention depends on why the record exists, such as reconciling a QRIS status, checking a virtual account reference or protecting account access. We keep it only for the applicable operational or legal period where local law permits. Ask support about a specific date and reference for a clearer response.

Use our account support message path and identify your question as a Privacy Policy request. Add the registered phone number, record date and payment reference when relevant, but never include a password or wallet PIN. We can explain collection, access, correction, cookies or retention through that contact route.