Reference

Privacy Policy for Your pkjp Account

Our Privacy Policy explains how pkjp handles the details you provide when you open an account, verify your phone and use local wallet routes such as DANA, OVO…

Account clarityWallet data careSimple requests
pkjp Privacy Policy for Your pkjp Account
POLICY HELP DESK

Get Help With a Privacy Request

A clear contact path helps when you want to ask about the Privacy Policy or the data connected with your account. Send your request through our account support route, and include the phone number linked to your profile plus the topic you want checked. We use those details to find the correct record without asking you to send a wallet password or one-time code. If a DANA, OVO, GoPay or QRIS reference is involved, keep the receipt number ready so our team can separate payment status from personal data questions.

Team online

Account support

Use the support route attached to your account to ask how your personal details are used under our Privacy Policy. Include your registered phone number and request type, but never send your password, PIN or one-time verification code in a message.

Wallet records

For a Privacy Policy question involving DANA, OVO, GoPay or QRIS, share the transaction reference rather than full wallet credentials. We can check which record is held, why it is needed and whether a correction request can be processed.

Receipt checks

A bank transfer or virtual account receipt helps us locate the right payment record when you ask about stored data. We compare the reference with your account details and explain the result without requesting access to your banking password.

DATA CONTROL POINTS

What We Do With Your Account Data

The Privacy Policy is practical at each account step, from phone verification to a return visit on mobile or desktop.

Account details

We use your registered account details to create access, verify the phone connected with the profile and send account-related messages. If a name or phone detail is wrong, contact support with the correction you want and enough context to identify the account.

Payment references

Wallet names, bank transfer references and virtual account records help us match a deposit or status enquiry to the right account. We do not need your wallet PIN or banking password for a Privacy Policy request.

Cookies and sessions

Cookies can keep your login session active, remember selected page settings and help us detect a suspicious session. You can manage browser cookie controls, although removing essential cookies may require you to verify your phone again.

Device signals

A mobile browser or desktop session may provide device and connection signals used to protect account access. These signals help us spot repeated login attempts and do not replace the phone verification step required before account access.

Retention choices

We keep personal records for the period needed to operate the account, resolve payment references, protect access or meet a legal requirement. After that need ends, we remove or anonymise the record through our retention process.

Change requests

You can ask to access, correct or clarify personal data connected with your account. State the request plainly, confirm the registered phone number and tell us whether it concerns login data, cookies, device signals or a DANA, OVO, GoPay or QRIS record.

Privacy Policy Answers for pkjp

These Privacy Policy answers focus on the requests you may make before opening an account or while checking a wallet record. We keep the route practical: identify your account, describe the data question and provide the relevant reference only when needed. Access remains subject to local requirements and depends on local law.

It covers account details, phone verification, payment references, device signals, cookies and support messages connected with your use of pkjp. It also explains why we use each category, how retention works and how you can ask for access or correction.

Yes. The Privacy Policy covers transaction references linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account references. We use them to match payment status and respond to account questions, not to request your wallet PIN.

Use the account support route and state that you want a data access request under the Privacy Policy. Include the phone number registered to your profile and describe the records you want checked, such as cookies, device signals or payment references.

You can ask for a correction when an account detail is inaccurate or incomplete. Tell us which field needs changing, confirm the registered phone number and provide the reason for the request. We may need an account check before applying an update.

We keep data for the time needed to provide account access, protect the account, reconcile a wallet or transfer record, resolve support matters or meet a legal requirement. When that purpose ends, we remove or anonymise the relevant record.

Yes. It explains that cookies can maintain a mobile browser session, remember page settings and support security checks. If you block essential cookies, the site may ask you to sign in or complete phone verification again before access.

Yes. Send the concern through the account support route and describe the policy topic clearly. For a wallet or transfer question, add the receipt reference, but do not include your password, wallet PIN or one-time verification code.