Reference

Privacy Policy for Your permata 123 Account

Your account details, phone verification and wallet activity receive a clear Privacy Policy at permata 123.

Account dataWallet activityPhone checksPolicy requests
permata 123 Privacy Policy for Your permata 123 Account
CONTACT ROUTES

Policy Help For Wallet And Login Questions

A clear contact path helps when your Privacy Policy question involves login, a wallet reference or a phone check.

Account access If a phone verification step blocks account access, tell us which device path you used and what appeared on screen. We use the minimum detail needed to identify the account record and explain how the Privacy Policy applies to that request.
Wallet status For DANA, OVO, GoPay or QRIS questions, include the payment reference and its visible status rather than private wallet credentials. We can then check the relevant account record and describe the data held for that cashier event.
Policy request To ask about collection, correction or deletion, state the specific account detail and the action you want. We may need an account check before responding, so we do not disclose private records to the wrong person.
DATA PRACTICE

Account Data Behind Your Lobby Access

The Privacy Policy is put into practice across the account path, from phone verification to a mobile return to the lobby.

Data we collect

We may handle account identifiers, contact details, phone verification results, device or session signals and payment references. The purpose is to provide account access, connect a cashier event to your account and respond to a specific Privacy Policy request.

Cookie choices

Cookies can keep a session active or remember a device preference when you move from login toward the lobby. Your browser settings can restrict or remove them, although a restricted session may require another account check.

Account security

Phone verification is used before account access, and we do not ask you to place a password or wallet PIN in a support message. This reduces exposure while we investigate login or payment-status questions.

Retention approach

We retain account, security and payment-reference records for the period needed to operate the service, address disputes or meet a legal need. When a record is no longer required for those purposes, our handling moves toward removal or aggregation.

Change requests

You can ask us to correct an inaccurate account detail or explain why a field is held. Include the affected detail and your requested change; we may confirm account ownership before making any amendment.

Who to contact

Our policy contact route handles questions about access, cookies, payment references, retention and account data. Describe one issue per request and include only safe identifiers, allowing us to give a focused response without excess personal detail.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to meet when accessing permata 123 from Indonesia. We explain the connection between account data, phone verification, cookies and local wallet references without turning the policy into a general lobby description. If your circumstances involve eligibility or access, the outcome depends on local law and applies where local law permits.

The Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references and policy requests. It explains why we handle each category, how it supports account security or status checks, and how you can ask about correction, retention or removal.

We use phone verification before account access to help connect the person entering the account with the correct record. The result can support login security and a policy response, but you should not send your password, wallet PIN or full private credentials through a contact request.

Yes. When DANA or QRIS is used, we may handle a payment reference, visible status and related account details to match the cashier event or investigate a stalled status. We do not need your wallet PIN for that check, and you can ask what record is held.

OVO and GoPay activity can create reference and status data connected with your account. We use those details for account operation, security and support handling, not as a reason to request your private wallet credentials. A policy request can ask us to explain the relevant record.

Yes. State the account detail you believe is inaccurate and the correction you want through the policy contact route. We may confirm ownership with a suitable account step before changing it, which helps prevent another person from altering your private record.

We keep account, security and payment-reference records only while they support service operation, dispute handling or a legal need. The retention period can differ by record type. You can ask which category applies to your request and why it remains necessary.

Cookies may help maintain a session or remember a device preference as you move from login toward the lobby. You can restrict them in your browser, but that may remove a saved session and cause another account or phone check before access.