Reference

borneo303 Privacy Policy For Your Account

borneo303 Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status, and why each record is…

Account recordsDevice detailsWallet statusPolicy requests
borneo303 borneo303 Privacy Policy For Your Account
CONTACT ROUTES

Where To Ask About Your Data

A clear contact route helps when you want to understand a record rather than guess from a wallet screen. We handle Privacy Policy questions through the support channel linked in your account area, and you can include the registered phone contact, relevant date, and payment reference. For a login issue, use the account help path first; never send your password or wallet PIN.

Team online

Account support route

Open the support path inside your account and describe the Privacy Policy request. Add your registered phone contact and the affected account step so we can locate the correct record.

Payment status query

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, share the reference and date only. We use those details to check status without asking for a wallet password.

Access assistance

If your phone browser cannot reach the policy page, tell us the device type, browser path, and account stage. We can separate a device issue from a data-access request.

SECURITY PRACTICE

How We Handle Account Records

We keep this Privacy Policy practical by linking each data use to an account action, such as phone verification, a wallet status check, or a request to correct details.

Collection by action

We collect account details when you open access, verify a phone contact, contact support, or request a wallet status check. The action gives us the reason for keeping that record.

Cookies and browser use

Cookies or similar browser storage can keep a session working and help us detect repeated sign-in attempts. You can manage browser storage through your phone or desktop settings.

Account security

Phone verification and sign-in checks help connect a request to the correct account. We will not ask you to disclose a password, wallet PIN, or one-time security code in a support message.

Retention decisions

We assess account, support, device, and payment-reference records by purpose. Security reviews, disputes, or legal duties may require longer storage than a routine support exchange.

Who receives details

We limit access to personnel and service partners who need a record for account support, security checks, payment reconciliation, or a lawful request. We do not treat your details as a public listing.

Changing your details

Ask us to correct an inaccurate account detail through the support route in your account. Include the old and requested new value, but leave out passwords, PINs, and full wallet credentials.

Privacy Policy Questions From Indonesia

These answers address the searches we receive about the borneo303 Privacy Policy, account access, device records, and local wallet references. If your request concerns a specific account, use the support route inside that account and provide only the details needed to identify the issue.

The Privacy Policy covers account details, phone verification, device and browser signals, support messages, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use your phone contact to connect the account opening step, verification result, and support request to one account. It can also help us investigate unusual access without requesting your wallet PIN.

Yes. The Privacy Policy includes the rail name, reference, amount status, and related timestamps supplied for a DANA or QRIS check. We do not require your DANA or QRIS password to review that status.

We may record device type, browser path, session details, and security signals linked to a sign-in or support request. These details help separate an account issue from a browser or device problem.

Use the support route shown inside your account and state which detail is inaccurate, what it should say, and why. Do not include a password, wallet PIN, or one-time security code.

Retention depends on why the record exists. We may keep account, security, support, or payment-reference data for an operational, dispute, or legal period, then remove or de-identify it when appropriate.

You can submit a data-access request through the account support channel. Include your registered phone contact and request scope; we may need to verify account control before releasing or changing records.