Reference

pgraja Privacy Policy For Your Account

pgraja Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount access choicesDirect policy requests
pgraja pgraja Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Your Data

A clear contact route helps you correct an account detail without sending sensitive information to the wrong place.

Account support Use the support channel available after sign-in for questions about your profile, phone verification…
Cashier records For a wallet reference or payment status question, choose the cashier support route and…
Policy request Ask for access, correction or clarification through the policy contact route shown on our…
DATA PRACTICE

Six Privacy Steps Inside pgraja

Privacy is handled through practical account controls rather than a single promise. We separate sign-in checks from payment references, explain why cookies support a session, and keep request handling tied to the…

Collected details

We may receive contact details, verification details and account activity when you create or use an account. Technical data from your device and browser can help us detect a sign-in pattern, maintain a session and investigate unusual access without treating every device as the same.

Cookie choices

Cookies can keep your signed-in session working, remember practical preferences and help us understand whether a page request belongs to your account. You can manage cookie controls in your browser, although restricting them may affect the login path or the way policy pages load.

Account security

Phone verification before account access gives us an extra check when you sign in or need help. Keep your password and wallet credentials private; our support route does not need your full wallet password to investigate a DANA, OVO or QRIS reference.

Payment matching

A payment reference, method, amount and status can be retained to match a deposit or account adjustment. This applies to QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity, helping us trace a receipt without storing unrelated wallet content.

Retention period

We keep information only for as long as it supports the purpose described in the Privacy Policy, account security, payment reconciliation or a legal duty. When a record is no longer needed for those reasons, our handling follows the applicable deletion or anonymisation process.

Your requests

You can ask what account data we hold, request a correction, or ask how a record is used. Send the request through the policy contact route with your account identifier; we may verify ownership first, then explain the available action and any local-law limit.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or linking a local wallet. They explain access, cookies, payment records, corrections and contact steps in plain English. If your situation is not covered, use the support path shown in your account and include only the details needed to identify your request.

It covers data you provide for an account, information created through sign-in and account activity, cookie use, payment references and support requests. It also explains security, retention, correction requests and the circumstances in which local law can affect access or a requested action.

We keep the payment method, reference, amount, time and status needed to match a transaction to your account and answer a receipt question. The same approach can apply to OVO, GoPay, bank transfer and virtual account records, without needing your wallet password.

Yes. Use the policy contact route shown on our site and identify the account detail that needs correction, such as a phone number or contact field. We may ask you to complete phone verification or another account check before changing private information.

Cookies may keep your session active, remember selected settings and help connect a page request with your account. You can adjust them through your browser controls. If you block required cookies, login, phone verification or the route from mobile access to the lobby may not work as intended.

Retention depends on why the record exists. Account security, payment reconciliation, support handling and legal duties can require different periods. The Privacy Policy explains the purpose-based approach, and you can ask support about a particular record without sending your password or full wallet credentials.

Send an access request through the policy contact route or the signed-in account support channel. Include the email or phone linked to your account and describe the data you want clarified. We verify ownership before sharing account details, and any response depends on local law.

The same policy is intended for accounts connecting from Indonesia, including mobile access in Semarang. Specific eligibility, access or legal requests may differ because they depend on local law. Check the current page and contact us when you need the rule applied to your account.