Reference

Privacy Policy for Your dewalink77 Account

Our dewalink77 Privacy Policy explains what we collect when you open an account, sign in, verify your phone and use local wallet options such as DANA, OVO, GoPay…

Account and phone recordsWallet and payment referencesCookies and device accessPrivacy request path
dewalink77 Privacy Policy for Your dewalink77 Account
PRIVACY HELP PATHS

Where to Ask About Your Account Data

A clear contact route helps you resolve a privacy question without guessing which team handles it. Start from the support link connected to your account and describe the exact record you want checked, such as a phone verification entry, a QRIS reference or a cookie setting. If you cannot sign in, include only the details needed to locate your account; never send a wallet PIN or password. We use the same path for access, correction and deletion requests.

Team online

Account support path

Use the support link after signing in and state whether your request concerns profile details, phone verification, a device sign-in or a saved preference. We can then match the request to the correct account record without asking for your wallet password.

Payment record check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the visible transaction reference and date through account support. We use that information to check the payment record while avoiding requests for private wallet credentials.

Access request route

To ask for a copy, correction or removal of personal data, identify the account phone number and the request you want handled. We may ask for account verification before changing records, so another person cannot alter your details.

DATA HANDLING DETAILS

How We Handle Cookies and Account Records

We keep this Privacy Policy practical by linking each data use to an account step you can recognise: sign-in, phone verification, wallet reconciliation, device access or support.

Data collected

We may handle your name or contact detail, phone verification result, account activity, device and sign-in signals, support messages, and payment references. We collect these details because they support account access, status checks, security review and a response to your request.

Cookie choices

Necessary cookies can keep a sign-in session and remember a selected setting. Other cookie or device signals may help us understand an access problem. You can review browser controls on your phone or desktop, although disabling necessary cookies may affect account access.

Account security

Phone verification adds an account step before access, and sign-in events can help us identify an unfamiliar device. Keep your password and wallet credentials private. If a login looks unusual, contact account support from the available support path rather than sharing secret codes.

Payment references

A DANA, OVO, GoPay or QRIS reference lets us match a payment status to your account. Bank transfer and virtual account checks may show BCA, BRI, Mandiri or BNI as the sending bank. We use these records for reconciliation, not to request your banking password.

Retention approach

We keep account, support and transaction records for as long as needed for the purpose explained here, account administration, legal duties or a dispute. When a record is no longer needed and no duty applies, we remove it or separate it from direct account identification.

Requesting changes

You can ask us to access, correct or remove personal data by using the support route connected with your account. Tell us which record is incorrect and provide the minimum account detail needed for verification. We will explain any lawful reason a request cannot be completed.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the account questions you are most likely to have before opening access from Indonesia. We have kept the examples specific, including phone verification, device cookies, local wallet references and the support path used for data requests. If your situation is different, send the details through account support and we will assess the request under the current policy and where local law permits.

It covers personal data linked to your account, phone verification, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains retention, security measures and how to request access or changes.

Phone verification helps connect the correct person to an account before access and helps us respond safely to a data request. We may use the verification result to investigate an unfamiliar sign-in or correct an account record, but you should never send us a private verification code.

No. For DANA, OVO, GoPay and QRIS, we handle the payment reference and status details needed for reconciliation. We do not need your wallet password or banking password. For a payment query, send the visible reference and date through account support instead.

Use the support route connected with your account and ask for a personal data access request. Include your account phone number and describe the records you want, such as profile details, sign-in history or payment references. We may verify your identity before releasing account-linked data.

Yes, you can request correction or removal through account support and identify the specific record. We assess the request under this Privacy Policy and where local law permits. Some records may need to remain for legal duties, account security, payment reconciliation or an unresolved dispute.

Necessary cookies can maintain a session and remember a setting when you move from phone login to the lobby. Browser controls on Android, iPhone or desktop can manage available cookie choices. If necessary cookies are disabled, sign-in or account support functions may not work as expected.

We retain records for the period needed for the purpose described here, account administration, security checks, legal duties or a dispute. DANA, QRIS, bank transfer and virtual account references may remain while reconciliation is required. You can ask support about a particular record and its status.