Reference

dewagaruda Privacy Policy For Your Account Data

Your dewagaruda Privacy Policy explains what we collect when you open an account, verify your phone and move between the lobby and cashier.

Account clarityPayment recordsCookie choicesPhone verification

Explore Our Lobby Read FAQ

How Your Wallet Data Is Recorded

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

Our Privacy Policy applies from the first account step through sign-in, phone verification and any request involving DANA, OVO, GoPay, QRIS, virtual account or bank transfer. We record the payment reference, amount, account identifier and status needed to match a cashier action with your account; we

1
do not need your wallet password. A BCA, BRI, Mandiri or BNI transfer can also create bank and reference details for reconciliation. Device signals, login time and security events help us investigate unusual access. We use the data for account operation, payment checks, security and legal
2
duties. Where local law permits, you can ask about stored data or request a correction through support. Access and eligibility depends on local law, and this policy applies to the service only within those boundaries.

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

HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should not leave you guessing. Use the support path beside account access or the cashier when you need to ask what a record…

YOUR DATA CONTROLS

What We Do With Account And Device Data

We keep the Privacy Policy practical: each data category has a reason linked to account access, payment matching, security or legal duties.

Account details

When you open an account, we use the details you provide to create the profile, support phone verification and connect your account with relevant access records. We do not ask you to place a wallet PIN or bank password in the profile.

Payment matching

A DANA, OVO, GoPay or QRIS transaction can produce a reference, status and time record. We use those fields to match a cashier event, investigate a receipt question and reduce confusion between your account and another payment.

Cookies and sessions

Cookies and session signals help remember sign-in state, protect an active session and understand whether a request came from a mobile browser or desktop device. You can manage browser cookie controls, although some account functions may then need another sign-in.

Security checks

We may assess login time, device signals, phone verification status and unusual account activity to protect access. These checks are not a request for your wallet credentials. If a check interrupts you, use the account support route for clarification.

Retention period

We retain account, payment and security records for the period needed to provide the requested service, resolve disputes, protect access or meet applicable legal duties. When a record is no longer needed for those purposes, our process addresses its removal.

Your request path

You may ask what personal data we hold, request a correction or ask about removal where local law permits. Send the request through support with your registered contact and account reference; we may verify ownership before replying or changing records.

Privacy Policy Answers For dewagaruda

These Privacy Policy answers cover the account steps you are most likely to question before opening an account. We explain how payment references, cookies, device signals and phone verification fit together, plus how to contact us about your records. If a local requirement affects access, eligibility depends on local law.

The dewagaruda Privacy Policy covers personal data collected during account creation, phone verification, sign-in, cashier activity, support requests and device sessions. It explains our purposes for using those records, how long we retain them and how you can ask about access, correction or removal.

Phone verification helps connect an account request to the person controlling the registered contact and supports account recovery or security checks. We may use the verification status when you sign in or request a privacy change, but you should never send us a one-time code.

Yes. The Privacy Policy covers payment references, status, time and account links created when you choose DANA, OVO, GoPay or QRIS. We use these details to match a cashier event and investigate a receipt, not to request your wallet password or banking login.

A mobile browser or desktop session can provide device, browser, login-time and security signals. We use them to maintain session access, detect unusual account activity and understand why a sign-in failed. The exact signals can vary by device settings and browser controls.

Use the account support route and state whether you want access to your records or a correction. Include your registered contact and account reference, while leaving out passwords, wallet PINs and banking credentials. We may verify ownership before responding, where local law permits.

You can submit a deletion request through support, and we will assess it against service, security, dispute and legal-retention needs. Where local law permits, records no longer needed for those purposes can be addressed through our retention process after account ownership is checked.

Start with the support link beside account access or the cashier and label your request as a Privacy Policy question. Provide your registered contact, account reference and the record date involved. We will use that context to identify the request without asking for sensitive credentials.

dewagaruda Privacy Policy For Your Account Data

Get Clear Answers About Your Data

What We Do With Account And Device Data

Account details

Payment matching

Cookies and sessions

Security checks

Retention period

Your request path

Privacy Policy Answers For dewagaruda

01 What does the dewagaruda Privacy Policy cover?

02 Why does dewagaruda need phone verification?

03 Does the Privacy Policy cover DANA, OVO, GoPay and QRIS data?

04 What device data does dewagaruda collect?

05 How can I request a copy or correction of my data?

06 Can I ask dewagaruda to delete my personal data?

07 Where local law permits, how do I contact dewagaruda about privacy?

Related Pages