Reference

fin4d Privacy Policy For Your Account

fin4d Privacy Policy gives you a clear view of the account, device and wallet details we use when you move from login to the lobby.

Account dataWallet statusCookie choicesAccess requests

Browse Our Lobby Read FAQ

How Policy Covers QRIS And Accounts

fin4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy explains the details collected when you open an account, complete phone verification, sign in from a mobile browser, or ask support about a wallet status. This can include contact details, login records, device signals, security events and payment references connected with DANA, OVO,

1
GoPay, QRIS, bank transfer or a virtual account. We use these details to identify your account, check unusual access, match a payment status and respond to a request. We do not use a game name such as Sic Bo or Aviator as a reason to collect
2
unrelated details. You can ask what we hold, request a correction or ask about deletion, subject to records we must retain. Account access depends on local law, and we apply this policy to Indonesia requests where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH DATA

Three Ways To Ask About Privacy

A direct support path keeps privacy questions separate from ordinary lobby browsing.

DATA PRACTICE

Six Practical Privacy Controls

We keep the Privacy Policy practical by connecting each data use to an account action you recognise.

What we collect

We may handle your contact details, phone verification result, sign-in timestamps, device signals, support messages and payment references needed to operate your account path.

Cookie choices

Cookies can remember session settings and help keep you signed in on a mobile browser. You can manage browser cookie controls, though some account functions may then need another sign-in.

Account security

We use phone verification, sign-in records and device checks to identify unusual account access. Never share your password or one-time code in a support message.

Retention period

We keep records for as long as needed for the stated account, security, payment-status or support purpose, then handle removal according to applicable local requirements.

Change a detail

If your phone number, contact detail or account record is inaccurate, ask support for a correction and identify the affected account step without sending secret credentials.

Who to contact

Our support route beside the cashier path is the starting point for privacy requests. Include your account identifier and request type so we can direct the question correctly.

Privacy Policy Answers For fin4d

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover payment references, cookies, device access, corrections and contact steps, so you can decide what to share before using the account path. Where eligibility or access is relevant, it depends on local law.

It covers account details, phone verification, device signals, cookies, support messages, security events and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use the verification result to connect account access with the correct phone step and help identify unusual sign-ins. It does not mean you should send a one-time code to support.

Yes. The policy covers payment references and status details linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity needed for account support.

Use the support route beside the cashier path and ask for an account data request. Include your account identifier and the record type, but leave out your password and one-time code.

Yes. Send a correction request through support, identify the inaccurate phone or contact detail, and explain the account step involved. We may need to verify that you control the account.

Cookies can retain session choices and page settings when you use a mobile browser. Browser controls can remove or block them, although sign-in may need to be completed again.

Contact support from your account path and describe the unfamiliar device event, approximate sign-in time and affected account step. We can then direct the security request without asking for secret credentials.

fin4d Privacy Policy For Your Account

Three Ways To Ask About Privacy

Six Practical Privacy Controls

What we collect

Cookie choices

Account security

Retention period

Change a detail

Who to contact

Privacy Policy Answers For fin4d

01 What does the fin4d Privacy Policy cover?

02 Why does fin4d need my phone verification result?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request my fin4d account data?

05 Can I ask fin4d to correct my personal details?

06 How does the Privacy Policy handle cookies on mobile?

07 Where can I report an unfamiliar device sign-in?

Related Pages