Reference

api88 Privacy Policy for Your Account

api88 Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Lightning Roulette or use DANA and QRIS.

Clear data purposesWallet record contextAccount access requestsCookie choices
api88 api88 Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Beside Account Support

A clear contact path helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Send your request through the account support route linked near sign-in, and include the phone number or account reference you use with us. We may ask for a verification step before discussing personal data, so a request cannot expose your details to another person.

Team online

Privacy request

Ask us to explain, access or correct personal data through the account support route. Include your account reference and the specific record, such as a QRIS payment status.

Login access

If phone verification blocks access, tell our support desk which device path you used and when the issue appeared. We use those details to locate the relevant security event.

Wallet query

For DANA, OVO, GoPay, bank transfer or virtual account questions, send the payment reference rather than a wallet password. We can then trace the record without requesting secret credentials.

DATA HANDLING

What Our Privacy Process Covers

We keep the Privacy Policy practical by linking each data use to an account action: sign-in, phone verification, wallet reconciliation, security review or support.

Collection

We receive details you submit during account creation, phone verification and support contact. We also record technical events such as sign-in time, browser type and the device path used.

Payment matching

DANA, OVO, GoPay and QRIS references help us connect a wallet result with the correct account. Bank and virtual account records serve the same reconciliation purpose.

Cookies

Cookies can preserve a signed-in session and remember security preferences. Browser settings let you remove or restrict them, but a fresh phone verification step may follow.

Account security

Phone verification, sign-in records and device signals help us spot access that does not match your usual pattern. We may pause a request while confirming that it is yours.

Retention

We retain records only for the operational, dispute, security and legal purposes described in the Privacy Policy. When a retention period ends, records are removed or separated from direct account use.

Changes and requests

You can ask about a stored detail, request a correction or question a processing purpose through support. We may verify identity and explain any restriction required by applicable law.

Privacy Policy Answers for api88

These Privacy Policy answers address the account and wallet questions we hear most often before access begins. They cover what we record, how you can reach us and why a verification step may appear. If your situation is unusual, send the relevant account reference through support so we can examine the correct record.

It covers account details, phone verification, sign-in and device events, cookies, support messages, game activity references and payment records connected with DANA, OVO, GoPay, QRIS or bank rails.

No. The Privacy Policy allows us to use transaction references, status and account links for reconciliation. We do not need your DANA or QRIS wallet password to check a payment.

You can contact our account support route with your account reference and request access to personal data. We may verify your identity first and apply any restriction required by local law.

Send a correction request through support and identify the detail that appears wrong, such as a phone number or account record. We will confirm ownership before changing information.

Phone verification connects account access to the correct person and helps us investigate unusual sign-in activity. It also protects payment questions involving OVO, GoPay, DANA or QRIS.

Retention depends on the operational, security, dispute and legal purpose for each record. The Privacy Policy does not keep data indefinitely for its own sake; records are removed or separated when no longer needed.

You can restrict or remove cookies through your browser controls. Some account functions may then ask for another sign-in or phone verification because the session preference is no longer available.