Reference

Privacy Policy for permata 4d Accounts

permata 4d Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA and QRIS for wallet activity.

Account dataWallet recordsCookie choicesAccess requests
permata 4d Privacy Policy for permata 4d Accounts
CONTACT OPTIONS

Privacy Questions Along Your Account Path

A clear contact path helps you ask about the Privacy Policy without repeating your account story. When you contact us about personal data, include the account phone number or email used for access, the device involved and the subject of your request. For a DANA or QRIS record, add the payment reference rather than sending a full wallet password or one-time code. We use the details you provide to locate the relevant record, verify that the request comes from the account holder and explain the next step where local law permits.

Team online

Account data request

Ask us to explain the account details connected with your permata 4d access, such as the contact record, phone verification status and recent sign-in events. We may ask for an account step or matching detail before discussing personal data, so another person cannot obtain it.

Wallet record query

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference and approximate date through the account help path. We use that information to check the wallet record without asking you to disclose a wallet PIN, password or one-time verification code.

Cookie access help

Questions about cookies or device data can be raised from the same account support route. Tell us whether you used a mobile browser or desktop browser and what changed after clearing cookies, then we can separate a privacy request from a simple sign-in issue.

DATA HANDLING

What We Do With Policy Data

The Privacy Policy is practical because each data category has a defined use. Account fields support sign-in and phone verification; device signals help identify unusual access; payment references help reconcile wallet status…

Account security

We use sign-in events, device details and phone verification status to help identify unusual account access. If your browser changes or a new phone is used, an additional account check may be needed before we discuss personal data or wallet records.

Payment references

We keep the reference needed to connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account. Our Privacy Policy does not ask you to share a wallet PIN, card password or one-time code in a support message.

Cookie controls

Cookies can remember a session choice, support account navigation and help us understand whether a page loads correctly. You can manage cookies through your browser settings, although clearing necessary cookies may require another sign-in or phone verification step.

Retention periods

We retain each data category only for the period needed for account operation, payment matching, security checks, dispute handling or legal duties. When that purpose ends, records are deleted or changed so they no longer identify you where the applicable process allows.

Correction requests

If your contact detail or account record is inaccurate, contact us with the field that needs changing and the account step that confirms your connection to it. We check the request before editing the record and explain any limit imposed by local law.

Who to contact

Use the account help path for questions about this Privacy Policy, data access, cookie use or wallet references. Include only the minimum details needed to locate the issue, and never include your password, wallet PIN or one-time verification code.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the searches we receive most often from people checking permata 4d account access in Indonesia. They cover collection, cookies, wallet references, corrections, deletion questions and contact steps, so you can understand the data path before opening an account or returning from a mobile browser.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookie choices, support messages and payment references. It explains how we use these records for account access, security, wallet matching and legal duties, with eligibility depending on local law.

We may collect the details you enter for an account, contact and verification records, browser or device signals, cookie settings, support correspondence and references for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use DANA and QRIS references to match a payment event with the correct account and investigate a status question. We do not need your wallet PIN or one-time code in a support message, and we check account ownership before discussing a record.

Yes. Contact us through the account help path and identify the inaccurate field, such as a contact detail, together with the account step that confirms your connection. We verify the request first and explain any correction limit required by local law.

Cookies can keep a session choice, support account navigation and show whether a page loads correctly. You can manage them in your mobile or desktop browser. Removing necessary cookies may sign you out and require phone verification when you return.

Retention depends on the purpose of each record, including account operation, payment matching, security checks, dispute handling and legal duties. When the relevant period ends, we delete or anonymise the data where the applicable process permits.

Use the account help path and state whether your question concerns personal data, cookies, a DANA or QRIS reference, or deletion. Include the account contact detail and minimum locating information, but never send a password, wallet PIN or one-time code.