Reference

Privacy Policy for Your okjp Account

Our Privacy Policy explains what data we collect when you open an okjp account, use the lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet recordsCookie choicesSecurity requests
okjp Privacy Policy for Your okjp Account
HELP WITH PRIVACY

Get Help When A Data Request Stalls

A clear request route helps you resolve privacy questions without repeating your account story.

Account help path Use the account help route when you need a copy of your personal data…
Payment record check If a wallet receipt or bank transfer status appears wrong, send the transaction reference…
Access concern When a privacy concern follows an unfamiliar login or device event, describe the device…
DATA CONTROL DETAILS

What You Can Check And Change

Privacy is easier to manage when the practical steps are visible. We separate account identity details from payment status records, limit internal access to what a support or…

Data collected

Account creation can involve your name or contact detail, phone verification status, login activity and support messages.

Cookie settings

Cookies can keep a session active, remember a selected language or help us understand which privacy page step needs clearer…

Account security

Phone verification is an account access step, and device and login signals help us identify unusual activity.

Retention period

We keep account, security and payment-status records only for the period needed for the purpose described in this policy, including…

Your requests

You can ask what personal data we hold, request a correction, ask about use, or request deletion where applicable.

Policy contact

For a Privacy Policy question, state the request clearly and use the contact route shown in account help.

Answers About The okjp Privacy Policy

These Privacy Policy answers focus on the account and records you may encounter when using okjp from Indonesia. They cover the points that usually matter before account access: what we collect, why payment references appear, how cookies work, and where to send a request. If your situation is unusual, include the relevant account step or transaction reference so our support team can assess it without asking for unnecessary credentials.

The Privacy Policy covers account details, phone verification, login and device signals, support messages, cookies, and payment-status records. It explains why we use each category, how we protect access, how retention works, and how you can ask about, correct or delete eligible personal data.

A DANA or QRIS reference helps us connect a payment request with the correct account and status. We may need it to check a missing receipt, duplicate request or unresolved cashier record. We do not need your wallet password or complete banking credentials for that check.

Yes, you can send a data access request through the account help path. Tell us which account contact detail applies and whether you want account, cookie, security or payment-status records. We may verify account ownership before sharing data, so another person cannot request it for you.

Use account help and describe the detail that needs correction, such as an outdated phone number or an incorrect support record. Include the relevant account step or receipt reference when useful. We review the request against account ownership and update eligible records after verification.

On a mobile browser, cookies may keep your session, remember a setting and help us measure page use. Your browser controls can restrict them, although login preferences may need to be entered again. We do not treat cookie settings as permission to request unrelated account details.

We retain payment-status and security records for the period needed to operate the account process, investigate disputes, protect access and meet legal duties. After that period, we delete or anonymise them where appropriate. You can ask support why a particular record remains available.

Send your Privacy Policy request through the account help route near the cashier path. Describe the action you want, such as access, correction, deletion or a security check, and include only the account detail needed to locate it. Never include a password or wallet secret.