Reference

sugiha4d Privacy Policy for Indonesia Accounts

Our Privacy Policy explains how sugiha4d handles the details you provide when opening an account, signing in from a mobile browser, or checking activity across casino, sports and…

Clear data purposesCookie choicesAccount contact pathWallet record context
sugiha4d sugiha4d Privacy Policy for Indonesia Accounts
CONTACT DATA HELP

Privacy Requests Through Your Account Path

A clear contact path helps when you want to ask about your Privacy Policy rights or correct an account detail.

Access request Ask us which personal details are connected with your account and why they are used. We may request account verification before sending a response or exposing records linked to DANA, OVO or QRIS activity.
Correction request If your phone number, contact detail or account status appears incorrect, tell us through the account support path. Include the specific field and a safe reference so we can check the correct record.
Wallet status query For a payment receipt or status question, provide the rail name, such as GoPay, bank transfer or virtual account, plus its reference. We use that information to trace the transaction without requesting your wallet password.
DATA HANDLING DETAILS

What We Do With Account Information

Our Privacy Policy separates account necessities from optional browsing functions. We record enough detail to verify sign-in, protect the account and answer a transaction question, while cookies help remember session choices on…

Account details

We may handle your name, phone number, sign-in details and verification status when you open an account. These details let us match the right account during access checks and correction requests.

Activity records

Sign-in time, device path and selected areas such as Bingo or Fishing God can create activity records. We use them to protect sessions, investigate account questions and maintain an accurate request history.

Cookie controls

Cookies can support a continuing session on your mobile browser or desktop browser. You can manage browser cookie settings, although removing required cookies may interrupt sign-in and prevent the account area from loading correctly.

Account security

Phone verification and sign-in checks help us distinguish your account from an unauthorised access attempt. Never send a password or one-time code in a contact request; we will use safer account checks.

Retention approach

We retain account, security and transaction records for as long as needed for the stated service purpose, dispute handling or legal duties. When a record is no longer needed, our process removes or anonymises it.

Changes and contact

You can ask about access, correction or deletion through the signed-in support path. Tell us what you want changed, and we may verify your phone number before making or explaining the requested update.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the searches we expect from someone deciding whether to open an account. They explain the data connected with login, mobile browsing, local wallet checks and requests made through our support path, without turning a privacy question into a general lobby description.

It covers account details, phone verification, sign-in activity, browser cookies, game-area activity, payment references and support requests. We explain the purpose for each category and apply access depends on local law.

Yes. If you use DANA or QRIS, we may retain a payment reference, status and related account details needed to confirm the request, answer a receipt question or address a transaction discrepancy.

Phone verification helps us connect an access request with the correct account and identify unusual sign-in activity. It also supports correction or deletion requests, but you should never send us your private code.

Use the signed-in account support path and ask for an access request. Include your linked phone number and the records you mean, such as cookie, account or GoPay transaction details.

Yes. Send a correction request through account support, identify the incorrect field and provide a safe account reference. We may verify your phone number before changing the record.

We keep information for the time needed to provide account access, protect sessions, handle disputes or meet legal duties. After that need ends, the record is removed or anonymised through our process.

Cookies can maintain your session and remember browser settings on mobile. You can change cookie controls in your browser, but required-cookie removal may stop sign-in or the account area from working.