Reference

permata4d rtp Privacy Policy

Our Privacy Policy explains how permata4d rtp handles the details you provide when opening an account, checking wallet status or entering the lobby.

Account dataWallet referencesCookie choicesPolicy requests
permata4drtp.club page image
CONTACT FOR DATA

Where To Ask About Privacy Policy

A clear contact path matters when a name, phone number or wallet reference needs checking. Use our site support route and include the account step involved, such as phone verification, a DANA receipt or a QRIS status query. We will use the details in your request to locate the relevant record and explain the next privacy step.

Team online

Account data request

Ask us to confirm the account data connected with your phone verification step. Include your account identifier, but never send a password or wallet PIN through the support route.

Payment record check

For a DANA, OVO, GoPay or QRIS query, attach the transaction reference and date. We use that reference to locate payment data without asking for private wallet credentials.

Privacy correction

Tell us which account detail appears wrong and what should change. We may request an account check before editing records, helping prevent another person from changing your data.

DATA HANDLING

Privacy Controls Inside Your Account

We treat the Privacy Policy as an operating process rather than a page you read once. Account access, payment matching and support replies each create a different data trail, so our handling…

Account security

We use phone verification before account access and may compare session details when a login comes from a new browser or device. This helps us spot unusual access without requesting your wallet PIN.

Cookies and sessions

Cookies can keep your session active, remember security progress and record basic preferences. You can manage browser cookie controls, although blocking them may interrupt the account path.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to reconcile status. We do not need your wallet password to investigate a receipt or cashier reference.

Device details

Our site may process browser version, device type, IP address and language setting for session protection and technical diagnosis. These details can help explain why a mobile login behaves differently.

Retention approach

We retain account, payment and support records for the operational, security or dispute purpose that requires them. When that purpose ends, we remove, aggregate or restrict the record where practical.

Your request route

You can ask what personal data we hold, request a correction or ask about removal through site support. We may verify account ownership before acting on a privacy request.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, wallet and device questions you may have before opening access. If your situation is not covered, send a focused request through site support with the relevant account step or payment reference.

It covers account details, phone verification, device and browser data, cookies, support requests, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and protect the account, including a verification step before access. It can also help support locate the correct record when you request a data change.

Yes. The Privacy Policy explains that we may retain a QRIS, DANA, OVO or GoPay reference and status so we can match a receipt, investigate a query and update the account record.

You can contact site support to ask what account data we hold or to request a correction. Include the affected account step, and we may verify ownership before replying or editing.

Cookies can preserve a login session and remember a completed security step. If your browser blocks them, the account path may ask you to verify again or may not continue correctly.

We keep records while they serve an account, security, payment matching or dispute purpose. After that need ends, we remove, reduce or restrict the data where practical and permitted.

Yes. Access or eligibility depends on local law. If you request data about an account used from Jakarta or another location, we may apply the rules relevant to that request.