Reference

nabila77 Privacy Policy, Clearly Explained

nabila77 Privacy Policy shows what we collect when you open an account, verify your phone, use DANA or QRIS, and contact support.

Account dataWallet recordsDevice choicesContact rights
nabila77 nabila77 Privacy Policy, Clearly Explained
HELP WITH PRIVACY

Get Policy Help Beside Your Account

A direct support route makes the Privacy Policy easier to use when a question concerns your own account.

Account support path Open the account support path while signed in and select the privacy subject.
Wallet record question If your request concerns DANA, OVO, GoPay, QRIS, or a bank transfer, include the…
Access or correction Ask us to see, correct, or clarify personal data through the same account support…
DATA HANDLING DETAILS

How We Handle Your Privacy Choices

Privacy decisions work best when the process is specific. We separate account identity data from payment references where our operational systems allow, limit internal access to work needs…

Account data use

We use your name, contact details, phone verification result, and account activity to create and protect your account.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we keep the reference, amount status, and timing needed…

Cookies and devices

Cookies may remember a session choice, while device details such as browser type and operating system help us identify unusual…

Account security

Phone verification is an account step before access, and security records can include login time, device signals, and failed attempts.

Retention requests

We keep records for as long as needed for the stated service, security, dispute, and legal purposes described in the…

Changing your details

If your phone number, contact detail, or other account data is wrong, contact support from your signed-in account and name…

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the questions you are most likely to have before opening an account or sending a data request. We keep the wording practical: what we collect, why payment references appear, how device records work, and which account step helps us respond safely. If your situation is different, use the signed-in support path and describe the specific record.

It covers account details, phone verification, payment references, device and browser records, cookies, support messages, security events, retention, and requests to access or correct data. It also explains how these records are used for account operation, payment matching, security checks, and applicable legal needs.

DANA and QRIS activity creates a payment reference and status that we may need to match with your account. The Privacy Policy explains that we use this operational record to check a transaction, while your wallet password and banking sign-in details are not needed for that check.

Open the support path from your signed-in account and ask to access your personal data. Include the contact detail linked to the account and describe the records you want. We may ask for phone or account verification before sharing private information with you.

Yes, send a correction request through the signed-in support path and identify the field that is wrong. We compare the request with your account details before making a change. If a record must remain for security, dispute, or legal reasons, we explain that limit.

On a mobile browser, cookies can retain session choices and help recognise unusual access alongside device signals. You can adjust cookie settings in the browser path on your phone. Turning them off may affect sign-in continuity or saved policy preferences.

Retention depends on the purpose of the record, including account operation, security checks, payment reconciliation, disputes, and legal requirements. The Privacy Policy describes these purposes rather than promising one period for every record. You can ask support what applies to your account.

Yes. Access, correction, deletion, or other requests depend on local law and the type of record involved. Where local law permits, we follow your request after verifying account control. Contact support from the account linked to the data so we can assess it safely.