Reference

bnn288 Privacy Policy For Your Account Data

Your account details, wallet records and lobby activity are handled under the bnn288 Privacy Policy, so you can understand what we collect before opening an account.

Clear data categoriesWallet record controlsPhone verification detailsCookie choicesContact path
bnn288 bnn288 Privacy Policy For Your Account Data
PRIVACY HELP DESK

Where To Ask About Your Privacy

A clear contact path helps when you want to ask about the bnn288 Privacy Policy, rather than sending personal details through an unrelated channel. Use the support contact route shown on our site and include the phone number or account reference connected to your request. We may ask for a verification step before discussing wallet records, login history or a request to change data. Keep DANA, OVO, GoPay or QRIS receipts ready when your question concerns a transaction record.

Team online

Privacy request form

Send a request through our site contact form when you want to ask what account data we hold, correct a detail or ask how a Privacy Policy right applies to your account.

Account verification

We confirm the account owner before discussing phone verification results, login events or wallet references. This step helps prevent another person from receiving details linked to your bnn288 account.

Receipt context

Attach the relevant DANA, OVO, GoPay or QRIS reference only through the requested support route. We use that context to locate a record without asking you to share a wallet password.

SIX DATA CONTROLS

Six Controls Behind Account Data

We keep the Privacy Policy practical by connecting each rule to an account step you can recognise.

Collected account details

We may collect your phone number, account identifiers, verification result and messages you send to support. These details let us respond to an account question and connect a request to the correct record.

Mobile cookie use

Necessary cookies can keep a session setting or language choice available when you move from login to the lobby on a mobile browser. You can manage non-essential cookie choices through the available browser controls.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data, status changes and confirmation times. We use those details to match payment questions with the right account event.

Account protection

Phone verification and sign-in records help us examine unusual access. If a request concerns login activity, we first check account ownership before explaining the record or making a requested change.

Retention periods

We keep different data types for the periods stated in the Privacy Policy, considering account support, transaction matching and legal requirements. When a retention period ends, the record is removed or handled as the policy states.

Change requests

You can ask us to correct account details, explain a data use or consider removal where applicable. Send the request through support, identify your account, and follow the ownership check before we respond.

Privacy Policy Questions For bnn288

These Privacy Policy answers cover the searches we hear most often about account data, Indonesian wallet records, cookies and account access. We keep each answer tied to a practical step: what to submit, where to ask, or what we may need to verify. If your situation is not listed, use the support route and refer to the policy version shown on the site.

The bnn288 Privacy Policy covers account details, phone verification, login events, cookies, support messages and transaction references. It also explains why we use these records, how long different data may remain, and how you can ask about correction, access or removal where applicable.

Yes. The Privacy Policy includes records connected with DANA and QRIS, such as a reference, status and confirmation time. It can also cover OVO, GoPay, bank transfer and virtual account records when those details are needed to match an account transaction or resolve support.

Phone verification helps connect an account to the contact detail submitted during account creation and helps us examine unusual sign-in activity. The result and related access event may be recorded under the Privacy Policy, and we check ownership before discussing those records.

Use the privacy request route or site contact form and identify the account with its registered phone number or account reference. We may request an ownership check before responding. Our reply will follow the Privacy Policy and any limits that depend on local law.

You can ask us to correct an inaccurate account detail through support. State which field needs attention and provide the account reference connected to it. We may verify ownership first, then assess the request against the Privacy Policy and applicable local requirements.

Necessary cookies may keep login settings and required session functions available as you move from your mobile browser into the lobby. The Privacy Policy explains their purpose. Browser controls can manage non-essential choices, while deleting cookies may require you to sign in again.

Use the support contact route displayed on bnn288 and label your message as a Privacy Policy request. Include your account reference, describe the question and avoid sending wallet passwords. We use an ownership check before discussing personal data or transaction records.