Reference

Privacy Policy for Your svip2 Account

Clear handling of your account, device and wallet details is the purpose of this Privacy Policy.

Account access recordsWallet data clarityMobile privacy choicesIndonesia policy scope
svip2 Privacy Policy for Your svip2 Account
POLICY HELP ROUTES

Get Privacy Help Near Your Account

A clear contact route helps when you want to ask about a record, correct an account detail or understand a wallet status entry.

Privacy contact form Use the privacy contact form for questions about collection, storage, sharing or deletion. Include your account phone number and a short description of the requested change so we can locate the correct record without asking for unnecessary wallet details.
Account support panel The account support panel is suited to access concerns, phone verification questions and device sessions. Tell us whether the issue appeared on mobile browser or desktop, and we can connect the privacy request with the relevant sign-in record.
Payment record request For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference shown on your receipt. We use that reference to check status while limiting the request to the transaction connected with your account.
HANDLING BY DESIGN

Inside svip2 Privacy Controls

Our handling approach follows the practical steps you meet when opening and using an account: collect what is needed, connect it to the right session, protect access and keep records for a…

Data we collect

We may handle your phone number, verification result, account activity, device signals and transaction references. These details help connect a login with the correct account and identify a payment status without requiring access to the wider contents of your DANA, OVO, GoPay or QRIS wallet.

Cookies and sessions

Cookies and similar session records help keep your sign-in path working across the mobile browser or desktop browser you choose. They can remember a session state and support security checks; you can manage browser controls, although some account functions may then need another verification step.

Account security

Phone verification takes place before account access, and sign-in activity may be checked against device and session signals. If a login looks unfamiliar, contact support through the account path and do not send a password, wallet PIN or one-time code in a message.

Record retention

We retain account, payment and support records only for the operational, dispute-handling or legal purpose that requires them. When a record no longer serves that purpose, our handling process moves it toward deletion or de-identification, subject to obligations that may still apply.

Who receives data

A payment reference may be shared with a payment or banking service when needed to confirm a transaction, while support records may be accessed by the team handling your request. We do not treat a request about one receipt as permission to disclose unrelated account activity.

Requesting a change

To request access, correction or deletion, contact us through the privacy form and describe the record involved. We may ask for account verification before changing it, because protecting the account comes first; the result also depends on local law and required record duties.

Privacy Policy Questions For Indonesia

These answers address the privacy searches we hear most often before an account is opened or a payment record is checked. They focus on svip2 account data, mobile access, local wallets and the steps available when you want a copy, correction or explanation.

The Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains why we use each category, when a service may receive limited transaction data and how you can ask for access, correction or deletion.

We use payment references and status details needed to match a DANA, OVO or GoPay transaction with your account. This does not mean we receive the wider contents of your wallet. A receipt reference lets us investigate one payment without requesting unrelated wallet data.

Phone verification helps us connect the person signing in with the correct account and identify unusual access. It also supports a privacy request when you ask us to change or disclose account data. We will not ask you to send a password or one-time code.

For QRIS, bank transfer and virtual account payments, we may retain the reference, status, sending bank detail and reconciliation result. BCA, BRI, Mandiri or BNI may appear in a transfer record. We use those details for confirmation, disputes and required record duties.

Yes. Send a correction request through the privacy contact form, identify the account detail that is wrong and complete any verification we request. We limit the check to the relevant account, then assess the change under this Privacy Policy and where local law permits.

Use the privacy contact form and state which account records you want deleted. We first verify the request, then remove or de-identify data where no operational or legal reason requires retention. Some payment, dispute or legal records may need to remain for a permitted period.

Yes, the policy applies when you access the account from a mobile browser in Jakarta or elsewhere in Indonesia. Cookies, device signals and session records may support sign-in security. Account access and eligibility depend on local law, including rules applying to your location.