Reference

Privacy Policy For Your Account Journey

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

Account dataWallet recordsCookie choicesContact requests
shio kambing 5 Privacy Policy For Your Account Journey
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps you question a record without explaining your whole account history.

Account request Use the support route inside your account to ask what personal data is held for your phone verification or sign-in record. We may ask for an account step that confirms the request comes from you before discussing private details.
Wallet record For a DANA, OVO, GoPay or QRIS record, send the payment reference and status shown in your account. We use that reference to trace the entry, while the wallet provider remains responsible for its own customer data.
Correction request If a name, phone detail or account entry needs correction, describe the exact field and the device used to reach it. We will check the account record and explain any step required before changing information linked to access.
DATA HANDLING

How We Manage Privacy In Practice

Privacy is handled through the same account steps you already use: phone verification, sign-in, wallet status checks and device access.

Account details

We use your phone verification and sign-in details to connect the right account to the right person. If you enter the lobby from a new phone, device and session signals can help us check access without requesting your DANA or QRIS password.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can carry a reference, amount status and time. We use those fields to match a receipt or pending status, not to take control of your external wallet.

Cookies

Cookies can keep a session active, remember a language or device choice and help us identify a broken account step. You can clear browser storage through your phone or desktop settings, although a later sign-in may ask for verification again.

Security checks

Phone verification comes before account access, and unusual device activity may prompt another check. Keep your sign-in details private and avoid sending them in a support message; our team can work from an account reference instead.

Retention timing

We retain account, security and payment reference data for the period needed for access records, status checks and applicable legal duties. When a record is no longer needed for those purposes, our retention process moves it toward removal or restricted storage.

Your request

You can ask what data is linked to your account, request a correction or ask about deletion where local law permits. Use the account support path and describe the specific record, such as a phone field or QRIS receipt reference.

Privacy Policy Answers For Account Access

These Privacy Policy answers cover the searches we expect before you open an account or check a wallet record. Each answer points you toward a practical account step, from phone verification and cookie controls to a request about payment references. If your question depends on location or eligibility, the answer remains subject to local law.

The shio kambing 5 Privacy Policy covers account details, phone verification, device and session signals, cookies, lobby access records and payment references. It also explains how to ask for access, correction or deletion where local law permits, including records connected with DANA or QRIS.

Phone verification helps connect an account request with the person trying to access it and can support an extra check on a new device. We use the verified phone detail for account security; you should not send wallet passwords or private login codes through support.

Yes. The policy explains the account-side records created when you use DANA, OVO, GoPay or QRIS, such as a reference, status and time. The external wallet or bank remains responsible for its own handling, terms and privacy practices.

Use the support route inside your account and ask for the personal data linked to your phone verification and sign-in record. Include the relevant account reference, not your password. We may complete an identity check before sharing private account details.

You can request a correction by naming the exact field, such as a phone detail or account entry, and explaining what is wrong. We will compare the request with the account record and tell you which verification step is needed before an update.

Cookies can remember a session, language or device choice when you use a phone browser. You can clear them through your browser settings, but this may end the session and require phone verification again when you return to the account.

We keep account, security and payment reference records for the time needed to provide access, check a DANA or bank transfer status and meet applicable legal duties. Retention can vary by record and location, and access depends on local law.