Reference

ips88 Privacy Policy For Your Account

ips88 Privacy Policy gives you a clear view of the account details, wallet records and device data we handle when you use our service.

Account dataWallet recordsCookie choicesContact route
ips88 ips88 Privacy Policy For Your Account
CONTACT PATHS

Wallet Status Questions Reach Our Support Route

A clear contact path helps when a Privacy Policy question is tied to a real account event. Sign in first when possible so we can match your request with the correct account record, then use the support route shown beside account and wallet status. If you are in Medan or elsewhere in Indonesia, include the payment rail, device path and approximate time so we can check the right record without asking you to send a password.

Team online

Account request

Ask us to explain, correct or remove an eligible account detail through the support route shown after login. Include your registered phone number in the secure form, but never place your password, PIN or full wallet credentials in the message.

Payment record

For a DANA, OVO, GoPay or QRIS question, provide the payment rail and transaction reference visible in your receipt. We use that reference to locate the matching record and can explain its status without requesting your wallet password.

Access concern

If your account access changes after phone verification or a device switch, contact support from the account path and describe the mobile browser or desktop used. We may ask for account checks before discussing private records with you.

DATA CONTROLS

Six Data Controls Behind Your Account

We keep this policy practical by connecting each data purpose to an account action you can recognise.

Account details

We handle the phone number and account details you submit for account opening and access checks. Keeping these details accurate helps us connect your request to the right record when you ask about the Privacy Policy.

Phone verification

A phone verification step may be used before account access or a privacy request is completed. This reduces the chance that another person receives private account details or changes records without the required account check.

Cookie controls

Cookies and similar browser storage can remember session choices and help the account path function on mobile. You can review or restrict browser cookies through your device settings, although some account steps may then need to be repeated.

Device signals

We may record device and browser signals, such as the access path and sign-in time, to protect account sessions. These signals help us investigate an unfamiliar login without treating your device as a permanent identity.

Retention period

We retain records only for the period needed for the stated account, payment matching, security or legal purpose. When a record is no longer needed, our handling follows the deletion or anonymisation process available under applicable local rules.

Change requests

You can request access to eligible records, correction of inaccurate details or clarification of a data purpose. Send the request through the support route after login, and we will complete account checks before discussing or changing private data.

Privacy Policy Answers For ips88 Access

These Privacy Policy answers address the searches we hear most often from people opening an Indonesia account. They cover what we collect, how wallet records are matched, what happens on a mobile browser and how to send a request. If your situation is not listed, use the account support path and include the specific record or access step involved.

It covers account details, phone verification, browser cookies, device signals, wallet and bank transaction references, retention and privacy requests. It also explains why each category is handled and how you can contact us about records connected with your account.

We may handle the phone number and account details you submit, along with verification results needed for access checks. We can also record sign-in time, browser path and device signals so we can protect a session and respond to account questions.

Yes. The Privacy Policy includes records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use references, rail names, status and timing to match a payment event with your account without asking for your wallet password.

Sign in where possible and send an access request through the support route connected with your account. State that you are requesting records under the Privacy Policy, then complete the phone or account checks needed to protect private details.

You can request correction when an eligible account detail is inaccurate or out of date. Use the support route after login, identify the affected record, and provide the replacement detail. We may verify your account before making a change.

Retention depends on the reason for keeping a record, such as payment matching, account security or a legal requirement. Our Privacy Policy describes the applicable handling, and you can ask support why a particular DANA, QRIS or bank record remains.

Yes. It covers the mobile browser path as well as desktop access, including cookies, session details and device signals. If you change devices or clear browser storage, phone verification or another account check may be required before private records are discussed.