Reference

rajabandot99 Privacy Policy for Your Account

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

Account dataWallet recordsCookie choicesRequest access
rajabandot99 rajabandot99 Privacy Policy for Your Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact path helps you act on this Privacy Policy without guessing which team to reach. Start from the support contact shown after login and include the account detail connected to your request, but never send a wallet PIN or full payment credential. We can use a payment receipt reference, device path and account email to locate the right record. If you are in Semarang, the same request process applies, subject to local law.

Team online

Access request

Ask us for the account data linked to your rajabandot99 login. We may request an account step or verification detail before releasing records to the person who controls them.

Correction route

If your phone, email or wallet status is outdated, contact support through the signed-in account path. Tell us which field is wrong and attach only the relevant receipt reference.

Status question

For a DANA, OVO, GoPay or QRIS record, send the date and transaction reference rather than a PIN. We use those details to check the privacy and payment record together.

CONTROL AND CARE

Your Controls From Login Onward

We apply this policy through practical account controls rather than vague promises. Your sign-in step, wallet reference and device session are handled for a defined purpose, and we limit internal access to…

Account collection

At account opening, we collect the details needed to create access and confirm the contact route. A clear phone verification step may be required before your account can be used.

Wallet matching

DANA, OVO, GoPay and QRIS references help us identify payment status without asking for your wallet PIN. We use the reference to reconcile a receipt or investigate a mismatch.

Device sessions

When you move from a phone browser to a desktop browser, session and device details can help detect unusual sign-ins. Sign out on shared devices and repeat verification when prompted.

Cookie choices

Our cookies can retain a session and basic preferences. You can remove or block them in your browser settings, but doing so may send you back through the login step.

Retention period

We retain account, payment and support records only as long as needed for the stated purpose, account protection, dispute handling or a legal duty, then review whether continued storage is needed.

Change request

To request access, correction or deletion where available, contact us through the account support route. Include your contact detail and request type so we can verify and respond accurately.

Privacy Policy Questions From Indonesia

These answers focus on the Privacy Policy questions you may have before opening an account or checking a wallet record. If your situation is not covered, use the signed-in support route and describe the exact account step, device path or payment reference involved.

It covers account details, phone verification, device sessions, cookies, payment references and support records connected with your use of rajabandot99. It also explains access, correction and deletion requests.

No. Our Privacy Policy does not require you to send a DANA or QRIS PIN to support. We use a transaction reference or receipt detail to check payment status.

Phone verification helps connect the account to the contact route you provide and reduces mistaken access. We may use that record when handling a privacy request or an unusual sign-in.

Use the support contact shown after login and ask for an access request. Include the account email or phone route, but leave out wallet PINs and unrelated payment credentials.

Yes, where local law permits. Tell us which phone, email or wallet-status detail is incorrect through the account support path, and provide a verification detail so we can update the right record.

Cookies may retain your session and basic preferences when you use a mobile browser. Browser controls can remove them, but you may need to repeat login and phone verification.

Access and eligibility depend on local law. We may use location or device signals to apply that rule, while the Privacy Policy still explains the account and payment records involved.