Reference

jurnal4d Privacy Policy For Your Account

jurnal4d Privacy Policy explains how we collect, use and protect details connected with your account, wallet activity and support requests.

Account clarityWallet recordsDirect contact
jurnal4d jurnal4d Privacy Policy For Your Account
CONTACT THE TEAM

Privacy Help Along Your Account Path

A clear contact route matters when you want to ask about personal data rather than a lobby feature. We handle privacy questions through the support path linked to your account, so we can match a request with the correct account record without asking you to post private details publicly. Include the phone number or account identifier used for access, the subject of your request and any relevant receipt reference. We may ask for an account step or phone verification before discussing protected details. Support is available every day from 08:00 to 23:00 WIB through live chat.

Team online

Privacy request

Use live chat from your signed-in account to ask what account details we hold, why a field is needed or how to request a correction. We keep the conversation attached to the relevant case so our team can follow the request without exposing it in a public channel.

Access concern

If your account opens on desktop but not on your phone, tell us the device path, browser and approximate time. We use those details to separate a security check from a privacy request, then explain the next account step without asking for your wallet PIN.

Receipt question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, send the transaction reference through live chat rather than a public message. Our team can check the account trail and explain which data is retained for status handling.

DATA HANDLING

What We Do With Your Personal Details

We keep this policy connected to the actions you take, not to vague promises. Account creation, phone verification, wallet status checks and support conversations each create different records…

Account data

We may hold your account identifier, contact details and phone verification result so we can connect a sign-in with the…

Wallet context

DANA, OVO, GoPay and QRIS references, along with bank transfer or virtual account details, can form part of a payment…

Cookies

Cookies and device signals can preserve a signed-in session, remember a selected path and flag unusual access.

Account security

We use sign-in events, device information and phone verification to help protect account access.

Retention

We retain records for the period needed to provide the requested account service, investigate security events, answer disputes and meet…

Changes and contact

You can ask for access to personal details, correction of an inaccurate field or clarification of a processing purpose through…

Privacy Policy Questions About jurnal4d

Searches about a Privacy Policy usually come before an account decision, so we answer the practical points here. These answers describe the account, device and wallet records we may handle, along with the contact steps for a privacy request. If your circumstances involve a different country or access condition, the outcome depends on local law. For a record-specific answer, use live chat from the account connected with the request.

The jurnal4d Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support conversations and payment status records. It explains why we use each category, how we protect access and how you can ask about, correct or otherwise request action on your personal details.

Phone verification helps us connect you with the correct account and reduce the chance of protected details being disclosed to another person. We may request it during account access or a privacy request, particularly when a new device or unusual sign-in pattern needs confirmation.

Yes. The Privacy Policy includes account-linked status references for DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to trace a requested payment action, match a receipt and answer a status question connected with your account.

Open live chat from your signed-in account and ask for access to your personal data. State the account identifier and the records you want clarified, such as profile details or support history. We may complete a phone verification step before releasing protected information.

You can request a correction through live chat by identifying the inaccurate field and providing the account identifier connected with it. We may ask for phone verification or another account step before changing the record, so the request cannot be made by someone else.

Cookies can keep your session active, remember a device path and help us detect unusual access. Your browser controls can remove or restrict them, but necessary cookies may be required for sign-in. If access changes afterward, support can help you complete the account path safely.

Use live chat between 08:00 and 23:00 WIB each day, preferably from the account connected with your request. Explain whether you need access, correction, retention clarification or a security explanation. Do not send wallet PINs or full authentication secrets in the message.