Reference

sgp pools Privacy Policy for Your Account

The sgp pools Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, browse Live Roulette Grand, and use local…

Account dataWallet recordsDevice choicesPrivacy requests
sgp pools sgp pools Privacy Policy for Your Account
PRIVACY HELP DESK

Get Privacy Policy Help Near Cashier

A privacy question should not slow down your account flow. We give you a direct route from the signed-in account area to request access, correction, or clarification about a wallet record.

Account privacy request Use the privacy contact route in your signed-in account area when you want to ask what personal data we hold. Add your registered contact detail so we can verify the request before discussing records connected with your sgp pools account.
Wallet record question For a DANA, OVO, GoPay, or QRIS record, share the payment reference and date rather than private wallet credentials. We use that reference to locate the status, explain what was stored, and keep the request tied to the correct account.
Login and device concern If a new phone, browser session, or login alert looks unfamiliar, contact us through the account support path before sending extra documents. We can check the security event, guide the verification step, and record your privacy concern for follow-up.
DATA CONTROL DETAILS

How We Protect Account and Wallet Data

We keep this policy practical by linking each data use to a real account action. A login creates security records, a wallet payment creates a reference trail, and a mobile session may…

Account creation

When you open an account, we collect the contact details needed for the account path and phone verification before access. We use them to identify your account, send account-related messages, and distinguish your records from another person using the same device.

Cookies and sessions

Cookies and session markers help keep your signed-in path connected while you move from account access to the lobby. On a phone or desktop browser, they can also help us detect unusual sign-in behaviour. You can manage browser cookie settings, though some account functions may then need another check.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we retain the reference, amount status, and related account link needed for reconciliation. We do not ask us to store your wallet password, and you should never include it in a support message.

Account security

Phone verification, sign-in records, and device signals help us investigate an account access concern. If you switch from mobile to desktop or see an unfamiliar session, tell support through the account route so we can compare the event with your account history.

Retention approach

We keep personal and transaction records only for as long as needed for the purpose described here, account security, dispute handling, or a legal duty where local law permits. When a record no longer serves those needs, our handling process moves it toward deletion or removal of identifying detail.

Changes and contact

You may ask us to correct inaccurate account details, explain a data use, or provide an accessible copy of eligible records. Send the request through the privacy contact path with your registered contact detail; we may verify ownership before making a change or releasing account data.

Privacy Policy Questions About Your Account

These answers address the privacy searches we expect when you are deciding whether to open an account or checking a payment record. Each answer applies to our handling of account, device, cookie, and transaction data, with access and eligibility depending on local law.

The sgp pools Privacy Policy covers account details, phone verification, device and session records, cookies, support messages, and transaction references. It explains why we use each category, how we protect it, how long we retain it, and how you can request access or correction.

No. For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we use payment references and status details to connect a transaction with your account. Never send a wallet password, card secret, or security code in a privacy request.

Open the privacy contact route from your signed-in account area and state that you want a copy of eligible personal data. Include your registered phone or email and a clear request. We verify account ownership first, then explain the records available and the delivery step.

Yes, you can ask us to correct inaccurate contact or account details through the privacy support path. Tell us which field is wrong and provide the registered contact detail. We may ask for an account verification step before changing information tied to access or payment records.

Device signals, cookies, and session markers help keep your login connected while you move between the account page and lobby. They also help us investigate unusual access, such as a new browser or phone. You can adjust browser cookie settings, subject to account function requirements.

We retain payment references and related account records for the period needed to reconcile status, handle a dispute, protect account security, or meet a legal duty where local law permits. The exact period can differ by record type and the reason it was collected.

Use the privacy contact route in your signed-in account area and describe the concern without including passwords or full security codes. For a DANA, OVO, GoPay, or QRIS question, add the transaction reference and date so we can locate the correct record.