Reference

Privacy Policy for Your dpwawasan4d Account

Our Privacy Policy explains how dpwawasan4d handles the details you provide when opening an account, signing in and checking wallet activity.

Account dataWallet recordsDevice controlsContact requests
dpwawasan4d Privacy Policy for Your dpwawasan4d Account
CONTACT ROUTES

Privacy Help Through Your Account Path

A clear contact route helps you ask about the Privacy Policy without sending private details through an unsuitable channel.

Account request Use the account support path to ask what personal details are connected to your profile. We may request a matching account step or phone-verification detail before sharing records, so your request is handled with the right account.
Wallet receipt For DANA, OVO, GoPay or QRIS questions, include the payment reference shown on your receipt. We compare that reference with the account record and status history rather than asking you to send unrelated private information.
Policy change If a detail is outdated or you want a correction request logged, contact us through the same support route. State the exact field to change and the reason, then complete any ownership check we send back.
DATA CONTROLS

Six Practical Privacy Protections

We treat the Privacy Policy as an operating process, not a page kept apart from account work.

Account details

We use your contact and phone-verification details to create and protect the account path. A clear account step helps us distinguish a genuine sign-in from an attempt using the wrong credentials, while unrelated phone content remains outside our process.

Payment references

A DANA, OVO, GoPay or QRIS reference lets us match a receipt with the correct account status. Bank transfer and virtual account records may also be used for reconciliation, but payment providers remain responsible for their own systems.

Device signals

Our mobile and desktop sessions may record browser type, session time and security signals linked to access. These details help us investigate repeated sign-in failures or an unfamiliar device without collecting unrelated files, contacts or messages.

Cookies

Cookies can keep a session connected to the page you opened and help us understand basic account navigation. You can manage browser cookie settings, although disabling some cookies may interrupt sign-in, phone verification or the cashier status path.

Retention

We retain account, security and payment-status records only as long as operational, dispute or legal needs require. When a record is no longer needed, our handling follows the removal or de-identification process available for that record type.

Correction requests

To request a correction, describe the inaccurate field through account support and provide an ownership detail. We review the request against the account record, update eligible data and tell you if a provider-held record must be changed directly.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account, device and wallet questions you are most likely to ask before opening an account. They also explain the practical route for checking records or requesting a change. If your situation is not covered, use the account support path and refer to the specific section that concerns you.

The Privacy Policy treats phone verification as an account-security step. We use its result to connect account access with the correct contact detail and investigate unusual sign-ins. We do not use it to inspect unrelated phone content, and you can ask support how the record is connected to your account.

Yes. The Privacy Policy covers payment references and status details that reach us from DANA, OVO, GoPay and QRIS. These records help match a receipt with your account step. The payment provider may hold additional records under its own terms, so provider-specific requests may need to go there.

We may use browser, session and device signals to protect account access and identify unusual attempts. The Privacy Policy does not give us a reason to read unrelated files, messages or contacts on your device. Mobile and desktop sessions can therefore have different security signals without changing your account details.

You can contact us through the account support path and specify whether you want a data copy or a correction. The Privacy Policy requires an ownership check before we discuss account records. For a correction, name the field and explain the change; provider-held payment data may require a separate request.

We keep account, security and payment-status records for as long as they are needed for account operation, dispute handling, reconciliation or legal duties. The Privacy Policy does not set one period for every record. Where local law permits, records are removed or de-identified when those needs end.

Cookies can support session continuity and basic navigation, including sign-in and the cashier status path. You can control them through your browser. The Privacy Policy explains that disabling some cookies may stop parts of the account flow from working, but it does not allow us to access unrelated device content.

Yes. Access and eligibility depend on local law. Our Privacy Policy explains how we handle data when you use an available account path from Indonesia, but it does not change legal requirements in your location. If you have an access question, contact support without sending more personal data than needed.