Reference

88ii Privacy Policy For Your Account

88ii Privacy Policy shows what we collect, why we use it, and how you can ask us to correct or remove eligible data.

Clear data purposesWallet status contextMobile access pathContact for changes
88ii 88ii Privacy Policy For Your Account
PRIVACY HELP PATH

Where To Ask About 88ii Privacy Policy

A direct support route helps when you need a copy of your account data, want to question a wallet reference or need a correction after phone…

Data access request Ask us for the personal data connected to your account, including contact fields, verification…
Correction request If your phone number, email address or identity detail needs correction, contact support from…
Wallet data question For a DANA, OVO, GoPay or QRIS reference that looks unfamiliar, send the transaction…
DATA HANDLING DETAILS

What We Do With Your Privacy Choices

Privacy choices work best when they match the way your account is actually used. We separate account service records from optional device signals, use cookies to keep a signed-in session working, and…

Account records

We may hold your name, contact details, phone verification result and account activity so we can maintain access and answer account questions. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account are used to match status, not to collect your wallet PIN.

Device signals

When you sign in from a phone or desktop browser, we may record device and connection signals such as browser type, session time and security events. These details help us spot unusual access and protect your account; they are not a substitute for your registered contact confirmation.

Cookies

Cookies can keep a session active, remember a language or preserve a security setting during your visit. You can manage cookies through your browser controls, although turning off required cookies may interrupt the account menu path where you open the Privacy Policy.

Account security

Phone verification is one account security step before access to protected account areas. We may request additional confirmation when a device changes or an activity pattern needs checking. We will not ask you to disclose a password or wallet PIN through a support message.

Retention checks

We review stored records against the reason they were collected, such as account service, transaction matching, legal duties or a dispute. When a retention period ends and no valid reason remains, the record is deleted, anonymised or placed beyond routine account use.

Change requests

To request access, correction, deletion or a restriction where available, use the support route linked to your account and describe the specific record. We may need registered phone or email confirmation, and we will explain any limit imposed by local law before completing the request.

Privacy Policy Questions For 88ii

The questions below address the account situations Indonesian customers most often raise before opening an account. They explain how the Privacy Policy relates to phone verification, mobile access, wallet references, cookies and requests for changes. If your situation is not covered, contact support from the account menu and keep your message free of passwords and wallet PINs.

The 88ii Privacy Policy covers information linked to your account, such as contact details, phone verification, device signals, login activity and payment references. It explains why we use each category, how retention is assessed and how to contact us about access, correction or deletion where local law permits.

Phone verification helps us confirm that an account request comes from the registered contact and supports security checks when access changes. We may use its result to protect account areas and investigate unusual sign-ins. The process does not require you to share a wallet PIN with us.

Yes. The Privacy Policy explains how we use payment references and status details connected with DANA, OVO, GoPay and QRIS. We can use those references to match an account-side transaction, while your wallet PIN and full secret credentials should remain with the relevant payment service.

You can contact us through the support path inside your account and request the personal data connected with your profile. Include the registered email or phone number, but not a password. We will confirm your identity, explain the available records and apply any limits required by local law.

Send a correction request through the account support route and name the field that is wrong, such as an email or phone number. We may compare it with your phone verification record before making a change. If a legal or security reason prevents it, we will explain why.

On a mobile browser, cookies may keep your session active, remember a language choice and support security settings while you move from login to the account menu. You can control them in browser settings. Turning off required cookies may prevent the Privacy Policy page or protected account area from working correctly.

We assess retention by purpose, including account service, payment matching, legal duties and dispute handling. When the relevant period ends and no valid reason remains, we delete, anonymise or remove the record from routine account use. You can ask support to explain the period connected with a specific request.