Reference

svip11 Privacy Policy Explained Clearly

svip11 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the mobile lobby and live tables.

Account dataWallet recordsCookie choicesAccess requests
svip11 svip11 Privacy Policy Explained Clearly
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear support path helps when you want to understand a Privacy Policy request rather than guess which account screen to use. Contact us through the support route shown inside your account and include the phone number linked to your profile, without sending a wallet password or payment secret. We can explain a receipt match, a device sign-in record, or a correction request. If you reach support after checking your cashier status, we can connect the privacy question to the right account record.

Team online

Account support

Use the signed-in support route for a Privacy Policy question about your phone verification, account details or a device record. We first match the request to your account step, so you should include the registered phone number and the subject you want checked. Never send your password or wallet PIN.

Wallet receipt check

For DANA, OVO, GoPay or QRIS questions, keep the payment receipt reference ready and contact support through the cashier path. We can check whether the reference is attached to your account record, explain its status, and tell you which privacy request applies without asking for your wallet secret.

Access request

If you want a copy, correction or removal review for eligible account data, state the request plainly through support. We may ask for an account verification step before discussing personal details. That step protects your profile while we identify the correct record and explain any retention reason.

DATA HANDLING

Six Privacy Controls We Keep Visible

Privacy is handled through account routines you can recognise, not hidden wording. We separate contact details from wallet references, use device signals to spot unusual access, and keep cookies tied to their…

Collected account details

We collect details needed to create and protect your account, such as a phone number, verification state and sign-in activity. If you browse the lobby from a mobile device, technical details such as browser type and session time may help us keep the account path working and identify unusual access.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and time record for account matching. Bank transfer and virtual account records serve the same purpose. We use these details to trace a cashier question, not to request your wallet password or private wallet PIN.

Cookies and device use

Cookies can remember a session choice and help us understand whether the mobile account path is functioning. Device signals can support sign-in checks when you move from the lobby to a live table. You can manage browser cookies through your device settings, although some account steps may then need to be repeated.

Account security

Phone verification comes before account access, and sign-in records help us investigate an unfamiliar session. If your access changes after opening Aviator Fast Round or another lobby area, support may ask you to confirm the account step. We do not ask you to disclose a password in a support message.

Retention choices

We keep personal and transaction records only for the period needed for the stated account, security, dispute or legal purpose. A request to remove data may not erase records that must remain for those purposes. Support can explain which category applies and what can be changed.

Correction route

If your phone detail, verification status or account record is wrong, contact us through the signed-in support path and describe the correction. We may verify ownership before editing anything. For a wallet mismatch, include the receipt reference, but leave out wallet credentials and private security codes.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. We explain the records created by phone verification, payment references, cookies and device access in direct terms. If your situation is not covered, use the support path while signed in and ask us to identify the relevant account record.

The svip11 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, payment references and support requests. It applies when you access the mobile or desktop lobby, including activity connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

No. The Privacy Policy describes transaction references and status details needed to match DANA or QRIS activity with your account. We do not ask you to send a wallet password, PIN or private security code in support chat, and you should not include those details in a request.

Phone verification helps connect the correct person to an account before access and gives support a safe way to identify your record. The Privacy Policy also covers the verification result and related sign-in event. If the detail is inaccurate, request a correction through the signed-in support route.

Where local law permits, you can ask us which personal account records we hold and request a copy of eligible data. Use the support path while signed in, name the record you want, and complete any ownership check. We will explain the format, scope and timing of the response.

Cookies can keep a session choice and help us check whether your account path works on the device you use. The Privacy Policy explains their purpose. You can adjust cookies in your browser settings, but turning them off may require another sign-in or repeat a step before the lobby opens.

The Privacy Policy does not set one period for every record. We retain DANA, OVO, GoPay, QRIS, bank transfer and virtual account references for the period needed for matching, security, disputes or legal duties. Support can explain the category and retention reason for your specific account.

Yes. Account access and any privacy request depend on local law, and we apply the available process where local law permits. If you are in Indonesia and need help understanding a request, contact support from your account with your registered phone number and the record concerned.