Reference

Open fun77 Privacy Policy With Clarity

fun77 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check DANA and QRIS status.

Account dataWallet referencesCookie choicesSupport requests
fun77 Open fun77 Privacy Policy With Clarity
ASK ABOUT PRIVACY

Contact Support About Your Data

A clear support path helps when a privacy question sits beside a login or wallet-status issue.

Account request Use the account support path for a Privacy Policy question, then state the email…
Wallet reference If your question involves DANA, OVO, GoPay or QRIS records, include the transaction reference…
Correction request For a spelling change, outdated phone detail or other account-data correction, describe the exact…
DATA HANDLING

Explore Six Privacy Controls For Accounts

Privacy depends on practical handling rather than a general promise. We separate account access from payment references, limit support visibility to the request being handled and use session controls when a device…

Data collected

When you open an account, we may collect contact details, verification results, sign-in events and records you submit to support. We use these categories for account access, security checks and request handling, rather than asking for unrelated personal details.

Cookie settings

Cookies can remember a session, language setting or security preference on the device you use. You can manage browser cookie controls, although removing necessary cookies may require you to sign in again before reaching account pages.

Account security

We use sign-in checks and device session signals to reduce unauthorised account access. Keep your password and verification codes private, and contact support promptly if a session, phone detail or account action does not look familiar.

Payment references

A DANA, OVO, GoPay or QRIS record may be linked to an account request through a reference, amount status or time. We do not need your wallet PIN for support, and you should never place that secret in a message.

Retention period

We retain account and support records for as long as needed for their stated purpose, security checks, dispute handling or legal duties. When a record no longer has a valid need, our handling follows the applicable deletion or anonymisation process.

Change request

You can ask us to access, correct or remove personal data through the account support route. We may verify your identity and explain any record that must remain for security, transaction handling or a legal requirement.

Ask About fun77 Privacy Policy

These Privacy Policy answers cover the account questions we expect before sign-in: what data is collected, how cookies work, how wallet references are handled and how you can request a change. If your situation is specific, send the account support request with only the details needed to locate the record.

It covers personal data used for account creation, sign-in, verification, support requests, cookies and payment references. It also explains security handling, retention and requests to access, correct or remove data connected with your fun77 account.

We may collect contact details, account credentials, verification results, device session signals and messages you send to support. If you use DANA, OVO, GoPay or QRIS, a transaction reference or status may also be connected with your account.

We use payment references, status and related account details to identify a request or investigate a transaction issue. We do not ask for your wallet PIN or authentication code, and you should keep those secrets out of support messages.

Yes. Send a correction request through the account support path and name the field that needs changing. We may confirm account ownership first, then update the record where appropriate or explain why a security or legal record must remain.

Necessary cookies can keep a sign-in session and remember security or language settings. Browser controls let you manage cookies, but removing required cookies may sign you out or prevent an account page from working until settings are restored.

Retention depends on the purpose of the record, account security needs, transaction handling, dispute resolution and applicable legal duties. When a record no longer has a valid purpose, we follow the relevant deletion or anonymisation process.

Use the account support route and describe whether you want access, correction or deletion. Include a safe account reference, not a password or wallet code. We may verify ownership before responding, and handling depends on local law.