Reference

svip2 h5 Privacy Policy for Indonesia

Our Privacy Policy explains how we handle your account details when you browse Speed Baccarat, Starburst or other lobby areas, and when you use DANA, OVO, GoPay or…

Account dataWallet recordsCookie choicesSecurity checks

Browse Our Lobby Read FAQ

How Indonesia Data Rules Shape Privacy

svip2 h5 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to personal data you provide during account creation, phone verification, sign-in, wallet selection and support contact. We use those details to identify your account, match a DANA, OVO, GoPay or QRIS status to the correct transaction, detect unusual sign-in behaviour and answer

1
a request about your records. Some services or eligibility conditions depend on local law, and access is offered where local law permits. We do not ask you to send a payment receipt through an unconfirmed route; use the account help path connected with your cashier activity
2
instead. Policy wording may change when our data practices or legal duties change, and the current page is the version we apply to new and existing account activity.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

POLICY HELP ROUTES

Get Privacy Help Beside Your Account

A clear contact path matters when you want to ask about stored data, a wallet record or a phone verification detail.

Account data request Open the account help route after sign-in and tell us which profile detail you want checked. We use your account step to connect the request with the correct record.

Wallet record question For DANA, OVO, GoPay, QRIS or bank transfer records, include the payment reference shown in your account. We can then separate a wallet-status question from unrelated data.

Privacy correction If your phone, name or contact detail needs correction, send the requested change through account help. We may ask for a verification step before changing personal data.

HANDLING YOUR RECORDS

What Our Privacy Process Covers

We treat account data as part of the access path rather than as lobby content. Our process covers the details entered at registration, device signals used for sign-in protection, cookie preferences, wallet…

Account creation

When you open an account, we record the details needed for the profile and phone verification step. This lets us connect later sign-ins, policy requests and account changes to one record.

Cookie controls

Cookies help remember session choices and understand which page path brought you to a policy request. Your browser can remove or restrict them, although some sign-in functions may then need to be repeated.

Device signals

A mobile browser and a desktop browser may provide different device and session signals. We use these signals to notice unusual access patterns, not to replace the account details you provide.

Wallet references

A DANA, OVO, GoPay or QRIS reference helps us match a payment status with your account. We record the transaction context needed for checking, rather than treating wallet activity as public profile content.

Retention approach

We keep personal data for as long as needed for the stated account, security, payment-record or legal purpose. When a record is no longer required, our handling follows the applicable retention process.

Change requests

You can ask us to correct eligible account details or explain how a record is used through account help. We confirm ownership before making a change that could affect sign-in or payment matching.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we expect before you create an account or contact us about a record. We focus on the practical points: what we collect, how wallet references are matched, how cookies behave on mobile, and how you can request a correction. If a question involves eligibility or regional access, the answer depends on local law.

It covers account details, phone verification, sign-in signals, cookies, wallet references, support messages, retention and requests to correct eligible records. The policy applies where local law permits access.

Phone verification helps connect you with the correct account and reduces mistaken access when a sign-in or data request is made. We may repeat the check before changing important profile details.

Yes. The Privacy Policy explains how we use DANA and QRIS references, along with OVO, GoPay, bank transfer or virtual account details, to check payment status against your account.

We use cookies for session continuity, saved choices and page-path measurement connected with policy requests. You can restrict cookies in your browser, but sign-in preferences may need to be entered again.

You can contact us through the signed-in account help route and identify the record involved. We verify account ownership first, then assess the request under the Privacy Policy and applicable local law.

Retention depends on the reason for collection, such as account access, security checks, payment matching or legal duties. We remove or otherwise handle records when the relevant purpose no longer requires them.

Use account help and state whether your question concerns profile data, cookies, phone verification or a DANA, OVO, GoPay or QRIS reference. Include only the details needed to locate your request.

svip2 h5 Privacy Policy for Indonesia

Get Privacy Help Beside Your Account

What Our Privacy Process Covers

Account creation

Cookie controls

Device signals

Wallet references

Retention approach

Change requests

Privacy Policy Answers For Your Account

01 What does the svip2 h5 Privacy Policy cover?

02 Why does svip2 h5 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What cookies does svip2 h5 use?

05 Can I request a copy or correction of my data?

06 How long are account and payment records kept?

07 How do I ask about a privacy matter?

Related Pages