Reference

dewanaga77 Privacy Policy for Your Account

Your account details, DANA or QRIS status, and device session are handled under the dewanaga77 Privacy Policy.

Account dataWallet recordsDevice sessionsPolicy access
dewanaga77 dewanaga77 Privacy Policy for Your Account
CONTACT ROUTES

Where Privacy Questions Reach Our Team

A clear contact path matters when a login record, wallet reference or device entry needs explanation.

Account access If a privacy question follows phone verification or a login issue, use the account…
Wallet status For DANA, OVO, GoPay or QRIS references, share the transaction date, amount reference and…
Data request To ask for a copy, correction or removal of eligible account data, state the…
DATA PRACTICES

Account Data Controls Beside Wallet Status

We keep this policy practical by connecting each data category to an account action you recognise. Registration and phone verification create an account record; a QRIS status creates a transaction reference; returning…

Data we receive

We may receive your account contact, phone verification result, login timestamps, device signals, support messages and transaction references. These records help connect an account request with the correct activity.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, language or security checks on your device. You can adjust browser controls, though restricting them may interrupt account access.

Account security

Phone verification and session checks help us distinguish your account from an unfamiliar device. Keep your password and verification code private, and contact support if a session looks unfamiliar.

How long records stay

We retain different records for different periods based on account operation, security checks, disputes and legal duties. When a record is no longer needed, our process removes or de-identifies it.

Who handles requests

Our support team receives privacy questions through the account help route. We may ask for account-matching details before discussing records, so another person cannot request changes to your account.

Requesting a change

You can ask us to correct eligible account details, explain a data category or address a handling concern. Describe the requested change and use the contact route connected to your account.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers cover the searches we hear most often before account access. We focus on the records connected to phone verification, mobile sessions, wallet status and support requests, so you know what to prepare when contacting us.

It covers account details, phone verification, login and device signals, cookies, support messages, and transaction references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access to the correct contact and supports security checks when you return from a different device. We record the verification result, not your private authentication code.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay and QRIS. We use those records to match an account event without requesting your wallet PIN.

Use the account help route and state that you want a copy of eligible account data. Include your connected email or phone, and we may verify ownership before preparing the response.

You can ask us to correct eligible account details through support. Tell us which field is wrong and provide the accurate replacement; ownership checks may be required before the change is made.

Cookies can keep a mobile browser session active and support security checks. If you block them, login or account access may require extra steps, and some policy-related controls may not work.

You may request removal of eligible records through the account help route. Some data can remain where needed for security, disputes or legal duties, and account access depends on local law.