Reference

paket4d Privacy Policy For Your Account

Our Privacy Policy shows what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account data explainedWallet records clarifiedRequests welcomed
paket4d paket4d Privacy Policy For Your Account
HELP WITH REQUESTS

Get Privacy Help Near Your Account

You can contact our support chat when a Privacy Policy question concerns your account, wallet record or device access. Include the phone number or account identifier connected to your request, but never send a wallet password or one-time code. We use the existing cashier help path for receipt and status questions, then route privacy matters to the appropriate internal contact.

Team online

Account privacy chat

Ask our support chat about the data linked to your account, phone verification or sign-in record. We may request account details to confirm that the request comes from you.

Wallet record help

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the receipt reference and date. We can explain the stored status without asking for your wallet password.

Correction requests

If your account details are inaccurate, tell us which field needs changing and why. We check the account path first, then confirm the result through the contact method on file.

YOUR DATA PATH

What We Do With Account Records

We keep the Privacy Policy practical by separating account access, payment references, cookies and support records. Your data is handled for a stated purpose rather than copied into unrelated areas.

Account details

We use your account name, contact details and phone verification status to provide sign-in access, confirm requests and reduce confusion when you contact us about your account.

Payment references

DANA, OVO, GoPay and QRIS records may include an amount, reference, time and status. Bank transfer and virtual account records serve the same matching purpose.

Cookies and sessions

Necessary cookies help maintain sign-in and language settings. Session signals from your mobile browser or desktop help us identify an interrupted or unusual access attempt.

Account security

Before we change sensitive account details, we may compare your request with the contact method and phone verification connected to the account. Never share a one-time code in chat.

Retention periods

We retain records only for operational, dispute, security or legal needs described in the Privacy Policy. When a period ends, records are deleted, anonymised or securely restricted.

Data changes

You may ask us to access, correct or delete eligible personal data. Send the request through support chat with enough detail for us to locate the correct account.

Privacy Policy Answers For paket4d

These Privacy Policy answers address the account and payment questions you may have before opening access. Each answer points you toward a practical request path, from checking stored data to asking about cookies or a QRIS receipt.

It covers account details, phone verification, sign-in sessions, cookies, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps connect an account request to the correct contact path and protects sensitive changes. We may use its status when confirming access, correcting details or handling a privacy request.

No. We use transaction references, status results and receipts to match wallet activity. Your DANA, OVO, GoPay or QRIS password and one-time code should not be sent to our support chat.

When you use a mobile browser or desktop, we may receive browser, device, session and security signals. These help maintain access, remember necessary settings and identify unusual sign-in behaviour.

Contact our support chat and state that you are making a Privacy Policy data request. Include your account identifier and the records you want to access, while keeping passwords and codes private.

Yes, you can request a correction for eligible details. Tell us the incorrect field and the accurate replacement; we first check the account contact path before confirming any change.

Retention depends on the record and its operational, dispute, security or legal purpose. The Privacy Policy explains when records may be deleted, anonymised or restricted after that purpose ends.