Reference

svip5web Privacy Policy For Your Account

Our Privacy Policy explains how svip5web handles the details connected with your account, including phone verification, login activity and payment status.

Account recordsWallet referencesCookie choicesContact requests
svip5web svip5web Privacy Policy For Your Account
CONTACT PATHS

Privacy Questions Near Your Account Path

A clear contact path helps you ask about the Privacy Policy without repeating your account story.

Account data request Use the account help route to ask what personal details are connected with your profile. We may ask you to complete an account check before discussing phone verification records or changing contact details.
Wallet record question For DANA, OVO, GoPay, QRIS or bank transfer references, include the displayed transaction identifier and date. We use that information to separate a payment-status query from a request about your stored personal data.
Policy change request Ask us to correct, update or explain a record through the same support route linked with your account. We assess the request against identity checks, account safety and any retention need described in this Privacy Policy.
DATA HANDLING

What We Do With Your Account Details

We separate information needed for account access from details used to reconcile a wallet request.

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification. The account path may also record sign-in time and device signals so we can respond to access concerns.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained to match a cashier event with your account. We do not need your wallet password to investigate the displayed payment status.

Browser cookies

Cookies can keep a session setting or help us understand whether a page request belongs to an active account. You can manage browser cookies through your device settings, although changing them may affect the account path.

Security checks

We use phone verification, sign-in records and device behaviour to help identify access that does not match your normal account pattern. If a check pauses access, contact support rather than sharing a password or verification code.

Storage periods

We retain account and payment references for as long as needed for account administration, security checks, dispute handling and applicable legal duties. When a record is no longer needed for those purposes, our process removes or separates it.

Your correction request

You can ask us to correct incomplete account details, explain a stored record or discuss deletion where applicable. Send the request through account help with enough detail for us to identify the record without exposing sensitive credentials.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often from people opening or maintaining an Indonesian account. They cover the data attached to phone verification, payment references, browser use, device checks and requests for access or correction. If your situation is not covered, use the account help route and describe the record you want us to examine. Eligibility depends on local law.

It covers data linked with your account, including phone verification, sign-in activity, device signals, cookie settings, support messages and payment references. It also explains why we use those records, how long they may remain stored and how you can ask about correction or access.

No. Our payment records may show a DANA or QRIS reference, amount status and matching details needed for account reconciliation, but we do not need your wallet password. Never send a wallet password, card secret or phone verification code through support.

Phone verification connects the account with a contact route and helps us respond to unusual access. The Privacy Policy treats that number as account data. If the number is wrong or no longer available, ask support to explain the correction steps after an account check.

Cookies may preserve a session setting or help recognise an active browser request. You can control them through your browser or device settings. If you clear required cookies, you may need to sign in again or repeat part of the account access path.

Yes, you can ask us to identify the personal records connected with your account through account help. Include your account identifier and a precise request. We may verify ownership first, and some records can remain subject to security, dispute or legal retention needs.

Send a correction request through the account help route and state which detail is inaccurate, such as a phone number or profile field. We may ask for verification before changing it, so the request does not weaken account security or redirect wallet records.

The Privacy Policy describes our data handling, but account access and eligibility depends on local law. If your location or payment route creates a restriction, the account path may show a different result. Contact support if you need clarification about a displayed access message.