Reference

Privacy Policy for boom88i accounts

Our boom88i Privacy Policy explains what we collect when you open an account, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet activityCookie choicesAccess requests
boom88i Privacy Policy for boom88i accounts
HELP ROUTES

Where to ask about your account data

A clear contact route helps you act on this Privacy Policy rather than search through old messages.

Access request Ask us for a copy of account records linked to your verified contact detail.
Correction request Tell us which account field is inaccurate and provide the corrected value.
Privacy question Use the same support route for cookie, retention or device questions.
CONTROL LAYER

Six controls behind account privacy

Our privacy work follows the account journey: creation, verification, wallet activity, sign-in and support. We limit records to a practical purpose, review unusual access signals and keep a route open for corrections.

Data collection

We use contact details, verification results, payment references and sign-in events for account operation, security checks and support handling. We do not ask for a wallet PIN through ordinary support messages.

Cookie choices

Cookies and similar browser storage can remember session settings and help us identify unusual sign-in behaviour. You can review browser controls, although changing them may affect account access.

Account security

We connect device signals, login events and verification steps to help detect access that does not match your account pattern. Keep your contact detail current so security messages reach you.

Retention periods

We keep records only for the period needed for account support, payment matching, security checks or a legal duty. When a record is no longer needed, we remove or separate it.

Data changes

You can request a correction when your account record is wrong or incomplete. We may retain the earlier value in a security history so a change cannot hide an access event.

Device access

Our mobile path may read browser, operating system and session signals, not unrelated phone content. If you switch from mobile to desktop, the new sign-in can create a separate security event.

Privacy Policy answers for Indonesian accounts

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. They explain the practical steps for access, records, cookies and contact, including what happens when you move between a mobile browser and desktop session.

It covers account details, verification records, device and browser signals, cookies, payment references, support messages, retention and requests to access or correct your personal data.

We use DANA and QRIS references to match a payment with your account, show its status and investigate a receipt query. Wallet PINs are not requested through ordinary account support.

Yes. The Privacy Policy covers OVO and GoPay transaction references, status events and related support records when you connect either wallet to an account.

Contact our account support path using the contact detail attached to your account. State that you want an access request, and complete the ownership checks needed before records are released.

Yes. Identify the inaccurate field and provide the corrected value. We may ask for a verification step, while keeping a limited change history for account security.

Cookies can retain session settings and help detect unusual sign-ins. Your browser controls can restrict them, but some account access functions may not work as intended afterward.

We retain each record for the period needed for account support, payment matching, security or a legal duty. After that purpose ends, we remove or separate the record.