Reference

Privacy Policy for Your putri jp Account

Our Privacy Policy explains how we handle the details you provide when opening a putri jp account, signing in from a phone, or checking wallet status.

Account clarityWallet recordsCookie choicesIndonesia access
putri jp Privacy Policy for Your putri jp Account
CONTACT ROUTES

Get Privacy Help Through Account Support

A clear contact route matters when you want to understand a record or correct an account detail.

Account desk Use our account support channel for a copy request, correction request or question about…
Wallet check If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account…
Security concern For an unfamiliar sign-in, changed phone detail or device alert, use the account support…
HANDLING DETAILS

What We Do With Your Personal Data

The Privacy Policy is practical: it connects each data use to an account action you can recognise.

Account records

We store details needed to maintain your account, such as contact information, verification status and support history.

Payment references

We receive transaction identifiers and status information for supported routes such as DANA, OVO, GoPay, QRIS, bank transfer and virtual…

Device signals

Browser type, operating system, approximate session details and security events can be recorded when you sign in.

Cookies

Session cookies keep you signed in during an active account path, while preference cookies remember settings where available.

Retention

We retain personal data while it supports account operation, security checks, support handling or a legal requirement.

Your request

You may ask what personal data we hold, request a correction, ask about deletion where applicable, or question a specific…

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening or using an account. They explain the practical link between your account step, a local wallet reference, mobile access and a request to our support team. If your situation is not listed, contact us with the smallest amount of detail needed to locate the issue.

It covers account details, phone verification, device and browser signals, cookies, support messages, payment references and retention. It also explains how we respond to access or correction requests, including situations where account access depends on local law.

Yes. We may handle a transaction reference, status and timing connected with DANA, OVO, GoPay or QRIS. We use that information to match activity and check a wallet issue; we do not need your wallet PIN or full authentication code.

Phone details support verification before account access, while device and browser signals help identify an unfamiliar sign-in. These checks can protect your account when you switch from a mobile browser to desktop, and they do not replace your password.

Contact our account support route and state whether you want a data copy or a correction. Include your registered contact detail and a short description of the record. We may ask for reasonable identity confirmation before sharing or changing account-specific data.

We keep records while they are needed for account operation, security, support handling or a legal requirement. After that need ends, we remove or anonymise the record where applicable. A support agent can explain the reason a particular record remains.

Yes. Your browser settings can block or remove cookies, including session cookies. If you clear them, you may need to sign in again and some account-path preferences may not remain. We describe cookie purposes in the Privacy Policy so you can choose knowingly.

Use account support for privacy questions, a correction request or an unfamiliar device alert. For wallet-related data, include the date and status connected with the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, but never send a password or PIN.