Reference

Privacy Policy for paludewa Accounts

paludewa Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and contact us about access.

Account dataWallet recordsCookie choicesSecurity requests
paludewa Privacy Policy for paludewa Accounts
HELP WITH REQUESTS

Get Clear Answers About Your Privacy

A clear contact route helps you act on the Privacy Policy instead of guessing what to do next.

Account access If you cannot sign in or complete phone verification, use the account support route. We first confirm the account details needed to discuss your request, then explain which Privacy Policy step applies before changing access records.
Wallet status For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, send the transaction date and visible status. We use that narrow payment context to locate the record without asking you to disclose a wallet password.
Data changes Ask through the account support path when your phone number, contact detail or stored profile entry needs correction. We may verify ownership first, then confirm what changed and whether a security or legal record must remain.
HANDLING YOUR DETAILS

What We Do With Account Information

Privacy Policy choices are easier to understand when each data use has a practical reason. We separate sign-in details from payment references where possible, limit internal access to the work being completed…

Account security

Phone verification comes before account access so we can connect a sign-in request with the right account. Session and device signals help us identify unusual access, including a change from mobile to desktop, without treating the device itself as your identity.

Payment references

A DANA, OVO, GoPay or QRIS record normally contains a reference, amount status and account connection rather than your wallet password. Bank transfer and virtual account records follow the same purpose: matching a request and checking its status.

Cookies

Cookies may keep your sign-in journey working and help us understand which Privacy Policy pages are opened. You can adjust cookie controls in your browser, although restricting necessary cookies may interrupt account access or page settings.

Retention

We keep account, support and payment references for the time needed to protect access, resolve a dispute, answer a request, or meet an applicable duty. When a record no longer serves one of those purposes, our process removes or de-identifies it where practical.

Your request

You can ask for access to personal data, correction of an inaccurate entry, or clarification of a processing purpose through the account support route. Please identify the account and request clearly; we verify ownership before releasing private details.

Policy questions

If a Privacy Policy paragraph is unclear, contact us with the exact topic, such as cookies, device signals, phone verification or QRIS status. We will explain the relevant handling step and note any limit that depends on local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions we expect you to ask before using paludewa. They cover access, wallet references, cookies, device behaviour, retention and requests. For a case involving your own record, use the account support path and provide only the details needed to identify the issue. Eligibility and any legal restriction depends on local law.

The paludewa Privacy Policy covers information connected with your account journey, including phone verification, sign-in activity, device signals, support messages, cookies and payment references. It explains why we use each category, how we protect access, how long records may remain, and how you can make a request.

Our Privacy Policy does not require your DANA or QRIS wallet password for a payment status check. We may store a reference, status and account connection so we can match the request. Keep wallet credentials private and contact the wallet provider if you suspect those credentials were exposed.

Phone verification links an access attempt to the account you created and helps reduce mistaken or unusual sign-ins. We may use related session and device signals to protect the account. If verification stalls, use the account support route rather than sending a password or complete wallet credentials.

Yes, you can ask what personal data is connected with your account through the support path. Include the account phone number and describe the records you want, such as profile entries or payment references. We verify ownership first, and the response depends on local law and required security records.

Send a correction request through account support and identify the inaccurate field, such as a phone number or contact detail. We may request an account check before editing it. If the entry is part of a payment, security or dispute record, we explain why the original record may need to remain.

Cookies can keep a sign-in session working, remember a page setting and help us measure use of Privacy Policy pages. Your browser can restrict or remove them. Blocking necessary cookies may interrupt account access, so check the browser result before submitting a support request.

We retain payment references for the period needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, protect account security, resolve disputes and meet applicable duties. Retention is not a promise of a fixed period; it depends on the record and local legal requirements.