Reference

prima555 Privacy Policy For Your Account

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

Account dataWallet recordsCookie choicesAccess depends on local law
prima555 prima555 Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear support path helps you ask about the Privacy Policy without repeating your account history.

Policy request Use the support contact in your signed-in account to ask how the Privacy Policy…
Wallet record When a privacy question concerns DANA, OVO, GoPay or QRIS, share the payment name…
Access concern If a sign-in from your phone looks unfamiliar, use the account support route and…
DATA HANDLING

What We Keep And Why

Privacy work is practical: we separate account details, device signals, cookie settings and payment records so each request has a clear purpose.

Account details

We collect the details needed to create and verify your account, including the phone step used before account access. We use them to maintain your profile, respond to requests and connect activity to the correct account.

Device signals

A phone or desktop sign-in can create device and session signals. We use these signals to spot unusual account access and investigate a security request. They are not a substitute for your password, PIN or one-time code.

Cookie controls

Cookies can remember a session, language setting or page preference. Your browser provides controls to remove or restrict them. Some account functions may need a session cookie to keep the signed-in path working correctly.

Payment records

A payment record can show a rail name, status, date and account reference. This lets us check whether DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity belongs to your request.

Retention period

We keep records for account service, security checks, dispute handling or legal duties, then remove or restrict them when the relevant purpose ends. The period can vary by record type and the request being handled.

Changes and requests

Ask us to correct an account detail, explain a data use or address a cookie concern through the signed-in support route. We may ask for an account step to confirm that the request comes from you.

Privacy Policy Questions Before Sign-In

These Privacy Policy answers address the searches we expect before an account is opened or a wallet record is checked. They cover account access, device behaviour, cookies, payment references and requests for changes. When a question involves eligibility or regional access, the answer depends on local law, and our support route can explain the applicable account step.

The prima555 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment status records and support requests. It also explains why we use each category, how long records may be kept and how you can ask for a correction or clarification.

We use the phone verification step to create or confirm the account linked to your request. It helps us distinguish one account from another when you sign in, ask for a data change or report an unfamiliar device. Never send your password or one-time code to support.

Yes. The Privacy Policy covers payment references and status records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use the rail name, date, status and account reference to investigate a request without needing your wallet PIN.

Cookies can keep a signed-in session, page setting or language choice available while you move through the account area. You can restrict or remove them in your browser. If a session cookie is blocked, you may need to sign in again before requesting account support.

You can request a correction through the support contact shown in your signed-in account. State which detail is wrong and what it should say. We may ask you to complete an account verification step before changing the record, so the request remains tied to you.

Retention depends on the record and its purpose. We may keep account, payment and support records for service, security checks, dispute handling or legal duties. When the relevant purpose ends, we remove or restrict the record according to our internal handling process.

Account access and eligibility depends on local law. Our Privacy Policy is written for the account and data steps available in Indonesia, but your location and circumstances can affect access. Use the signed-in support route when you need a region-specific clarification.