Reference

dewa4dku Privacy Policy For Your Account

Our dewa4dku Privacy Policy explains what account, wallet and device data we collect, why we use it, and how you can ask about it before opening an account.

Account dataWallet recordsDevice choicesPrivacy requests
dewa4dku dewa4dku Privacy Policy For Your Account
PRIVACY HELP DESK

Where To Ask About Your Privacy Policy

A clear contact path helps when you want to understand, correct or remove account data.

Account questions Ask us to explain phone verification, login records or account details held under your dewa4dku profile. We may request account identifiers so we can avoid discussing private data with the wrong person.
Wallet questions For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference rather than a full wallet password. We use the reference to trace the relevant account event.
Correction requests Tell us which personal detail needs changing and why it is inaccurate. We will check the account record, confirm the request through an appropriate account step and explain any legal reason for keeping it.
HOW DATA STAYS CLEAR

Account Security Across Mobile And Desktop

Privacy depends on practical handling, not a vague promise. We separate account access records from payment references where the workflow allows, use phone verification before account access, and consider device and browser…

Account records

We use your phone verification and account details to create access, confirm ownership and respond to account questions. If you contact us about a profile, we may ask for a matching account step before sharing details.

Payment references

DANA, OVO, GoPay and QRIS can provide transaction references or status details. Bank transfer and virtual account records may also appear, allowing us to match a payment without requesting your wallet password.

Browser cookies

Cookies can remember a session choice and help us understand whether a mobile browser or desktop browser is accessing the account. You can manage cookies through your browser settings, although some account steps may then need repeating.

Security signals

We may examine login time, device type and browser signals to identify unusual access around your account. These checks help protect private data and can prompt an additional phone verification step.

Retention period

We retain account, support and payment records only as long as needed for security, dispute handling, account administration or legal duties. When no valid need remains, we delete or separate the record.

Change requests

You can ask us to correct, access or remove eligible personal data through support. Include the relevant account step, and we will confirm what we can change, what must remain and why.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we hear before an account is opened. They explain the data connected with Indonesian wallet rails, browser access, phone verification and privacy requests. If your situation is different, contact our support route with a payment reference or account detail that does not expose your password.

It covers account details, phone verification, browser and device signals, cookies, support records and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps confirm that the person requesting account access matches the account record. It can also support a security check when a new device or unusual browser sign-in is detected.

Yes. The Privacy Policy covers QRIS references and status details linked to your account, along with DANA, OVO and GoPay records. We use these details to reconcile account activity, not wallet passwords.

Contact our support route and identify the account detail you want corrected, accessed or removed. We may verify ownership through an account step before confirming the result or any retention reason.

We keep personal data only for account security, dispute handling, administration or legal duties. Once a valid purpose ends, we delete the record or separate it from direct account identification.

Yes. It applies when you access the account from a mobile browser or desktop browser. Cookies, device type and login events may be processed to maintain sessions and identify unusual access.

Yes. Send a Privacy Policy question through support and identify the relevant account step or payment reference. We can explain the purpose, the expected retention reason and any available correction route.