Reference

rajabandot Privacy Policy For Your Account

Your account details, wallet records and device choices receive clear treatment under the rajabandot Privacy Policy.

DANA AND QRISPHONE VERIFICATIONCOOKIE CHOICESLOCAL LAW CHECK
rajabandot rajabandot Privacy Policy For Your Account
REQUEST HELP CLEARLY

Three Ways To Ask About Your Privacy

A privacy question should not get lost beside a wallet issue. Our support path is arranged around the account area, so you can identify the login, phone number or payment reference connected with your request. Tell us whether you need access, correction, deletion or a clearer explanation, and we will check the relevant record before replying. If you are in Denpasar, the same digital request path applies where local law permits.

Team online

Account access request

Ask us for the personal data connected with your account after completing the account identification step. We may check your verified phone before releasing details to the correct person.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate date. We use those details to locate a status record without asking you to send your full wallet credentials.

Correction or removal

Tell us which account detail needs changing or which eligible record you want removed. We assess the request against account operation, security needs and any retention duty that still applies.

SIX DATA PROMISES

What Our Privacy Process Covers

Privacy works through small account actions rather than a single setting. We separate login details from payment references, use verification before account access, and keep cookie choices tied…

Data collection

We may collect your name or contact detail supplied during account creation, verified phone data, login events, device signals and…

Cookie controls

Cookies can keep your session active and remember selected settings on your browser.

Account security

Phone verification helps connect access requests with the account holder.

Payment separation

We use payment references and status results to match a cashier event, but we do not ask you to disclose…

Retention choices

We keep records only for the stated account, support, reconciliation or legal purpose, subject to the period that applies.

Contact route

Use the account support path for access, correction, deletion or policy questions.

Privacy Policy Answers Before Account Opening

These answers address the searches we hear before an account is opened or a wallet is connected. They focus on rajabandot data handling, account access, cookies, payment records and requests you can make under the Privacy Policy. If your situation is not covered, use the support route with only the details needed to locate your record.

It covers account details, phone verification, device and cookie signals, payment references, support requests, retention and your choices about access, correction or removal, where local law permits.

We use phone verification to connect account access and privacy requests with the correct account holder. It can also help us review unusual login activity before sensitive details are changed.

Yes. We may store payment references, timestamps and status results for DANA and QRIS, as well as OVO, GoPay, bank transfer or virtual account activity used to match your account.

Use the account support path and ask for an access request. Include the account detail needed to locate your record; we may complete an identity check before sharing personal data.

You can request correction or removal of eligible data through support. We assess the request against account operation, payment reconciliation, security needs and any legal retention requirement.

Required cookies can maintain your login session, while other cookies may remember browser settings. Clearing cookies may sign you out or remove saved choices from that device.

Open the account support route and state whether your question concerns access, correction, deletion, cookies or a wallet record. Do not include your password, wallet PIN or verification code.