Reference

Privacy Policy for Your pulau 88 Account

Our Privacy Policy shows how we collect, use and protect the details connected with your pulau 88 account, from phone verification to DANA, OVO, GoPay and QRIS records.

Clear data purposesWallet record contextAccount request pathMobile and desktop use
pulau 88 Privacy Policy for Your pulau 88 Account
REQUEST HELP

Get Privacy Policy Help From Your Account

A clear request path matters when a name, phone number or wallet reference needs attention. We ask you to contact account help from the signed-in support route and include the detail you want checked, without sending a password or one-time verification code. If your concern relates to DANA, QRIS or a bank transfer, keep the payment receipt reference available so we can identify the record safely. We handle privacy requests according to the policy and local law.

Team online

Account help

Use the support route attached to your account when you want to ask about personal data, a phone verification record or a correction. We may ask you to confirm account ownership before discussing details, so another person cannot obtain your account history.

Wallet receipt check

For a DANA, OVO, GoPay or QRIS question, send the payment reference through account help rather than posting it in an open message. We compare the reference with the related cashier record and explain what data was used for that check.

Security concern

If a sign-in, device session or phone verification event looks unfamiliar, tell us through the signed-in support path as soon as possible. We can check the account event, guide the next identity step and avoid exposing private records during the conversation.

HANDLING DETAILS

How We Handle Your Account Data

We separate the data needed to operate an account from the records used to investigate a payment or security event.

Account details

When you open an account, we collect the details required for account access and phone verification.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can show which account initiated a payment check.

Device signals

We may record device type, browser details, sign-in time and basic session signals when you use a mobile browser or…

Cookie choices

Cookies can keep a browser session active and remember selected settings.

Retention period

We keep account, payment and security records for the period needed to operate the service, investigate disputes or meet a…

Change requests

You can ask us to correct inaccurate account details, explain a data category or clarify why a record is retained.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is checked. We keep each response tied to a real account step, device behaviour or payment reference, so you know what to prepare when contacting us. Where access or eligibility is discussed, it depends on local law and our account checks.

The pulau 88 Privacy Policy covers account details, phone verification, device and sign-in signals, cookies, payment references, support requests and relevant activity records. It also explains purposes, retention, security handling and how you can ask us to correct a detail or clarify a record.

Phone verification helps connect an account request to the correct account holder and reduces the chance of another person accessing private details. We may request it when you open an account, change an important detail or ask us to discuss a protected record.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks. We use those references to match receipts and status events with an account, and we do not ask you to send a wallet password or one-time code.

Use the signed-in account help route and state which field needs correction, such as your phone number or account name. We may ask you to confirm ownership before making a change. Include a payment reference only when it is relevant to the request.

Cookies can support a mobile browser session and remember selected settings. You can manage them in your browser controls, but blocking necessary cookies may sign you out or require another phone verification step before private account pages can open.

We retain personal data only while it supports account operation, payment reconciliation, security checks, dispute handling or a legal duty described in the Privacy Policy. When a record is no longer needed for those purposes, we follow the applicable deletion or anonymisation process.

Contact us through the signed-in account help path and describe the device type, approximate sign-in time and any related phone verification event. Do not send your password or one-time code. We use those details to locate the session while protecting the rest of your account.