Reference

Privacy Policy for rajabandit Account Data

Our Privacy Policy shows how rajabandit handles the data attached to your account, wallet activity and support requests.

Account clarityWallet data contextCookie choicesPhone verification
rajabandit Privacy Policy for rajabandit Account Data
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact path helps you ask what data we hold, why it is used or how a correction request should be made.

Account privacy request Use the account support path to ask about your stored profile data, phone verification…
Wallet record question For a DANA, OVO, GoPay or QRIS question, send the transaction reference rather than…
Correction request Tell us which account field appears wrong and what you want changed.
DATA PRACTICES

How We Handle Your Privacy Choices

Privacy work is tied to practical account steps rather than broad statements. We separate sign-in data from payment references where our operating records allow, use device signals to…

Account data

We use the details you provide during account creation to establish your profile, confirm the phone step and manage sign-in.

Cookies and sessions

Cookies can remember a sign-in session, language setting or security preference on the device you use.

Device security

A phone, browser and connection can produce technical signals such as device type, session time and unusual sign-in patterns.

Wallet records

Payment references help us match a DANA, OVO, GoPay or QRIS action with the correct account.

Retention timing

We retain account, security and payment records only for the period needed for account administration, reconciliation, dispute handling and legal…

Changes and contact

You can ask us to access, correct or explain personal data linked to your account through the support route.

Answers About Privacy Policy Access

These Privacy Policy answers address the searches we expect from an Indonesian account holder before opening an account or asking for a data change. They cover collection, cookies, wallet references, device signals, deletion and contact steps. If your situation is not covered, use the support path beside your account and describe the specific record or request. Access depends on local law, and we will apply the policy wording relevant to your account and location where local law permits.

It covers account details, phone verification, sign-in events, cookies, device signals, support requests and payment references. It also explains retention, security checks and how to request access or correction. The policy applies to account activity connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account records.

We use your phone number for account creation, verification and safer responses to privacy requests. A confirmed phone detail helps us distinguish the account holder from another person asking about your data. We may request that same verification step before discussing account records or changing profile details.

Yes. It explains cookies used for session continuity, language settings and security preferences when you browse from a phone or desktop. Blocking or clearing cookies can sign you out and trigger another verification step. Your browser also provides controls for some cookie choices and storage behaviour.

We may store a payment reference, account link, status and reconciliation details for DANA or QRIS activity. Similar records can apply to OVO, GoPay, bank transfer and virtual account steps. We do not ask you to send wallet passwords or one-time security codes in a privacy request.

Yes. Send a clear correction request through the account support route and identify the field that appears wrong. We may verify control of the account using the phone detail already attached to it. We will explain the outcome or any legal or operational reason a change cannot be completed.

The policy does not treat every record the same. Account, security and payment data can remain while needed for account administration, reconciliation, disputes or legal duties. When those purposes end, our process considers deletion or removal of direct links, subject to retention duties where local law permits.

You can request access to personal data linked to your account through the support path. State the account phone detail and the type of record you want clarified, such as sign-in history or a QRIS reference. We may verify account ownership before sharing data and will explain any applicable restriction.