Reference

nona55 Privacy Policy for Your Account

Our nona55 Privacy Policy shows what we collect when you open an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Account recordsWallet activityCookie choicesPhone verification
nona55 nona55 Privacy Policy for Your Account
CONTACT PATHS

Where Privacy Questions Meet Account Support

A clear contact path matters when a wallet receipt or login record needs explanation. From your account support area, send the relevant reference, the email or phone linked to your account and the privacy question you want answered. We use those details to locate the correct record without asking you to share a wallet password. Requests about DANA, QRIS, device access or account corrections stay tied to the Privacy Policy process.

Team online

Account support

Open the support path from your account area and describe the record you want checked. Include a DANA, OVO, GoPay or QRIS reference when your request concerns wallet data.

Privacy request

Ask for access, correction or deletion through the same support route. We may confirm your phone or account details first so private records are not sent to the wrong person.

Receipt check

For a missing payment record, attach the receipt reference rather than wallet credentials. We compare it with the account entry and explain what the Privacy Policy allows us to change.

ACCOUNT CONTROLS

Privacy Controls From Login To Wallet

We handle this policy area through practical account controls rather than vague promises. Phone verification helps us connect requests to the right account, while session and device checks help identify unusual access.

Data handling

We use account, payment-reference and device details for the service action they support, such as phone verification, wallet matching, login protection or a reply to your privacy request.

Cookie choices

Cookies can remember session settings and page preferences on your phone or desktop browser. You can adjust cookie controls in the browser path, although some account pages may then need fresh login.

Account security

Keep your login details private and sign out on shared devices. If a session looks unfamiliar, contact account support with the affected device path so we can check the access record.

Record retention

We keep account and payment records only as long as needed for service delivery, dispute handling, legal duties and security checks. When a record is no longer needed, we remove or anonymise it.

Your requests

You can ask what personal data we hold, request a correction or ask about deletion. We verify the account connection before acting, then explain any record that must remain for legal or payment reasons.

Policy contact

Send privacy questions through the account support route and name the exact issue, such as cookies, phone verification or QRIS receipt data. We use the conversation to keep the response focused.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions we expect before you open an account. They cover the data connected to login, mobile browsing, payment references and requests for access or correction. If your situation involves eligibility or regional access, where local law permits is the wording that applies.

It covers account details, phone verification, login activity, device signals, cookies, payment references and support requests. It also explains why we use those records and how you can ask about them.

We may collect contact and account details, verification results, session data, browser or device signals, cookie choices and payment references. We do not need your DANA, OVO, GoPay or QRIS password.

Wallet and QRIS references help us match a deposit or withdrawal request with the correct account. We record the transaction reference and status, not the private password used inside your wallet.

Cookies and similar browser records can keep a session active and remember selected settings. You can change them in your mobile browser, but turning them off may require you to log in again.

Use the account support path and state whether you want access, correction or deletion. Include the phone or email linked to the account; we verify that connection before discussing private records.

We use phone verification, session details and device signals to connect activity with the right account and identify unusual access. Never send login or wallet passwords in a support message.

Retention depends on the record and its purpose. We keep details for account service, payment matching, disputes, security checks or legal duties, then remove or anonymise them when they are no longer needed.