Reference

Open the svip2web Privacy Policy

Our Privacy Policy explains what happens to your account, device and payment details when you use svip2web, including DANA, OVO, GoPay and QRIS status checks.

Account dataCookie choicesWallet statusContact requests
svip2web Open the svip2web Privacy Policy
CONTACT THE TEAM

Reach Support About Privacy Policy

A clear contact path helps when you want to ask about Privacy Policy records rather than account activity itself.

Account privacy request Ask us to explain the personal details connected with your account. Include your registered contact detail and the subject Privacy Policy so we can route the request without asking you to disclose a login password.
Wallet record question For a DANA, OVO, GoPay or QRIS record, send the payment reference and date through our support route. We use those details to locate the relevant entry while keeping your wallet PIN and sign-in secret.
Correction or deletion Tell us which account detail needs correction or which record you want assessed for deletion. We may confirm ownership through the registered phone or email before changing a record or explaining why retention still applies.
DATA HANDLING

Browse Our Privacy Policy Controls

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

During the account path, we may handle your contact detail and verification result so we can associate access with the correct account. We use the registered phone or email when a Privacy Policy request needs an ownership check.

Device records

A mobile browser or desktop session can create technical records such as browser type, session time and error details. These records help us investigate failed access without treating your device as permission to collect unrelated personal content.

Cookies

Cookies can keep a signed-in session and remember selected settings. You can inspect or remove them through your browser controls, although clearing session cookies may require you to sign in again before requesting account assistance.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with an account action. We use the reference for status checks and reconciliation, not as a request for your wallet PIN.

Account protection

We limit account support changes to requests that pass an ownership check. Never include your password, wallet PIN or one-time code in a message; a payment receipt or date is safer for helping us identify the correct record.

Retention and changes

You can ask which information remains on file, request a correction, or ask whether deletion is available. We explain any continuing retention connected with disputes, account security or legal duties before taking action.

Check Common Privacy Policy Answers

These Privacy Policy answers focus on the questions you may have before opening an account from Indonesia. We cover the data connected with sign-in, wallet references, cookies, device use and requests for access or correction. If your situation is not listed, contact us through the account support route and identify the relevant record without sharing a password or wallet PIN.

The svip2web Privacy Policy covers account details, verification results, device and browser records, cookies, support messages and payment references. It explains why we use each category, how you can ask about it, and when access depends on local law.

Yes. The Privacy Policy includes references connected with DANA, OVO, GoPay and QRIS activity, along with bank transfer or virtual account references where relevant. We use those references to check status and match an account action, not to request wallet credentials.

You can contact our support route to ask what personal details are connected with your account. Include your registered phone or email and the wording Privacy Policy. We may verify ownership first, then explain the available access process and any limits.

Send a correction request through the account support path and identify the detail that is wrong. We may confirm your registered contact information before changing it. For a wallet record, include the date and reference, but never send a PIN or password.

On a mobile browser, cookies may keep your session active and remember selected settings. Your browser controls let you remove or restrict them. Clearing session cookies can sign you out, so keep your registered contact detail available if support needs to confirm ownership.

You can ask us to assess deletion of a particular account record through support. We first confirm ownership and identify the requested data. Some records may need to remain for account protection, dispute handling or legal duties, and we explain that reason.

Use the support route displayed near your account area and write Privacy Policy in the subject. Describe the data category, such as a device record or QRIS reference, without including secret credentials. We will use your registered contact detail to continue the request.