Reference

Open 88pulsa Privacy Policy Clearly

88pulsa Privacy Policy explains how we collect, use and protect details connected with your account, wallet checks and lobby access.

Account dataCookie choicesPhone verificationIndonesia access
88pulsa Open 88pulsa Privacy Policy Clearly
CONTACT YOUR WAY

Browse Support Paths for Privacy Requests

A clear contact route helps you resolve a privacy question without repeating your account story. Start from the support path beside your account and include the phone number used for verification, the subject of your request and any relevant receipt reference. We may ask for an account check before releasing personal details, because a request about a QRIS receipt or a device session must reach the right account. Access questions remain subject to where local law permits.

Team online

Account data request

Ask us to confirm the personal details connected with your account, such as your verified phone number, login record or wallet reference. Include the phone used at account creation so we can compare the request with the account record before responding.

Correction request

If your account detail is outdated or entered incorrectly, tell us which field needs attention and why. For a DANA, OVO or GoPay status issue, add the relevant receipt or reference while removing unnecessary private content from your message.

Access concern

When a familiar phone shows a new login prompt or your account path stalls, contact support with the device type and approximate session time. We use those details to check access events without asking you to send your full password.

HANDLING DETAILS

Explore How We Keep Policy Practical

Privacy work is part of the account path, not a separate promise that disappears after sign-in.

Account records

We use your phone number, login details and verification results to identify the account you ask us to manage. A clear account step reduces confusion when you request a copy or correction, while authentication helps prevent another person from receiving your details.

Wallet matching

DANA, OVO, GoPay and QRIS references can appear in account records when you ask us to trace a payment status. Bank transfer and virtual account details are used for matching, not as a reason to collect unrelated wallet content.

Device signals

Your browser and device may provide session data such as device type, access time and basic technical signals. We use these checks to spot an unexpected login and to investigate why a mobile session returns you to verification.

Cookie choices

Cookies can keep your account path working between the login screen and the lobby, while limited measurement helps us understand page errors. You can adjust cookie controls in your browser, although disabling some cookies may interrupt account access.

Retention periods

We retain records only as long as needed for the purpose described in the Privacy Policy, including security checks, payment questions, disputes and duties that depend on local law. Deleting an account does not always remove records that must remain for those reasons.

Your request route

Use the account support path to ask for access, correction, deletion or an explanation of handling. State the request plainly and identify the account with its verified phone number; we may confirm ownership before changing or disclosing anything.

Browse Privacy Policy Questions Before Joining

These Privacy Policy answers focus on the questions you may have before opening an account or returning from an Indonesian mobile device. We explain the records linked to phone verification, wallet status, cookies and support requests in direct terms. If your question concerns a specific receipt, device session or account correction, use the support path with only the details needed to locate your record. Any access or eligibility point depends on local law.

It covers account details, phone verification, login activity, device signals, cookies, payment references and support messages. It also explains why we use those records, who may handle them for account service, how long some records remain and how you can request access or a correction.

We use the phone number submitted during account creation to verify account ownership, support login checks and connect a privacy request with the correct record. We do not need your full password in a support message, and we may ask for an ownership check before disclosure.

Yes. The policy covers references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details help match a payment status with your account. We use the relevant reference for tracing and do not ask for unrelated wallet content.

You can request a correction through the account support path. Name the field that is wrong, explain the change and identify the account with its verified phone number. For a wallet status issue, include the relevant receipt reference while removing private details that are not needed.

Cookies and similar tools can keep your session connected while you move from login to the lobby and can help us locate page errors. Browser controls let you adjust some cookie choices. Turning off required cookies may interrupt verification or prevent parts of the account path from working.

Retention depends on the purpose of the record. We keep some account, payment and security details for as long as needed to answer disputes, trace activity or meet duties that depend on local law. A deletion request can be limited where a record must remain for those reasons.

Use the support path and state that you want access to the personal data connected with your account. Include the verified phone number and a clear description of the request. We may confirm ownership before sending details, and we respond according to where local law permits.