Reference

parada4d Privacy Policy for Your Account Data

The parada4d Privacy Policy shows what we collect when you open an account, use DANA or QRIS, and move between your phone and desktop.

Clear data purposesWallet record contextAccount access rightsCookie choices
parada4d parada4d Privacy Policy for Your Account Data
CONTACT DATA CARE

Contact Us About Your Policy Data

A clear request helps us find the correct account record without asking you to send unnecessary personal details. Use the support route available through your parada4d account when you need a privacy answer, a receipt check, or help correcting your phone verification record.

Team online

Privacy request

Tell us whether you want access, correction, deletion, or a copy of your account data. Include your registered phone number only through the account support route so we can match the request safely.

Wallet record check

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, provide the transaction reference and date. We use those details to locate the relevant record without requesting your wallet password.

Login assistance

If phone verification or sign-in stalls, contact us from the device path you used, such as mobile browser or desktop browser. We may ask account questions before discussing private records.

DATA HANDLING

Browse How parada4d Handles Account Data

Privacy work is part of each account step, from the first phone check to a later request about a QRIS receipt.

Account collection

When you open an account, we receive the details needed to create it and confirm phone access. Sign-in events help us identify the account involved when you ask for a correction or data copy.

Payment references

DANA, OVO, GoPay, and QRIS may return transaction references and status details. Bank transfer and virtual account records can be matched by reference, date, and amount rather than by your wallet password.

Cookie controls

Cookies can keep a session active and help us understand whether a page loads correctly. You can manage browser cookie settings on your phone or desktop, though some account steps may then need repeating.

Account security

We use phone verification and sign-in checks to reduce mistaken access to private records. Never share a verification code; if your device changes, start with the normal account access path.

Retention reasons

We retain selected account, security, and transaction records for as long as needed for the stated purpose or a legal requirement. A deletion request may not remove records that must remain available.

Change requests

Ask us to correct inaccurate account details, confirm stored data, or explain a retention decision through support. We verify your account before making changes that could affect private records.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers cover the searches we hear before account creation and during wallet activity. If your question concerns a particular phone record, device path, or transaction reference, send the request through account support so we can respond to the right record.

It covers data collected during account opening, phone verification, sign-in, lobby access, support requests, cookies, and wallet activity involving DANA, OVO, GoPay, QRIS, bank transfer, or virtual account.

We use your phone number to create and identify your account and to complete phone verification before access. It also helps us locate the right record when you request a correction or data copy.

Yes. The Privacy Policy explains that QRIS, DANA, OVO, and GoPay may provide transaction references, status, date, and amount. We do not ask for or store your wallet password.

Use the account support route and state that you want confirmation or a copy of your data. Include only the requested account identifier, then complete our ownership check before records are shared.

Yes. Send a correction request through support and identify the inaccurate field, such as a phone detail. We verify account ownership first, then update the record when the request is valid.

Retention depends on the type of record and its stated purpose. Account, security, or transaction records may remain when needed for legal or dispute handling, even after a deletion request.

Browser cookie settings can affect session continuity on a phone or desktop. You can change those settings, but sign-in or phone verification may need to be repeated during the next account visit.