Reference

Privacy Policy For Your siap11 Account

siap11 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice accessPrivacy requests
siap11 Privacy Policy For Your siap11 Account
REQUEST A CHANGE

Privacy Help Through Your Account Path

A privacy request should reach us with enough detail to locate the correct account without exposing your credentials. Start from the account support route, state whether you want access, correction, deletion or a processing question, and include the relevant wallet reference only when needed. We may ask you to complete phone verification before changing account-linked data. If you are in Surabaya or another Indonesian location, the same request path applies where local law permits.

Team online

Account support route

Open the support area after signing in and identify your privacy request clearly. We use your account details to locate the correct record, while phone verification helps prevent another person from asking for changes on your behalf.

Wallet record question

For a DANA, OVO, GoPay or QRIS question, mention the date and reference shown in your account. Do not send a wallet password, security code or full banking credential; we only need enough detail to trace the record.

Access correction request

Ask us to access or correct personal data through the same support path used for account help. We may confirm your phone number and account ownership before responding, with the available action depending on local law.

DATA HANDLING

What This Privacy Policy Covers

Privacy choices are easier to use when each data point has a clear purpose. We separate account access records from wallet references, explain why device signals may appear, and keep the request…

Account details

We may collect details you provide when opening an account, such as your contact data and phone number. Phone verification connects the account to your access request and helps us distinguish a genuine account action from an unknown sign-in attempt.

Access and device signals

Sign-in time, browser or device details and security signals can help us identify unusual account access. On mobile, these records relate to the path from login to the lobby; they do not give us access to unrelated files on your device.

Cookies and session use

We use cookies or similar session tools to keep an account session working, remember essential choices and support security checks. You can manage cookie settings through your browser, although changing them may interrupt login or account-linked privacy requests.

Wallet and transaction data

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with the related account event. We use this record to reconcile status and support a receipt question, not to collect your private wallet password.

Retention and deletion

We retain account, security and transaction records only for the period needed for the stated purpose, account support and legal duties. A deletion request can be submitted through support, but some records may remain where local law permits or requires retention.

Security and data requests

We limit account data access to operational needs and may verify your phone before releasing, correcting or changing personal details. Contact us through the signed-in support path for a copy request, correction request, deletion question or concern about account access.

Privacy Policy Answers For siap11

These Privacy Policy answers address the searches we expect before account access: what data is collected, why wallet records appear, how cookies work and how to request a change. Keep your phone verification details private, use the signed-in support route and read the specific response we provide for your account and location. Access and any available request depend on local law.

The siap11 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, wallet references and transaction records. It also explains retention, security and how you can request access, correction or deletion through the account support route.

We use your phone number for account setup and a clear verification step before account access or certain privacy changes. This helps connect a request to the right account. Keep verification codes private; we will not ask for your wallet security code.

Yes. This Privacy Policy explains how DANA, OVO, GoPay and QRIS references can be connected to an account event, receipt or status check. We use enough payment detail to reconcile the record and support you without requesting a private wallet password.

You can send a correction request through the signed-in account support route. Tell us which detail is wrong and provide the account contact needed for verification. We may confirm your phone number first, and the available action depends on local law.

We keep personal, security and transaction records for as long as needed for the purpose described in this Privacy Policy, account support and applicable legal duties. You can ask about deletion through support, although some records may remain where local law permits or requires it.

Yes, request access through the account support path and describe the records you want, such as profile details, sign-in events or wallet references. We may verify ownership before responding. The scope and timing of a data copy depend on local law.

Cookies can keep your session active, remember essential settings and support security checks while you move from login to the lobby. Browser controls let you manage them, but blocking required cookies may prevent account access or interrupt a privacy request.