Reference

depowin Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record controlsAccount access rights

Explore Our Lobby Read FAQ

How Payment Records Fit This Privacy Policy

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

Your payment records help us match an account action with the wallet or bank route you selected. When you choose DANA, OVO, GoPay or QRIS, we may record the payment reference, amount, time, status and account identifier needed to confirm the transaction. Bank transfer and virtual

1
account entries can include the receiving bank route, such as BCA, BRI, Mandiri or BNI, together with a reference supplied by the payment process. We do not ask for your wallet password or banking PIN through our account form. We use these records to resolve an
2
unmatched status, check an account request, prevent duplicate processing and answer a receipt question. Storage periods depend on operational, legal and dispute needs. Access to the service depends on local law, and we update this notice when the handling purpose or available account controls changes.

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

PRIVACY SUPPORT

Where To Ask About Your Account Data

A privacy question should reach a clear account path, especially when a wallet status or login detail is involved.

Account contact Use the support contact connected to your account for a Privacy Policy question, correction request or concern about sign-in records. We may ask for account details to confirm the request belongs to you.

Wallet receipt check If DANA, OVO, GoPay or QRIS shows a pending status, send the payment reference rather than a wallet password. We can compare the receipt record with the account event and explain the next step.

Access assistance When your privacy request follows a login problem, tell us whether you used a mobile browser or desktop path. This helps us separate device data, account data and the specific access issue.

DATA CONTROL POINTS

What We Do With Data At depowin

We keep this policy practical by linking each data category to an account action you can recognise.

Account details

We use your registered contact and verification details to create the correct account record, confirm an access request and send a reply about your Privacy Policy request. Keep your phone details current.

Device and cookies

A mobile browser or desktop session may create device and cookie records that keep login steps working and help us diagnose a failed page. Your browser settings provide controls for cookie storage.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account routes help us match a cashier event to your account without requesting your wallet PIN.

Account protection

We use sign-in checks, phone verification before account access and request validation to reduce mistaken changes. Never place a password, one-time code or banking PIN inside a support message.

Retention periods

We retain records only for the operational, dispute, safety or legal purpose that applies to them. When a period ends, the record is deleted, anonymised or restricted where appropriate.

Change requests

Ask us to correct account data, explain a processing purpose or remove eligible details through the account support contact. Include your registered phone number so we can verify ownership.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account actions you are most likely to search for before opening access. They cover wallet records, cookies, device sessions, correction requests and local eligibility. If your question concerns a particular payment reference or sign-in event, include that detail when contacting us.

It covers account details, phone verification, device sessions, cookies, payment references and support requests connected with your use of depowin. Access and processing apply where local law permits.

No. We use transaction references and status details needed to match DANA or OVO activity with your account. Do not send a wallet password, banking PIN or one-time code to support.

Phone verification helps us connect an access request with the correct account and reduce mistaken changes. The Privacy Policy explains this use, while eligibility and access depend on local law.

We may keep the QRIS or GoPay reference, status, amount, time and account identifier needed for matching, receipt checks and dispute handling. We do not need your wallet login credentials.

Yes. Contact the account support path with your registered phone number and a clear request. After ownership checks, we can explain held data and process eligible corrections under the Privacy Policy.

Cookies and device records can preserve session steps and help diagnose sign-in errors. Your browser settings can restrict storage, though some account functions may not work correctly after that change.

Retention depends on the record’s purpose, including account operation, payment disputes, safety checks and legal duties. When the applicable period ends, we delete, anonymise or restrict the record.

depowin Privacy Policy For Your Account

Where To Ask About Your Account Data

What We Do With Data At depowin

Account details

Device and cookies

Wallet matching

Account protection

Retention periods

Change requests

Privacy Policy Answers For Indonesian Accounts

01 What does the depowin Privacy Policy cover?

02 Does the Privacy Policy store my DANA or OVO password?

03 Why does depowin need phone verification before access?

04 How are QRIS and GoPay records handled?

05 Can I request a copy or correction of my account data?

06 How do cookies affect my mobile or desktop access?

07 How long does depowin keep payment and account records?

Related Pages