Reference

Privacy Policy for Your palu4 Account

Our Privacy Policy explains what we collect when you open a palu4 account, use the lobby, or check a wallet status through DANA, OVO, GoPay or QRIS.

Account detailsWallet statusDevice sessionsPolicy requests
palu4 Privacy Policy for Your palu4 Account
CONTACT ROUTES

Get Help With Policy Requests

A clear contact path helps when you want to ask about a Privacy Policy point, correct account data or understand a wallet record.

Data questions Ask which account, login or device details are held for your palu4 profile.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the payment…
Access support If phone verification or a login session stalls, contact support through the account route…
HANDLING DETAILS

How We Manage Account Information

We apply this Privacy Policy to practical account operations rather than collecting details without a purpose.

Collection purpose

We collect contact and verification details to create and protect your account, while login and device signals help us assess…

Cookies and sessions

Browser storage can support sign-in continuity, security checks and selected account settings.

Account security

Phone verification is part of account access, and session records help us investigate a sign-in that does not match your…

Payment matching

A payment reference, rail name and status may be attached to your account record when you use OVO, GoPay, a…

Retention choices

We keep information only while it serves an account, security, payment or legal purpose.

Your requests

You can ask what data is associated with your account, request a correction, ask about processing, or raise an objection…

Privacy Policy Answers for palu4

These Privacy Policy answers address the account and access questions that arise before you open the palu4 lobby. They explain the information connected with phone verification, device sessions, local wallet activity and support requests. Where a request involves eligibility or access, the outcome depends on local law, and we may need to confirm your account before sharing personal details.

It covers account details, phone verification, login events, device signals, support messages and payment references connected with your palu4 activity. It also explains cookies, retention, account-security handling and the routes available when you want to ask about or change your information.

Phone verification helps us establish account access and reduce the chance that someone else enters your profile. A verification record may be retained for security and account administration. We will not ask you to place a wallet PIN or password in a support message.

Yes. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain the rail, reference and status needed to match activity with your account. We do not need your wallet password to investigate a receipt or pending status.

You can send a correction request through the support route near your account area. Include the account identifier and describe the field that appears wrong. We may verify your phone or another account detail first, because a data change must not expose your profile to another person.

Retention depends on why the information was collected. Account, security, payment and support records may remain while they are needed for administration, dispute handling or legal duties where local law permits. We review whether continued storage is needed after those purposes end.

Use the policy contact route linked from your account and ask for a data-access request. Tell us which account and period you mean, such as a QRIS receipt or device session. We will confirm ownership before explaining or supplying information connected with you.

Yes. The policy applies when you sign in from a mobile browser or another supported device path. Session and device signals may be used for security, while browser cookie controls remain available to you. Account eligibility and access depend on local law.