Reference

viral365 Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your viral365 account, including phone verification, login activity and wallet records.

Clear data purposesWallet record controlsPhone verification contextIndonesia access terms
viral365 viral365 Privacy Policy for Your Account
PRIVACY HELP PATH

Get Help With Data And Account Access

A privacy question should not leave you guessing which account step to take.

Account data request Ask us to confirm which personal details are linked with your account, such as…
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the relevant transaction…
Access concern When login or account access stalls, contact us through the support route shown after…
DATA CONTROL DETAILS

What We Do With Your Personal Data

Our approach is practical: collect the details needed for account operation, use them for a stated purpose and limit access to people handling account, payment or security work.

Account details

We use your submitted account details to create access, send account messages and complete phone verification. Keeping your phone number current helps us connect a privacy request to the right account and reduces confusion when you return from a different mobile browser.

Payment references

A wallet or bank record can contain a reference, amount, status and time rather than your wallet password. We use these details to match DANA, QRIS, bank transfer or virtual account activity with the account step you initiated.

Cookies

Cookies can preserve a necessary login session, remember selected site settings and help us understand whether a page request completed. You can manage cookie permissions in your browser, although turning off necessary cookies may affect account access.

Device security

We may record device type, browser details, approximate connection data and sign-in time to identify unusual account behaviour. These records support account protection and privacy checks; they are not a request for your device passcode or wallet credentials.

Retention

We keep personal and transaction records only for the period needed for the stated service, security review, dispute handling or legal requirement. When a record is no longer needed for those purposes, our handling follows the retention process connected with that record type.

Changes and contact

You can ask us to correct an inaccurate name, phone detail or contact record through the support path inside your account. Include the requested change and a safe way to reach you; we may verify account ownership before making an update.

Privacy Policy Answers For viral365

These Privacy Policy answers cover the requests we expect you to make before opening or using an account. They explain the practical link between personal data, payment references, device sessions and support. If your question concerns a specific record, use the account support path and identify the account step involved. For access or eligibility, the applicable position depends on local law.

It covers personal details used for account access, phone verification, support, payment references, cookies, device sessions, security checks and retention. It also explains how you can ask for access to your records, request a correction or contact us about the way a detail is handled.

We use your phone number to create and verify account access, connect support requests to the correct record and help protect a session. Keep it accurate so a privacy request can be checked against your account without exposing details to another person.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. We use those records to check an account request or payment status, not to request your wallet password.

Yes. Send a correction request through the support path shown in your account and state which detail is inaccurate, such as a phone or contact record. We may ask for an account check first, then update the record when the request is confirmed.

Necessary cookies can keep a session active and remember site settings, while other cookies may support page measurement. You can change permissions in your browser. If necessary cookies are blocked, login or the return from a payment step may not work as expected.

Retention depends on why the record was collected. We keep details for the account service, security checks, payment queries, dispute handling or a legal requirement for the period needed for that purpose. You can ask support how a particular record is handled.

Use the support channel displayed inside your account and identify your request as a Privacy Policy matter. Explain whether you want access, correction or clarification. Do not send wallet passwords, one-time codes or unnecessary payment credentials in the message.