Reference

help99 Privacy Policy for Your Account

Clear account records, wallet details and device choices are covered in the help99 Privacy Policy, so you can understand what we collect before opening an account.

Account clarityWallet dataCookie choicesMobile security
help99 help99 Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact route matters when you want to ask about the Privacy Policy or a detail connected with your account.

Policy questions Use the support link inside your account to ask how the Privacy Policy applies…
Wallet records For a DANA, OVO, GoPay or QRIS record, include the visible reference and date…
Access requests If you want a copy, correction or deletion assessment, state the request clearly through…
DATA PRACTICES

How We Handle Privacy Details

The practical side of privacy is visible in the steps around your account. We separate sign-in and phone verification from payment references, limit internal access to records needed for support or security…

Account records

We collect details needed to create and maintain your account, such as your phone number, verification result and selected account settings. Activity connected with the lobby or support path can be associated with that account so we can protect access and answer a record-specific request.

Payment references

A payment reference can show that a DANA, OVO, GoPay, QRIS, bank transfer or virtual account step was submitted. We use that reference to match status, investigate a discrepancy and protect the account, without requesting your wallet password.

Device signals

When you move from phone login to the lobby, we may process device and browser signals used to keep sessions safe and detect unusual access. These signals help us assess an account event; they are not a substitute for your phone verification.

Cookies

Cookies can retain session choices, support essential sign-in functions and help us understand basic page performance. Browser controls let you remove or restrict them, but turning off required cookies may prevent the account path from working as intended.

Retention and removal

We keep personal details only for the period needed for account operation, security checks, payment matching or a legal requirement. A deletion request does not always erase records that must remain for those purposes; we explain the reason in our reply.

Policy requests

To request access, correction or a privacy clarification, contact us through the signed-in support route with a short description. We verify account ownership, review the relevant record and tell you what can be changed under the current Privacy Policy.

Privacy Policy Answers for help99

These Privacy Policy answers address the questions we expect before you open an account or connect a local wallet. We keep the wording practical: what we collect, why payment references appear, how cookies affect a mobile session and where to send a request. Account access remains subject to local law and the current policy wording shown on this page.

The help99 Privacy Policy covers account details, phone verification, device signals, cookies, lobby and support activity, payment references, retention and security handling. It also explains how you can request access, correction or deletion assessment through the signed-in support route.

We use your phone number to create and protect the account and to complete the clear verification step before account access. The number can help us connect a support request to the correct record, while the Privacy Policy explains its handling and retention.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those references to match payment status, investigate discrepancies and protect the account, not to request your wallet password.

You can send an access request through the support link inside your signed-in account. We first confirm account ownership, then identify the records available for disclosure. Some details may remain restricted or retained when security, payment matching or legal requirements apply.

Cookies can keep a session active, remember technical choices and help us measure basic page operation on your phone or desktop. You can restrict them in your browser, but required cookies may be needed for login, phone verification and the lobby path.

Use the signed-in support route and describe the detail that needs correction, such as a contact record or account setting. We check that you control the account, compare the request with the relevant record and confirm the outcome under the Privacy Policy.

We assess deletion requests against account operation, security checks, payment matching and legal retention needs. Where removal is possible, we follow the request after account verification. Where a record must remain, we explain the reason and the applicable Privacy Policy position.