Reference

furla Privacy Policy For Your Account

The furla Privacy Policy explains what we collect when you open an account, sign in from your phone, use DANA or QRIS, and contact our support path.

Account clarityWallet recordsCookie choicesSecurity requests
furla furla Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help Beside Account Support

A clear contact route matters when you need a Privacy Policy answer rather than a wallet status update.

Account access If you cannot sign in, tell us the account step that stopped working and the device path you used. We can separate a login issue from a Privacy Policy request without asking you to send a wallet password or full payment credential.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, share the relevant receipt reference rather than sensitive wallet credentials. Our support path can explain which account record is connected to the request and what privacy detail we can discuss after verification.
Data requests Ask us to access, correct, or discuss eligible deletion of your personal data through the same account support route. State the request clearly, and keep your contact details current so we can send a response to the right account holder.
DATA HANDLING

What We Protect On furla

Privacy work reaches beyond the form you complete at account opening. We connect account records with sign-in activity, device signals, cookie settings, support history, and payment references so we can protect access…

Account details

We may collect the details you provide during account creation, including contact information and verification results. A clear phone verification step helps connect account access with the person making the request, while reducing the chance that a stranger receives private account details.

Device activity

When you sign in from a mobile browser or desktop, we may record technical session signals such as device type, browser details, and access time. These signals help us identify unusual login behaviour and troubleshoot a failed path without reading unrelated content on your device.

Cookies

Cookies can remember session choices, keep the account path working, and help us understand which policy page brought you to a request. Your browser settings can restrict cookies, though some account functions may then require another sign-in or may not work as intended.

Wallet references

We handle payment references needed to match account activity with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account status. We do not need your wallet password for a support request, and you should never place a full password in a message.

Retention choices

We retain personal data according to the purpose for which it was collected and any account, dispute, security, or legal need that remains. A deletion request may not remove records that must be kept for those reasons; support can explain the applicable outcome.

Change requests

You can ask us to correct inaccurate account details or discuss access to the data connected with your account. Send the request through support, identify the account step involved, and complete verification so we can apply the right change without exposing another person’s record.

Privacy Policy Answers For furla

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening or using furla in Indonesia. We explain the practical path for data access, corrections, cookies, security, and payment references. If your situation is different, contact support with the account detail that needs attention. Any access or eligibility question depends on local law.

The furla Privacy Policy covers data connected with account creation, phone verification, sign-in activity, device sessions, cookies, support messages, and payment references. It explains why we use those details, how we retain them, and how you can request access or correction.

We may collect contact and verification details you provide, along with sign-in time, device or browser signals, cookie settings, support history, and references for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. We do not ask for wallet passwords in support messages.

Send a data request through the furla account support path and identify the email or phone connected with your account. We may verify your identity before sharing personal details. Mention whether you want access, a correction, or an explanation of a particular record.

Yes, you can ask us to correct inaccurate account details or discuss eligible deletion. Use support, describe the record, and complete account verification. Some data may remain when needed for security, dispute handling, account operation, or legal duties that apply.

Yes. The Privacy Policy covers payment references used to match account activity with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. We use the reference needed for status checks and support, not your wallet password or unrelated wallet content.

Cookies can keep your session active, remember selected settings, and help us understand how you reached a policy request. You can restrict cookies through your browser, but account access may then require another sign-in or certain session functions may not work.

We use phone verification, session signals, and account checks to connect requests with the correct account holder and identify unusual sign-in activity. Do not send passwords or complete wallet credentials to support. Account access and eligibility depend on local law.