Reference

Open loyal4d Privacy Policy clearly

DANA, OVO, GoPay and QRIS records are explained here alongside the account details we use to give you access to loyal4d.

Clear data purposesWallet record contextAccount request pathIndonesia access wording
loyal4d Open loyal4d Privacy Policy clearly
REQUEST HELP

Switch to the right privacy contact

A clear contact route helps when your account record, wallet reference or policy request needs attention.

Account access path If a login or phone verification record looks wrong, tell us the account step and device context. We can direct the request toward access data without asking you to resend unrelated wallet details.
Wallet record path For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, identify the payment rail and reference status. We use that detail to separate a privacy request from a payment-status question.
Policy request path For a copy, correction or removal request, state the Privacy Policy action you want and the account contact used during registration. We will explain the next verification step where local law permits.
DATA CONTROLS

Browse loyal4d security and retention steps

We handle privacy through practical account controls rather than vague promises. Login checks, phone verification and device session signals help us protect access, while retention is tied to the purpose of the…

Account details

We use the contact and verification details you provide to create your account, confirm requested access and respond to a privacy request. Please keep those details current so an account correction can be checked.

Device sessions

When you move from login to the mobile lobby, we may record device and session signals linked to security checks. These signals help us identify unusual access without treating your device as permanent identity proof.

Cookies

Cookies and similar session tools can remember the path between account access and the lobby. Your browser controls may restrict them, although some account steps may then require another verification check.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be retained with its account status so payment reconciliation is possible. We use the reference for that purpose rather than requesting your wallet password.

Retention period

We retain records for the purpose collected, account security needs and legal requirements where local law permits. When a record is no longer needed for those reasons, our handling follows the applicable deletion process.

Change requests

You can ask us to correct account data, request access to relevant records or ask how a detail is used. Include your registered contact and requested action; verification protects your account from false changes.

Check loyal4d Privacy Policy answers

These common Privacy Policy questions cover the account and payment records you are most likely to ask about before registration. Each answer stays focused on data handling, access and contact steps, including the device path from phone verification to the mobile lobby.

It covers account details, phone verification, device sessions, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use phone verification to confirm an account access request and help protect the login path. The record may also help us verify a correction or data-access request where local law permits.

Yes. The policy explains that QRIS, DANA, OVO and GoPay references may be retained with account status for payment reconciliation, without requesting your wallet password.

Use our policy request path and identify the registered contact plus the records you want to access. We may ask for an account verification step before responding to protect your details.

Yes. Tell us which account detail is inaccurate and provide the registered contact used during account creation. We will explain the verification and correction steps available where local law permits.

Retention depends on the purpose of the record, account security needs and applicable legal requirements. Payment references, access events and verification records may therefore follow different retention periods.

Yes. It applies when you access the account and mobile lobby through a supported browser. Device and session signals may be used for security, while cookies can be managed through browser settings.