Reference

jand4d Privacy Policy for Your Account

The jand4d Privacy Policy explains what account, device and wallet details we use, why we use them, and how you can ask about your records.

Account recordsWallet checksCookie choicesAccess requests
jand4d jand4d Privacy Policy for Your Account
PRIVACY HELP DESK

Where To Ask About Your Privacy Policy

A clear contact route matters when a privacy question affects your account or wallet status. Use the support contact shown inside the jand4d account area and describe the exact request, such as correcting a phone number, checking a device record, or asking why a receipt is linked to your profile. We may request an account step or verification detail before discussing private records. This protects you when support is reached from a new phone or browser in Surabaya.

Team online

Account privacy request

Send your request through the account support path and include the email or phone detail connected to your profile. We use an account check before sharing personal records, changing contact data or discussing a DANA, OVO, GoPay or QRIS reference.

Access and correction

Ask us to confirm the data we hold, explain its use or correct an inaccurate account field. A clear description helps us locate the right record, while the verification step prevents another person from receiving details about your login, device or wallet activity.

Receipt and status query

If a payment receipt or wallet status looks unfamiliar, contact support from the account area and keep the transaction reference ready. We compare the reference with the account record; never send a wallet PIN, password or full authentication code in a message.

SIX PRIVACY CONTROLS

What We Protect Across Each Account Step

Privacy is handled through ordinary account controls rather than hidden settings. We limit access to personal records, separate payment references from wallet passwords, and use device signals to review unusual login activity.

Collection purpose

We collect only the account and activity details needed for access, security, support and required records. A phone verification step can confirm that an account action belongs to you, while payment references help us trace DANA, OVO, GoPay and QRIS status.

Device signals

Your browser and device may provide language, operating system, session and sign-in timing signals. We use these details to identify unusual access and protect the account path. They do not give us your device files, wallet PIN or unrelated private content.

Cookies

Necessary cookies keep a verified session connected as you move from login to the lobby or account page. Measurement cookies may help us see whether a page loads correctly. Browser controls let you remove or restrict cookies, subject to functions that require an active session.

Account security

We treat login credentials, phone verification details and support conversations as private account material. We may pause a sensitive change until the account check is complete. Keep your password and one-time codes private, including when a message appears to mention jand4d.

Retention period

We keep records for as long as needed for the stated purpose, account security, dispute handling or applicable legal duties. When a record is no longer needed, our process may delete it, anonymise it or restrict access according to the reason it was retained.

Your request path

You can ask about access, correction, deletion where available, processing purpose or a privacy concern through account support. Include your account contact detail and request type. We may ask for identity confirmation before acting, and access depends on local law.

Privacy Policy Answers For jand4d Accounts

These Privacy Policy answers address the account questions you are most likely to ask before opening or using a jand4d profile. They cover the data connected with login, device access, cookies, local wallet references and requests sent to support. Where a legal right or access condition differs by location, it depends on local law.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how we protect access, how long records may remain and how you can ask for access or correction where local law permits.

No. Our payment records may contain a reference, status, amount or time needed to match an account action, but your DANA, OVO, GoPay or QRIS wallet password is not something you should send to us. Keep wallet credentials inside the relevant payment service.

Device and browser signals help us recognise unusual login patterns, maintain a verified session and investigate an account access request. We may record device type, browser, language, session timing and related security events. We do not use this process to access unrelated files on your phone or computer.

Yes. Contact support through the account area and state which field is incorrect, such as a phone number or contact detail. We may request an account verification step before making the change. Correction rights and any limits on them depend on local law and the record’s purpose.

Necessary cookies connect your login session to account pages, including the path from verification to the lobby. Other cookies may help us understand page loading and account navigation. You can adjust browser settings, but removing necessary cookies may prevent login, account checks or saved session functions.

Send an access request through the support contact displayed in your account area. Tell us the account contact detail and the records you want us to locate, such as login activity or payment references. We verify the requester first, then respond according to applicable law and available records.

Retention depends on why the information was collected. We may keep account, security, support or payment-reference records for account protection, dispute handling or legal duties, then delete, anonymise or restrict them when they are no longer needed. The applicable period depends on local law and the record type.