Reference

darumasakti Privacy Policy For Your Account

darumasakti Privacy Policy explains what we collect when you open an account, sign in from a mobile device, use DANA or QRIS, and contact our support team.

Account dataWallet recordsDevice controlsPolicy requests
darumasakti darumasakti Privacy Policy For Your Account
CONTACT ROUTES

Reach Support About Privacy Requests

A clear contact route helps you ask about your Privacy Policy rights without sending account data to the wrong place. Use the support channel shown beside the cashier path, include your registered phone number only when requested, and keep payment receipts private. Our available support hours are displayed in that contact panel so you can choose the right time to ask about access, correction or deletion.

Team online

Account access

If phone verification or a sign-in check blocks your account, contact the on-site support channel. We use the account reference and device event needed to locate the issue, rather than asking you to send a wallet PIN or full payment password.

Wallet status

For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference through the cashier-linked support path. We compare that reference with the account record and explain what data was used for the status check.

Privacy request

To request a copy, correction or removal of eligible personal data, name the account contact method and describe the request clearly. We may ask for an account step to confirm you are requesting changes to your own records.

DATA CONTROLS

Browse How We Handle Your Records

Privacy work is part of the account path, from the first phone verification to a later wallet status question.

Account collection

When you create an account, we collect the contact details and verification result needed to open access. We do not need your DANA, OVO, GoPay or QRIS wallet PIN to match a payment reference with your account.

Cookie choices

Cookies and local storage can remember a session choice, language setting or security signal. You can manage browser storage from your device settings, although removing it may sign you out and require phone verification again.

Device activity

We record practical device and login events, such as a browser session or a phone sign-in, to identify account access that needs checking. These records support account protection and are not a request for your private device files.

Payment references

A receipt reference, amount status and selected rail may be connected to your account when you use bank transfer, virtual account or QRIS. The purpose is reconciliation and support, while wallet credentials remain outside our requested data.

Retention period

We keep account, security and support records for the time needed to operate access, resolve a payment query, address a dispute or meet a legal duty. When a record is no longer needed, our process removes or separates it.

Change requests

You can ask us to access, correct or remove eligible personal data through the support route shown on the site. We confirm the account step first, then explain the result and any reason a record must remain.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers address the account, wallet and device questions you may search before opening access from Indonesia. If your case is specific, use the support route beside the cashier and include only the details needed to locate your account.

The darumasakti Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use those records, how long they may remain, and how you can ask about access, correction or removal.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use a reference and status to reconcile an account transaction; we do not ask for your wallet PIN or private wallet password.

We collect the contact details needed for an account and the result of phone verification before access. We may also record login, browser or device events and support messages. The specific data depends on the account step you complete and the request you make.

Use the support channel shown beside the cashier path and state whether you want access or correction. Include your registered contact method, but do not send a wallet PIN. We may confirm an account step before locating records or applying a change.

You can request removal of eligible data through the support route. We first confirm the account request, then check whether a record is still needed for security, a payment dispute or a legal duty. Where local law permits, we explain the outcome clearly.

Cookies can retain a session choice, while device and login events help us identify unusual access. If you clear browser storage, you may be signed out and asked to complete phone verification again. These controls support the Privacy Policy account safeguards.

Yes, access or eligibility depends on local law. Our Privacy Policy applies to the account and data handling steps available in your region, while the support route can clarify a request. Check local requirements before opening an account or sending any personal data.