Reference

dewacoin99 Privacy Policy For Your Account

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

Account dataCookie choicesWallet recordsSecurity steps
dewacoin99 dewacoin99 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Questions Through Your Account

A privacy request should include enough detail for us to locate the correct account without exposing another person’s records.

Account privacy request Sign in through the same phone or desktop path you normally use, then send an account-data request from the available support route. We use your account details to confirm identity before discussing records.
Wallet record check For a DANA, OVO, GoPay or QRIS query, include the date, amount reference and wallet name shown in your account history. This helps us separate a payment record from unrelated account activity.
Security concern If you see an unfamiliar sign-in or device, tell us which account step was affected and stop sharing verification codes. We can review the session trail and explain the next account-security action.
HANDLING PRACTICES

How We Apply This Privacy Policy

We apply this Privacy Policy to practical account events rather than treating every visit alike.

Data we collect

We collect account details you submit, verification responses, support messages and technical session signals. When you use Bank Transfer BCA or another listed rail, we also receive the reference needed to match the account event.

Cookies and sessions

Cookies help keep your sign-in session working and show whether a browser has returned. You can manage browser cookie settings, but blocking essential cookies may interrupt the path from account login to the lobby.

Account security

We compare sign-in signals such as device and session activity with account actions. A new phone, an unusual browser or a change to verification details may trigger an extra check before we allow the requested account change.

Retention period

We retain account, support and transaction references while they are needed for account operation, dispute handling, security checks or legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Correction request

If your contact detail or account record is inaccurate, ask us to correct it through the account support route. Include the affected field and the reason for the change so we can compare it with verification records.

Deletion request

You may ask whether your personal data can be removed or restricted. We first check open account, payment or security obligations, explain any record we must retain, and process eligible removal where local law permits.

Privacy Policy Questions About dewacoin99

These Privacy Policy answers address the questions we expect before an Indonesian account is opened or updated. They explain the data connected with login, wallet references, cookies, device changes and personal requests. If your case involves a particular account event, include its date and reference through the support path so we can apply the policy to the right record.

It covers account details, verification responses, device and browser signals, cookies, support messages and transaction references. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use the reference needed to match the event with your account.

We use device type, browser signals, session time and related technical records to keep sign-in activity understandable and identify unusual account changes. A phone session and a desktop session may create different records without changing the personal details you submitted.

Sign in through your usual account path and send the request through the available support route connected to your account. State that you want a copy of your personal data, include the account contact detail, and complete any identity check we request.

Yes. Send a correction request through the account support route and identify the field that is wrong, such as a contact detail or verification response. We compare the request with account records before making a change, and we may ask for proof.

The Privacy Policy treats DANA and QRIS references as transaction data linked to an account event. We use the reference, date and status to match the record or investigate a query; we do not need your wallet password to perform that check.

Retention depends on why the record exists. Account, support and transaction references may remain while needed for account operation, security checks, disputes or legal duties. When those needs end, the record follows our applicable removal or retention process.

You can ask us to assess deletion or restriction of your personal data through the account support route. We check for open payment, security or legal duties first, explain anything that must remain, and handle eligible requests where local law permits.