Reference

polo118 Privacy Policy for Your Account

Our polo118 Privacy Policy explains what we collect when you open an account, browse the lobby, or use DANA and QRIS, and why each detail is needed.

Clear data purposesCookie choicesAccount access stepsPrivacy contact path
Browse Our Lobby Read FAQ
polo118 polo118 Privacy Policy for Your Account
CONTACT ROUTES

Reach Support About Privacy Questions

A direct privacy question should not be mixed with a stalled login or wallet status.

Account privacy request Tell us which part of the Privacy Policy you are asking about and include…
Payment record query For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, share the transaction…
Access and cookie help If the Privacy Policy page or cookie controls do not display correctly on your…
DATA HANDLING

Explore How We Handle Your Data

Privacy at polo118 is managed through ordinary account operations rather than vague promises. We separate login protection from payment matching, limit internal access to details needed for a task, and retain records…

Account details

We collect details you enter during account creation, including the phone number used for verification. That information supports account recovery and access checks; it is not a reason for us to request your password or one-time code.

Device and browser data

A mobile browser may send device type, browser version, language, and access timestamps. We use these signals to detect unusual sign-in patterns, keep the policy page working, and understand whether a session belongs to your account.

Cookie controls

Cookies can keep a session active, remember selected settings, and help us identify technical faults. Open the cookie controls from the policy page to adjust available choices; blocking some cookies may affect account access or saved settings.

Payment references

We record payment references and status details needed to match DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. We use the reference to resolve the account event, not to create a separate marketing profile.

Security checks

Phone verification and session checks help protect account entry. If an action looks unusual, we may pause the request and ask you to confirm ownership through the account path. Never share a password or verification code with support.

Retention and changes

We keep records for the period needed for account operation, payment queries, disputes, or legal duties, then remove or restrict them where applicable. Ask us to access, correct, or delete eligible data using the support route.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain the practical difference between account data, payment references, cookies, device signals, and a request sent to support. If your question is not listed, use the account privacy path and describe the exact record or policy section you want us to check.

The polo118 Privacy Policy covers account details, phone verification, login events, device and browser signals, cookies, payment references, support messages, retention, and privacy requests. It explains why we use each category and how you can ask about access, correction, deletion, or cookie choices.

We collect details you provide for account creation and phone verification, plus technical records created when you sign in. These can include your phone number, session timestamps, browser type, device details, and account actions needed to protect access and resolve a support request.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use the reference to match an account event or investigate a receipt question, while avoiding requests for your wallet password.

Cookies may keep your session active, remember selected settings, and help us identify technical faults. The policy page provides available cookie controls. If you block a cookie used for account access, some sign-in or saved-setting functions may not work as expected.

You can ask us to check eligible account data, explain its purpose, or correct an inaccurate detail through the support path inside your account area. We verify account ownership first, then assess the request under the Privacy Policy and applicable local requirements.

We retain different records for the time needed to operate an account, match payment activity, resolve disputes, protect access, or meet legal duties. The Privacy Policy explains the relevant purpose, and you can ask support whether a particular record remains necessary.

Use the privacy support route shown in your polo118 account area and state whether you need access, correction, deletion, cookie help, or clarification. Include the relevant account detail or payment reference, but do not send a password or one-time verification code.

Related Pages

polo118 Indonesia FAQ Lightning Roulette Room polo118 Casino Account information