Reference

svip4 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a svip4 account, use the lobby, or check wallet status through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
svip4 svip4 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Privacy Policy

A clear contact route helps you act on the Privacy Policy instead of searching through account screens. If you need to check a record, correct a detail or ask why a security step appeared, contact our support team through the account support path. Include the email or phone number linked to your account, but do not send a password or wallet PIN. We use the account details you provide to locate the request and may ask for a verification step before discussing personal data.

Team online

Account support

Use the support path after signing in when you need a copy of account data, a correction to your contact detail, or an explanation of how your Privacy Policy request is being handled.

Payment record help

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference through support. We compare it with the account record before changing or explaining the stored payment detail.

Access questions

When a sign-in or phone verification step blocks access to your Privacy Policy request, tell us the device path you used, such as mobile browser or desktop browser, so we can check the event.

HANDLING DETAILS

How We Handle Your Privacy Data

We keep the handling steps practical: account details support sign-in and verification, payment references support reconciliation, and device signals help us investigate suspicious access.

Account collection

When you open an account, we collect the details needed for account access and phone verification. We use those fields to connect your login activity with the account you asked us to maintain.

Payment matching

A payment reference from DANA, QRIS, OVO, GoPay, bank transfer or virtual account can be stored with the related account event. This helps us investigate a receipt or status question without asking for your wallet PIN.

Cookie controls

Necessary cookies can keep a signed-in session working between the account screen and Privacy Policy page. Your browser settings can remove or restrict cookies, although some account functions may then require another sign-in.

Account security

We may record device, browser and login signals when checking unusual access. If a sign-in from a new mobile path needs confirmation, we may request phone verification before showing account-linked data.

Retention choices

We retain records for the period needed for the stated account, payment or support purpose and for applicable legal duties. When a record is no longer needed, our handling process addresses removal or further restriction.

Your requests

You can ask for access, correction or clarification by contacting support from the account path. We may verify ownership first, then explain what can be supplied or changed under local requirements.

Privacy Policy Answers For svip4

These Privacy Policy answers address the account and payment questions we expect Indonesian customers to raise before opening an account. Each answer follows the same practical path: identify the relevant record, protect account ownership and explain the next step. If your request concerns access or eligibility, the outcome depends on local law. Keep your transaction reference available when asking about DANA, OVO, GoPay, QRIS or bank transfer records.

The Privacy Policy covers account details, phone verification status, login events, device and browser signals, support messages, cookie settings and payment references. A DANA, OVO, GoPay or QRIS reference may be linked to the related account event for reconciliation and support.

Send an access request through the signed-in account support path and identify the email or phone number linked to your account. We may verify ownership before responding, so do not include your password, wallet PIN or full payment credentials.

Yes, you can request a correction through support when your contact detail, phone status or another account field is inaccurate. Tell us which field needs attention and provide the account identifier requested during verification; we then explain the available change.

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

Necessary cookies help keep an account session working when you move between the login screen, account area and Privacy Policy page. Browser controls can restrict cookies, but a restriction may require another sign-in or affect session-based account functions.

Retention depends on why the record was collected, such as account access, payment matching or support, and on applicable legal duties. You can ask support to explain a record category and its handling; deletion or restriction depends on the relevant requirement.

Use the account support route for an access, correction, cookie or payment-record request. Include your linked phone or email and a short description of the issue. We may request account verification before discussing personal data or changing a stored detail.