Reference

sugih4d Privacy Policy Explained

Our Privacy Policy explains how sugih4d handles your account details, wallet records and device data when you open the lobby from Indonesia.

Account dataWallet recordsCookie choicesAccess requests
sugih4d sugih4d Privacy Policy Explained
CONTACT PATHS

Privacy Help Beside Account Support

You can ask about this Privacy Policy through the support route shown inside your account area. We keep policy questions separate from game requests, so a question about QRIS receipt data, phone verification or cookie choices reaches the right handling path. If you are in Yogyakarta or elsewhere in Indonesia, use the same account contact route; access depends on local law.

Team online

Account contact

Open the support route after sign-in and identify the email or phone attached to your account. We use that account step to check identity before discussing stored personal data.

Wallet records

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather than your wallet password. We can trace the status while limiting the details shared in replies.

Policy requests

Ask us to access, correct or remove eligible account details through the displayed contact route. Our support hours and response path are shown there so you can follow the request.

HANDLING DETAILS

How We Apply This Privacy Policy

Privacy work happens at practical account points rather than in a separate hidden process. We record only the details needed to connect sign-in, wallet status, device behaviour and support history, then apply…

Account data

We may hold your name, contact details, verification result and sign-in history to create the account and protect access. Phone verification helps us distinguish an authorised account step from an unusual sign-in.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match payment status. We do not need your wallet password to investigate a receipt or pending reference.

Cookies

Cookies and similar device markers can keep a session working, remember selected settings and help detect repeated sign-in failures. You can manage browser cookie controls, though some account steps may then need repeating.

Account security

We use sign-in records, phone verification and device signals to identify unusual access. If an Aviator or Bingo session appears after a device change, these checks help us investigate without exposing private account details.

Retention

We retain account, payment and support records for as long as their operational or legal purpose requires. When a record no longer serves that purpose, we remove it or separate it from direct account identification.

Your requests

You may ask what eligible data we hold, request a correction, or ask about deletion through the account support route. We may request account verification before changing or disclosing personal records.

Privacy Policy Questions for sugih4d

These answers address the policy searches we hear most often before account access. Each response points to a concrete account, device or payment step, so you know what to prepare when contacting us. Availability and eligibility depend on local law.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references and support messages connected with your account and access to the lobby.

No. We use payment references, status and receipt details for DANA and QRIS checks. Your wallet password should remain with the relevant wallet service and should not be sent to support.

Use the support contact route inside your signed-in account and ask for an access request. Include the account phone or email, then complete any identity check we request.

Device and sign-in signals help connect your mobile or desktop session to account security. They can help us investigate an unexpected login without collecting the content of your personal device.

Yes. Send a correction request through account support and identify the field that needs changing. We may verify your phone or email before updating the stored record.

Retention varies by the payment, support or legal purpose involved. DANA, OVO, GoPay, QRIS and bank references remain only as long as the applicable operational or legal need requires.

Contact us through the policy request route shown after sign-in. You can ask about browser cookies, eligible deletion or account closure, and we will explain any verification or retention step.