Reference

jalak4d Privacy Policy: Your Data Path

jalak4d Privacy Policy explains how we handle the account details, device signals and wallet references connected with DANA, OVO, GoPay and QRIS.

Account recordsWallet referencesCookie choicesAccess requests
jalak4d jalak4d Privacy Policy: Your Data Path
CONTACT ROUTES

Privacy Help When Account Data Stalls

A clear contact route matters when a privacy request and an account check meet. Tell us which account step caused the concern, whether it involves a phone verification record or a DANA…

Account access If your phone verification record blocks account access, contact our support route with the account identifier and the device path you used, such as mobile browser or desktop browser. We use those details to locate the relevant record without asking you to send a wallet password.
Wallet reference For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, include the payment reference and approximate date. We can check the stored status against your account while limiting the reply to details needed for your request.
Data request To ask for a copy, correction or deletion assessment, state the exact data category and the email or phone linked to your account. We may verify ownership before responding, helping prevent another person from receiving your account or device details.
DATA PRACTICE

Six Privacy Controls Behind Your Account

Privacy is handled through practical account controls rather than broad promises. We separate account identity details from payment references where operationally possible, use device signals to identify unusual access, and keep a…

Account collection

We collect details needed to create and maintain your account, including contact information and phone verification results. The account step helps us connect an access request to the correct record before we disclose, correct or remove personal details.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be stored with transaction status and time so our records match the correct account. Bank transfer and virtual account references follow the same narrow purpose and are not treated as wallet passwords.

Device signals

When you move between a mobile browser and desktop browser, we may record technical signals such as browser type, session data and approximate access timing. These signals help us investigate unusual login activity without collecting the contents of your device.

Cookie choices

Cookies can keep your account session active and remember a selected setting. Your browser controls whether optional cookies remain available. If you clear them, you may need to repeat the login or account step when returning to the lobby.

Retention periods

We retain account, support and payment-reference records only for as long as needed for the stated operational purpose, dispute handling and applicable legal duties. When a record is no longer needed, we assess it for deletion or secure removal.

Change requests

You can ask us to correct inaccurate details, explain a data use or assess a removal request. Include the account contact and the specific record involved; we may verify ownership first and then reply with the available next step.

Privacy Policy Questions About jalak4d

These Privacy Policy answers address the account and payment questions we expect from people in Indonesia. Each answer stays focused on data handling, access and contact steps, including the details needed when your request concerns a mobile session, a wallet reference or a phone verification record.

The Privacy Policy covers account details, phone verification, device and session signals, cookie settings, support records and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It explains why we use each category and how you can ask about it.

Yes. The Privacy Policy applies when you access the account or lobby through a mobile browser, as well as desktop browser access. We may record browser type, session data and access timing for security and continuity, but we do not collect the contents of your device.

We may keep a DANA or QRIS payment reference, status and time to match activity with your account and answer a support request. We do not ask for your wallet password. The same limited approach applies to OVO, GoPay, bank transfer and virtual account references.

You can contact us with the account contact and the exact data category you want copied or corrected. We may verify ownership before replying. This helps us send account details to the right person and distinguish a phone verification record from a payment reference.

We keep account, support and payment-reference records for the period needed for their stated purpose, dispute handling and applicable legal duties. We then assess records for deletion or secure removal. A retention question can be sent through the same privacy contact route.

You can ask us to assess deletion of eligible personal data by naming the account and the record involved. Some records may need to remain for legal or dispute reasons. We will explain the available outcome after confirming account ownership.

Our Privacy Policy applies to access where local law permits, and account or service eligibility depends on local law. If you are in Bandung, Medan or another Indonesian location, local rules may affect whether access is available and which data request steps apply.