Reference

Open Your Privacy Policy Details

sgp live draw Privacy Policy explains how we handle the account, device and payment details connected with your access to our lobby.

Clear data purposesPayment detail controlsAccount contact routeMobile privacy choices
sgp live draw Open Your Privacy Policy Details
CONTACT OPTIONS

Find Help For Privacy Requests

A clear contact path helps you act on this Privacy Policy without searching through account screens.

Account support link Sign in, open the support route, and state whether your request concerns phone verification, a device record, or account data. We may confirm your registered number before discussing details so another person cannot obtain your account information.
Payment data request For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, send the receipt reference and date through support. Do not send a wallet PIN or password. We use the reference to locate the relevant record.
Privacy clarification If a paragraph in this Privacy Policy is unclear, quote the section and describe your question through our support channel. We can explain the purpose, retention reason or correction route without asking you to disclose unnecessary personal details.
DATA CONTROLS

Switch Through Your Privacy Choices

Privacy controls work best when they match the account actions you actually take. We review the information needed for sign-in, phone verification, security checks and payment reconciliation, while access to the lobby…

Account data

We may hold your name or account identifier, registered phone number, verification status and support correspondence. These records help us connect a request to the correct account and prevent changes being made by an unauthorised person.

Device records

When you sign in through a phone or desktop browser, we may record device, browser, session and security-event details. These signals help us investigate unusual access and do not turn your device into a public profile.

Cookie choices

Session cookies can keep your account path working between pages, while technical cookies help identify loading or sign-in faults. You can adjust browser cookie settings, but restricting session cookies may require you to authenticate again.

Payment references

A selected DANA, OVO, GoPay or QRIS route may leave a method label, amount reference and status record in the account flow. Bank transfer and virtual account records can serve the same matching purpose without exposing wallet credentials.

Retention approach

We keep records only for the period needed for account security, payment matching, dispute handling, legal duties or a documented support request. When a record no longer has a valid purpose, our handling follows the applicable retention process.

Change requests

Ask us to correct an inaccurate account detail or explain a retained record through support. Include your registered phone number and the specific field or event. We may verify ownership first, then confirm the action or reason it cannot be changed.

Browse Answers About Privacy Policy

These Privacy Policy answers address the searches we most often expect before an account is opened. They cover the practical points behind phone verification, mobile sign-in, cookies, payment references, corrections and account contact. If your situation is different, use the support route with a focused question. We will ask for an ownership check when the request could reveal or change personal account data.

It covers account details, phone verification, device and session records, cookies, support messages, payment references and retention. It also explains how to ask for access, correction or clarification. The policy applies to your use of our services where local law permits.

We use your phone number to create the account path, complete a phone verification step and help protect sign-in requests. It can also help support locate the correct account. We do not need your wallet PIN or password for this process.

Yes. The Privacy Policy covers method labels, status details and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. These records help match a receipt or investigate a status question without requesting wallet credentials.

We may record browser, device, session and security-event details when you sign in from a phone or desktop. These records help us identify unusual account access and technical faults. You can contact support if a device entry appears unfamiliar.

Use the support route while signed in and describe the exact record or account field you want copied or corrected. Add your registered phone number, but do not send a password or wallet PIN. We may verify ownership before responding.

Retention depends on the reason for holding the record, such as account security, payment matching, dispute handling, legal duties or a support request. We remove or stop using records when the applicable purpose and retention requirement have ended.

You can adjust cookie settings in your browser. Session restrictions may require another sign-in or affect parts of the account path, while technical records may still be needed to investigate security or loading faults. Support can explain a specific cookie question.