Reference

jakjp Privacy Policy For Your Account

jakjp Privacy Policy explains how we use the details connected to your account, including phone verification, wallet status and access records.

Account dataWallet checksCookie choicesSecurity requests
jakjp jakjp Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Near Your Account

A clear contact route helps when you want to ask what data we hold, correct an account detail or check why a security step is pending.

Policy questions Send a Privacy Policy question through the account support channel. We can explain the relevant data category, why it is used and what information we need before discussing an account-specific request.
Account corrections If your phone, name or payment reference needs correction, tell us which field is inaccurate. We may ask for a phone verification step before changing account data or connecting a DANA, OVO, GoPay or QRIS record.
Access concerns For an unexpected login or a stalled wallet check, contact support from the same account path where possible. Share the device type, approximate login time and payment rail so we can investigate without requesting a password.
HANDLING DETAILS

How We Manage Privacy Requests

We handle privacy requests alongside the account steps that protect your access. Phone verification helps us distinguish a genuine request from an unrelated message, while device and session records help us examine…

Data we receive

We may receive account contact details, phone verification results, device signals, session activity and support messages. When a transaction is checked, DANA, OVO, GoPay, QRIS, bank transfer or virtual account references can help us match the payment status.

Why we use it

We use account and security data to provide access, confirm that a request comes from you, connect payment status to the correct account and respond to privacy questions. We do not need your password in a support message.

Cookies on devices

Cookies can keep a session connected and help us identify unusual device activity. Your browser controls allow you to remove or restrict them. If required cookies are blocked, phone verification or account access may ask you to repeat a step.

Account security

We use phone verification before sensitive account access and may compare session details when a sign-in looks unusual. Keep your password private, sign out on shared devices and contact us through the account path if a login does not look familiar.

Retention approach

We keep records only while they serve account security, payment reconciliation, support handling, dispute review or a legal requirement. When a record is no longer needed for those purposes, our retention process removes it or separates it from direct account identification.

Change request route

To request access, correction or removal of eligible personal data, contact support through the private route shown in your account. Describe the request clearly; we may verify your phone before acting and may retain limited records where security or law requires it.

Privacy Policy Answers For jakjp

These Privacy Policy answers cover the account situations you are most likely to search for before opening or using an account. We keep each answer tied to an actual jakjp process, from phone verification and cookie settings to wallet references and requests for personal data. Where access or eligibility is discussed, it depends on local law.

The jakjp Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains how we use those details for access, security, payment matching and requests concerning your personal data in supported Indonesia regions.

We may collect the contact details you submit, phone verification results, device signals, login activity and messages sent to support. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, a payment reference may also be recorded for status matching.

Phone verification helps us confirm that an account request comes from you before sensitive access or a data change. It can also help us investigate an unfamiliar session. Never send your password to support; use the private account contact path instead.

Send a data access request through the support channel shown inside your account. State that you are asking for a copy of your personal data and include the account phone number only in that private route. We may verify your phone before processing the request.

Yes, you can ask us to correct inaccurate account details or remove eligible personal data through account support. Explain which record needs action. We may keep limited security, payment or legal records when retention is needed for those purposes.

Cookies can keep your session connected and support security checks on the device you use. You can restrict or delete them through browser settings, but necessary account functions may ask you to repeat login or phone verification when cookies are unavailable.

We retain data while it is needed for account security, payment reconciliation, support handling, disputes or a legal duty. After that period, our process removes it or separates it from direct account identification, subject to any valid request or applicable requirement.