Reference

Privacy Policy for Your pulo88 Account

Our Privacy Policy explains what we collect when you open a pulo88 account, use the lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Account clarityWallet contextCookie choicesPolicy requests
pulo88 Privacy Policy for Your pulo88 Account
GET POLICY HELP

Clear Answers When Privacy Questions Arise

Privacy questions are easier to resolve when you send the account detail connected to the request. Our support path is designed for questions about collection, access, correction, deletion, cookies, or a wallet reference that appears in your account history. You can contact us through the available support route and describe the issue in plain English. For a faster check, include your registered phone number, device type, and the relevant DANA, OVO, GoPay or QRIS reference without sharing your password.

Team online

Account data request

Ask us what personal data is connected to your account and why it is used. We may ask for the registered phone number and a verification step before discussing details, so another person cannot obtain your account records.

Cookie question

Tell us if a browser cookie appears unexpected or if you want help understanding session storage. Include whether you are using a mobile browser or desktop browser, because cookie behaviour can differ between those two access paths.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference is attached to the wrong account activity, send the date, rail name and reference through our support path. Do not include your password or a full wallet security code.

DATA HANDLING

What We Do With Your Privacy Choices

We keep the Privacy Policy practical by tying each data use to an account action you can recognise.

Account details

We use the contact details you provide to create and maintain your profile, send account-related responses, and connect a verified phone number with the correct login path. If a detail changes, contact us so we can assess the requested correction.

Device sessions

A browser or mobile device can produce session and security signals when you sign in. We use these signals to spot an access pattern that does not match your account and may ask for another phone verification step before access continues.

Cookies

Required cookies support sign-in continuity and page settings, while other browser storage can help remember the path you selected. You can manage browser controls on your device, but disabling required cookies may interrupt account access.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to trace a payment-status question. We use the reference for that purpose and ask you to remove unnecessary wallet details from any message.

Retention steps

We retain account and transaction records only as needed for account administration, security checks, dispute handling, or a period required by applicable rules. A deletion request may not remove records that must be kept for those purposes.

Change requests

To request access, correction or deletion, contact our support path with your registered phone number and a clear description of the request. We verify account control first, then reply with the next step and any applicable restriction.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the questions we expect before you create an account or return from a mobile device. They explain account records, cookies, wallet references, deletion requests, and access conditions in direct terms. If your situation is different, use the support path with the smallest useful amount of account detail. We can then confirm the correct process without asking you to disclose a password or full wallet security code.

The pulo88 Privacy Policy covers personal details used for account opening, phone verification, sign-in sessions, cookies, support requests, and payment-status checks. It also explains retention, data requests, and how we handle references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect account access to the person who controls the registered number. It can also support an extra check when a browser or mobile device shows an unusual session. We use the result for account security and do not need your password in a support request.

Yes. The Privacy Policy covers required cookies and similar browser storage used to keep sign-in steps and page settings consistent. Mobile browsers can handle storage differently from desktop browsers, so disabling required cookies may stop account access or remove saved session settings.

You can ask us to correct personal data that is inaccurate or incomplete. Send the request through our support path with your registered phone number and the specific field to change. We verify account control first, then confirm whether the correction can be applied.

Contact us with a clear deletion request and the phone number connected to your account. After verification, we explain what can be removed and what must remain for account administration, security checks, payment tracing, dispute handling, or a period required by applicable rules.

Yes. DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account references, can be used to investigate a payment-status question. We ask only for the details needed to trace the event, and you should never send a password or full security code.

Yes, access and eligibility depend on local law. Our Privacy Policy describes how we handle data for the service, but it does not change the rules that apply in your location. If you are unsure, contact support before opening an account so we can explain the available path.