Reference

hugo77 Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, use DANA or QRIS, and move between the Live Dealer…

Account recordsWallet activityCookie choicesAccess requests
hugo77 hugo77 Privacy Policy for Your Account Data
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you act on this Privacy Policy without searching through account pages. When a login record, wallet reference or cookie choice needs explanation, send the relevant account detail through our available support route. We use the smallest practical amount of data to locate the issue, and we may ask you to confirm account ownership before discussing private records.

Team online

Account privacy request

Ask us to explain, correct or remove eligible account data. Include your registered phone detail and the exact request so we can locate the right record.

Wallet record question

For DANA, OVO, GoPay or QRIS references, share the receipt code rather than your wallet password. We use that reference to check the matching account event.

Cookie or device help

Tell us whether you used a mobile browser or desktop and describe the page affected. This helps us separate a cookie setting from an account access issue.

DATA PRACTICES

Six Practical Controls For Your Privacy

Our handling of this policy area follows the account journey you can actually see: phone verification, sign-in, wallet status, lobby access and support contact.

Account data

We collect the account details needed to create and maintain access, including your registered phone detail and verification status. We use them to match you with the correct account record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account events may produce references linked to your account. We use those references for status checks without requesting your wallet password.

Cookie controls

Cookies can preserve a sign-in session and record basic page behaviour on mobile or desktop. You can adjust cookie settings in your browser, though some account pages may then require another sign-in.

Account protection

Phone verification comes before account access, and support may confirm ownership before discussing private records. Keep your sign-in details private and contact us if an unfamiliar access event appears.

Retention approach

We retain account, payment and support records only as long as needed for the stated service purpose, dispute handling or a lawful obligation. We remove or separate records when that period ends.

Change requests

You can ask us to correct eligible account data, explain its use or request deletion where permitted. Send the request through support with enough detail for ownership and record matching.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the searches we hear around account records, local wallets, cookies and access. If your question is not listed, use the support route with your registered phone detail and we will identify the relevant policy step.

It covers account details, phone verification, cookie activity, device access, payment references and support records created while you use hugo77. It also explains retention and requests for correction or deletion.

DANA and QRIS transactions create references that can be linked to your account. We use those references to check wallet status or receipts, not to request your wallet password or unrelated account data.

Our Privacy Policy does not require you to send an OVO or GoPay password to support. For a payment question, use the receipt or transaction reference so we can locate the matching event.

Cookies can keep a sign-in session active and help us see whether pages load correctly on your mobile browser or desktop. Browser controls let you change cookie choices, but another sign-in may follow.

Send a Privacy Policy request through our support route with your registered phone detail and the records you want explained or provided. We may confirm account ownership before releasing private account data.

Yes, you can request correction or deletion of eligible records under the Privacy Policy. We assess the request against account security, dispute handling and lawful retention duties before confirming the result.

The policy is available for you to read, while service access and eligibility depends on local law. If a legal requirement changes how a record is handled, we follow that requirement.