Reference

2svip Privacy Policy for Your Account

The 2svip Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and payment status.

Clear data purposesWallet record controlsRequest access by support
2svip 2svip Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Through Your Account Path

A direct support route helps you ask what data we hold, why we use it or how to correct an account detail.

Account privacy request Ask us to confirm the personal data connected with your account, explain its purpose or correct a phone detail. We may request account verification before replying, so one person cannot obtain another person's records through a simple support message.
Wallet record question For DANA, OVO, GoPay or QRIS records, send the transaction reference and date through the private support route. We use those details to locate the relevant status while avoiding unnecessary card, bank or wallet credentials in the conversation.
Access and deletion contact You can ask whether an access, correction or deletion request applies to your account. We explain any retention reason before acting, including unresolved account records or legal duties, and we respond through the contact details already verified with us.
HANDLING DETAILS

How 2svip Handles Privacy Requests

Privacy protection is part of the account path from phone verification through wallet reconciliation.

Account details

We may collect your phone number, account identifiers, login events and verification results to open access, detect unusual activity and answer account questions. We use the minimum detail needed for that purpose and do not ask you to disclose a password in support.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a wallet event with your account. We can inspect status and receipt timing without requiring your wallet PIN, one-time code or full banking credentials.

Cookies and devices

Cookies and similar device signals can keep a session working, remember a selected setting and help identify repeated login failures. Clearing browser data may sign you out or remove preferences, but it does not itself erase account records held for valid purposes.

Security checks

We review login patterns, phone verification and account changes to reduce unauthorised access. If a check pauses an account action, support may ask for a confirmation through the verified contact path rather than accepting sensitive details in an open message.

Retention timing

We keep account and payment records for as long as needed to operate the service, resolve a dispute, investigate misuse or meet a legal requirement. When a record no longer serves one of those purposes, our handling process removes or de-identifies it.

Request changes

To request access, correction or deletion, contact support from the route displayed on our site and describe the request clearly. We verify your identity, explain any lawful reason to retain a record and send the response to your confirmed account contact.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and payment questions you may have before opening an account. We keep each response tied to the way 2svip handles phone verification, cookies, wallet references, device sessions and support requests. Where a legal rule affects access or retention, depends on local law remains the governing condition.

The 2svip Privacy Policy covers account details, phone verification, login events, cookies, device signals and payment references. It explains why we use those details for access, security, support, wallet matching and legal duties, including records connected with DANA, OVO, GoPay and QRIS.

We may collect your phone number, account identifier, verification result, login activity, device session details and transaction references. We do not need your wallet PIN, one-time code or full banking credentials to check a DANA, QRIS, bank transfer or virtual account status.

Contact us through the support route shown on the site and ask for an account data access request. Include your verified phone number or account identifier, not a password. We may verify your identity before confirming which records are connected with your account.

Yes, you can ask us to correct an inaccurate phone or account detail through the verified support path. Tell us what appears wrong and provide the replacement detail when requested. We check the request before changing records that affect account access or wallet matching.

Cookies can maintain your session, remember a setting and help us understand repeated login failures on the device you use. Browser controls may clear or block them, although that can sign you out. Cookie handling does not automatically delete account records kept for valid purposes.

We retain records for the period needed to operate the account, resolve disputes, investigate misuse or meet a legal duty. After that need ends, our process removes or de-identifies the record. A deletion request may therefore have limits where retention depends on local law.

The privacy purpose stays the same when you use DANA, OVO, GoPay or QRIS: we record references and status needed to match the wallet event with your account. We do not ask for private wallet credentials, and access remains where local law permits.