Reference

dewavegas Privacy Policy For Your Account

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

Account dataCookie choicesWallet recordsAccess requests

Browse Our Lobby Read FAQ

How Wallet And Login Data Is Used

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

Our Privacy Policy covers data you provide during account opening, including contact details and the phone verification step before access. We also record sign-in events, device type, browser settings, support messages and activity needed to keep your account connected to the right wallet record. When you

1
use DANA, OVO, GoPay, QRIS, a virtual account or bank transfer, we may retain transaction references, status results and confirmation details rather than private wallet credentials. These records help us trace a pending payment or answer a receipt question. We use cookies and similar tools for
2
session continuity, preferences and security checks. Access and eligibility depends on local law, and our policy applies where local law permits. You can ask us what data is held, why it is used, how long it is kept, or how to request a correction through the
3
support path linked to your account.

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

HELP WITH PRIVACY

Where To Ask About Your Personal Data

A privacy question should not leave you searching through the lobby. From your account support area, you can send a request about a phone verification record, a DANA or QRIS receipt, a…

Account support path Open the support route from your signed-in account and describe the Privacy Policy request. We use account details to match the request with the correct record.

Wallet record query For DANA, OVO, GoPay or QRIS questions, include the transaction reference and status shown in your account. Do not send a wallet password or private security code.

Access correction If your phone, email or device record looks wrong, tell us which field needs attention. We may ask for an account step before making a change.

HANDLING YOUR DATA

Cookies, Devices And Account Records

We keep the Privacy Policy practical by separating account identity, payment references and device signals.

Account opening

We use the details entered during account creation and the required phone verification to establish account ownership. This helps us direct privacy requests to the right account.

Mobile sessions

When you sign in on a phone, we may store session and device signals so the account remains connected during the move from login to the lobby.

Cookie controls

Cookies can remember session preferences and support security checks. Your browser settings can restrict them, although some account functions may then require another sign-in.

Wallet matching

DANA, OVO, GoPay and QRIS references help us match a payment status with your account. We do not ask you to share a wallet password in a support request.

Retention choices

We retain records for the stated account, payment, security and legal purposes. You may ask us to explain a retention period or assess a removal request.

Request handling

To protect your data, we may verify account ownership before releasing a copy or changing details. Send requests through the signed-in support route linked to your account.

Privacy Policy Questions About dewavegas

These Privacy Policy answers cover the account steps most relevant to Indonesian customers. They explain the data connected to sign-in, mobile sessions, cookies and local wallet records, plus the route to ask for access or a correction. If your situation is not listed, use the support path inside your account and include the relevant reference.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, virtual account and bank transfer.

We use the phone verification step to help confirm account ownership before access and before discussing private records. It also helps us direct a Privacy Policy request to the correct account.

No. Our policy concerns transaction references, status results and confirmation details connected with your account. Do not include a wallet password, security code or private credential in a support request.

Sign in, open the account support route and ask for a copy of the personal data linked to your account. We may verify ownership before releasing records, where local law permits.

Yes. Use the signed-in support path, identify the phone, email or other field that needs correction, and explain the change. We may request an account step before updating it.

Cookies can keep a mobile or desktop session active, remember preferences and support security checks. You can restrict them through browser controls, but account access may then require another sign-in.

Retention depends on the purpose, such as account access, payment tracing, security or legal duties. Ask through account support for the period applying to a particular record or request.

dewavegas Privacy Policy For Your Account

Where To Ask About Your Personal Data

Cookies, Devices And Account Records

Account opening

Mobile sessions

Cookie controls

Wallet matching

Retention choices

Request handling

Privacy Policy Questions About dewavegas

01 What does the dewavegas Privacy Policy cover?

02 Why does dewavegas need my phone verification data?

03 Does the Privacy Policy store my DANA or QRIS password?

04 How can I request my data from dewavegas?

05 Can I ask dewavegas to correct account data?

06 How do cookies affect my Privacy Policy choices?

07 How long does dewavegas keep my account records?

Related Pages