Reference

borneojitu Privacy Policy For Your Account

borneojitu Privacy Policy explains how we handle your account details, wallet records and device signals from the first phone verification step.

Account clarityWallet recordsCookie choicesPrivacy requests
borneojitu borneojitu Privacy Policy For Your Account
PRIVACY HELP PATHS

Privacy Help For Login And Wallet Records

A clear support route helps you resolve a privacy question without repeating account details across several places. Start from the account help path connected to your login or cashier record, then describe the specific request, such as a data copy, correction or cookie concern. We use the existing account trail to identify the right record and keep the request focused.

Team online

Login record request

If you need to know which account details we hold, use the account help path after login and state whether you want access, correction or deletion considered. We may ask for a verification step before replying.

Wallet status question

For a DANA, OVO, GoPay or QRIS receipt concern, include the transaction reference and wallet name. We use that detail to separate payment reconciliation from unrelated profile records before handling your privacy request.

Cookie concern

When a browser cookie affects your account session, tell us the device and browser path you used. We can explain the cookie purpose and suggest a setting change without asking for your wallet password.

DATA HANDLING PRACTICE

How borneojitu Handles Device And Account Data

Privacy becomes easier to judge when each record has a defined reason for collection and a clear request path.

Account setup

During account opening, we use the phone number and verification result needed to connect you with the correct account. A clear verification step helps prevent another person from requesting or changing your records.

Device signals

We may record device type, browser version and connection markers when you sign in. These signals help us notice unusual access patterns; they are not treated as a replacement for your account credentials.

Cookie controls

Cookies can keep a session open, remember selected settings or support security checks. You can manage them through your browser settings, although removing necessary cookies may interrupt the login path or require verification again.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a receipt with your account ledger. We do not need your wallet password to check whether a reference reached the correct record.

Retention timing

We retain records only for the operational, security or legal purpose described in the Privacy Policy. When a purpose ends, eligible data can be removed, anonymised or kept only where a rule requires continued retention.

Change requests

You can ask us to access, correct or remove eligible personal records through the account support path. Include the account phone number and request type, and we may verify ownership before making a change.

Privacy Policy Questions About Your Account

These answers address the Privacy Policy searches we expect before an Indonesian account is opened. They explain what we collect, why wallet and device records appear, how cookies affect login, and which details help us handle a request. If your situation is different, use the account support path with the smallest amount of personal detail needed.

It covers account details, phone verification, device signals, cookies, wallet references, support records, security events and retention. It also explains how you can request access, correction or removal where local law permits.

Phone verification connects you to the correct account and helps prevent an unverified person from requesting changes. We use the result for account access and security checks, subject to the Privacy Policy.

No. We use transaction references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account to reconcile a receipt. Wallet passwords are not needed for that account record check.

We may receive device type, browser version, connection markers and security events linked to sign-in. These details help identify unusual account access and are handled under the retention rules in the Privacy Policy.

Cookies can support a login session, selected settings and security checks. You can adjust browser cookie settings, but removing necessary cookies may sign you out or require phone verification again.

Yes, where local law permits. Use the account support path, name the record you want copied or corrected, and provide the account phone number. We may verify ownership before releasing or changing data.

Retention depends on the record's operational, security or legal purpose. The Privacy Policy allows removal or anonymisation when that purpose ends, unless applicable rules require the record to remain available.