Reference

Open the pak jp Privacy Policy

The pak jp Privacy Policy shows what we collect when you open an account, verify your phone and move between the lobby and local wallet options.

Account dataWallet recordsCookie choicesContact requests
pak jp Open the pak jp Privacy Policy
CONTACT ROUTES

Contact us about Privacy Policy

You can raise a Privacy Policy question through the support route available after account access, without sending wallet passwords or one-time codes.

Account access Use the account support path when you cannot reach your privacy settings.
Wallet records For a DANA, OVO, GoPay or QRIS record question, include the payment rail and…
Privacy requests Ask us to correct, remove or explain a data record through the available contact…
HANDLING PRACTICE

See how we handle your data

We apply the Privacy Policy across the account path rather than treating it as a separate page.

Account security

Phone verification is part of account access. We use sign-in and device signals to identify unusual activity, and we do…

Device behaviour

Our browser pages may receive device, browser and session details when you move from login to the lobby on mobile…

Cookies

Cookies can remember session choices and help us understand page errors.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account events can create reference data.

Retention

We keep account, security and payment records only for operational, dispute or legal needs described by the Privacy Policy.

Change requests

You can ask us to correct account data, explain its use or request removal.

Ask about pak jp Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or sending a request. We explain the practical steps for phone verification, browser access, wallet records and data changes, while keeping eligibility wording clear: access depends on local law. If your case is not covered here, use the account support route and describe the record you need checked.

It covers account details, phone verification, sign-in activity, device and browser data, cookies, wallet references, support messages and retention. It also explains how to request correction, deletion or clarification through the account contact route.

Phone verification helps us confirm account ownership before access or a privacy request is completed. It also reduces the risk of another person receiving account details. We do not need your DANA, OVO, GoPay or QRIS password.

Yes. The Privacy Policy covers payment references and status events linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match an account action without collecting your wallet login credentials.

You can ask us to explain, correct or provide eligible account records through the available support route. Include the phone number on your account and describe the data involved. We verify ownership before processing the request.

Cookies may keep your session active and help identify page errors when you use a mobile browser. Browser controls can limit them, but login or saved policy preferences may not work as expected after some cookies are disabled.

We retain account, security, support and payment references for the operational, dispute or legal period connected with their purpose. When that need ends, we follow our retention process, subject to applicable obligations and local law.

Use the support route available through your account and state whether you need access, correction, removal or an explanation. Do not include wallet passwords or one-time codes. If access is unavailable, begin with account help so ownership can be checked.