Reference

bandotraja Privacy Policy for Your Account

Clear data choices start with a readable Privacy Policy. bandotraja explains why we collect account, device, cookie and wallet records, how long we retain them, and how you…

Account dataCookie choicesWallet recordsAccess requests
bandotraja bandotraja Privacy Policy for Your Account
CONTACT ROUTE

Check Privacy Requests Through Support

A clear support path helps when your account record or wallet reference needs attention. Use the support form linked from account help and describe the request in plain English, such as access, correction, deletion or cookie preferences. Include your account contact detail and the relevant DANA, OVO, GoPay or QRIS receipt reference when a payment record is involved. We use those details to locate the correct record without asking you to send a password.

Team online

Account help

Open the account help support form for a Privacy Policy request. We use your account contact detail to match the request and do not ask you to share your password.

Wallet records

For DANA, OVO, GoPay or QRIS questions, add the receipt reference and approximate request date. This helps us separate a wallet record from another account without exposing unnecessary data.

Access checks

We may ask for a reasonable account check before releasing personal data. Phone verification status and the account email or phone path help us send records to the right person.

SECURITY DETAIL

Explore Security And Retention Details

We handle Privacy Policy requests as account matters, not as public chat topics. Our process separates identity checks, device signals, cookie settings and wallet references so each record is considered for its…

Account collection

We collect the details needed for account creation, including your contact route and phone verification status. We use them to manage access, respond to requests and connect records to the correct account.

Cookie controls

Cookies can retain page preferences and help keep an account session consistent. Your request can ask about cookie categories or seek a change where that choice is available under local law.

Mobile device path

A mobile browser may provide device and session signals used for security checks. Those signals help identify unusual sign-in behaviour and are considered separately from your wallet receipt details.

Phone verification

Phone verification comes before account access in the account path. We use its status to support identity checks, protect requests for personal data and reduce the chance of sending records to the wrong person.

Retention choices

Retention varies by record type, including account, cookie, security and payment references. We remove or restrict eligible records when a valid request applies and where local law permits that action.

Request handling

Send access, correction or removal requests through account help. We may confirm ownership, clarify the scope and explain any legal reason that limits a requested change.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the questions you may have before opening an account. We cover wallet references, mobile browsing, cookies, identity checks, retention and contact steps. If a request involves eligibility or access, the outcome depends on local law, and our support route can explain which account details are needed.

It covers account details, phone verification, sign-in and device signals, cookies, wallet references, security records, retention and requests for access, correction or removal where local law permits.

DANA and QRIS references help us match a receipt or wallet status with the correct account request. We use those records for support, account checks, security review and applicable legal needs.

Yes. The Privacy Policy applies when you use the mobile browser path. Session and device signals may support security checks, while the normal login and phone verification steps protect account access.

Use the support form connected to account help and ask for data access. Add your account contact route, then complete any reasonable ownership check before we prepare the eligible records.

Yes, you can request a correction through account help. Tell us which detail is inaccurate and provide the updated value; we may confirm ownership before changing the account record.

There is no single period for every record. Account, cookie, security and payment references follow different operational or legal needs, and eligible removal depends on local law and the request scope.

Start with the support form linked from account help. Describe the Privacy Policy concern, include the relevant account contact route and avoid sending passwords or unnecessary payment credentials.