Reference

djrum4d Privacy Policy For Your Account Data

Our djrum4d Privacy Policy shows what we collect when you open an account, sign in from mobile, or use DANA and QRIS.

Clear data choicesWallet records explainedMobile access detail

What Payment Data We Receive

djrum4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers data supplied during account creation, including your contact details, phone verification status and records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those records to match transactions, investigate a payment receipt and keep the correct account

1
accessible from your device. We may also receive technical details such as browser type, session time and approximate location signals. If you browse from Bandung or elsewhere in Indonesia, those signals help us protect sign-in sessions rather than identify your exact address. Access or eligibility depends
2
on local law, and our policy applies only to data handled through our own account and support paths. The payment chips below identify the wallet references covered by this policy.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where To Ask About Your Data

You can raise a privacy question through the support path shown after account access, especially when a wallet receipt or login record needs checking.

ACCOUNT SAFETY

Six Controls For Your Account Data

Our handling process is built around limited collection, account security and clear requests. We separate operational records from support conversations where practical, check access before making changes, and use the same Privacy…

Data use

We use contact, verification and transaction data to provide account access, match wallet activity and respond to support requests. We do not need unrelated details to process a DANA receipt.

Cookie choices

Cookies and similar device storage help preserve sign-in state and measure page errors. You can adjust browser settings, although blocking them may interrupt the mobile path to the lobby.

Sign-in checks

Phone verification and session signals help us recognise an account request. Never send your password or one-time code to support; we use account checks instead.

Retention period

We retain account, payment and support records only for the period needed for account operations, dispute handling, security checks and legal duties that apply where local law permits.

Correction requests

If your phone number or account detail is wrong, ask support to correct it. We may request an account step or matching receipt before changing stored data.

Deletion requests

You can ask how to remove eligible data through the policy contact route. Some transaction or security records may remain while a valid operational or legal need exists.

Privacy Policy Questions For djrum4d

These answers address the questions we expect before an Indonesian customer opens an account. Each response points back to the data process, payment record or access step covered by our Privacy Policy, so you can decide what to share before using a phone or desktop browser.

It covers data collected during account creation, phone verification, sign-in, wallet activity and support contact. It also explains cookies, device signals, retention and requests to correct or remove eligible data.

Yes. We may handle DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account records, to match payment status and investigate a receipt linked to your account.

Phone verification helps connect an account request with the correct contact detail and reduce unauthorised sign-in attempts. We record the verification status, not a request for your private one-time code.

You can contact support through the route connected to this Privacy Policy and ask which data is held for your account. We may check account ownership before responding to the request.

Send a correction request through support and identify the affected account detail, such as a phone number. We may ask for a matching account step or payment reference before updating it.

Retention depends on the purpose of each record, including account operation, receipt checks, security and legal duties. The Privacy Policy contact route can explain the reason for a specific record.

It applies to data handled through our account and support paths for Indonesian access where local law permits. Your eligibility to access account areas depends on local law and applicable conditions.

djrum4d Privacy Policy For Your Account Data

Where To Ask About Your Data

Six Controls For Your Account Data

Data use

Cookie choices

Sign-in checks

Retention period

Correction requests

Deletion requests

Privacy Policy Questions For djrum4d

01 What does the djrum4d Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS records?

03 Why does djrum4d need phone verification?

04 Can I request a copy of my account data?

05 How do I correct data in my Privacy Policy record?

06 How long does djrum4d keep wallet and support records?

07 Does the Privacy Policy apply to access from Indonesia?

Related Pages