Reference

dayak777 Privacy Policy For Your Account

dayak777 Privacy Policy shows what we collect when you open an account, verify your phone, sign in from a device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPhone verification
dayak777 dayak777 Privacy Policy For Your Account
HELP WITH YOUR DATA

Account Help Beside The Receipt Trail

A clear contact route helps when a privacy question and a wallet receipt meet in the same account. Start from account help beside the cashier path and include your account identifier, payment reference and device used. We can then separate a login issue from a DANA, OVO, GoPay or QRIS record without asking for your private wallet credentials.

Team online

Account access

Use the account-help route when phone verification or a sign-in check blocks your privacy request. Tell us which device you used and we will match the request to the correct account record.

Wallet status

For a DANA, OVO, GoPay or QRIS receipt question, include the reference and approximate time shown in your account. We use those details to locate the payment status without requesting your wallet PIN.

Data changes

Ask us to correct account details or explain a stored record through account help. We may ask for phone verification before making a change so another person cannot alter your privacy data.

HANDLING YOUR RECORDS

How We Keep Policy Requests Clear

Privacy work is tied to practical account events rather than vague labels. We record the minimum context needed to answer a request, protect a sign-in and trace a wallet receipt.

Account collection

We collect details you submit for account creation, phone verification and support, plus sign-in and device signals used to distinguish your session from suspicious access.

Cookie choices

Cookies can remember a session, language preference and security state. Your browser settings can remove them, although clearing required cookies may interrupt account access or verification.

Account security

We use phone verification, sign-in records and device checks to protect your account. Support will not need your wallet PIN, bank password or one-time security code.

Retention timing

We keep account, receipt and support records only as long as needed for security, dispute handling, service records or legal duties, then remove or separate them.

Correction requests

If your phone number, name or contact detail is wrong, contact account help with the correction. We verify the account first and explain any limit on changing historical records.

Policy contact

Send privacy questions through the account-help path and identify the request clearly. We may request account verification before discussing stored data or confirming a deletion request.

Privacy Questions Before Account Access

These Privacy Policy answers address the questions we expect before you open an account from Indonesia. They cover wallet references, device records, cookies, corrections and contact steps. If your situation involves a restricted region or a legal request, access depends on local law; use account help so we can assess the request against the relevant record.

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

No. We use payment references and status details to match a receipt to your account. We do not ask you to send a DANA or OVO PIN, bank password or one-time code.

Device and sign-in signals help us recognise your session, investigate unusual account access and protect phone verification. They can include device type, browser details and access timestamps.

Yes. Use account help and ask for a data copy, giving your account identifier. We verify the request before responding, and the available response depends on local law and record limits.

Contact account help with the incorrect detail and the replacement value. After phone or account verification, we can correct suitable profile data while preserving necessary receipt or security records.

You can clear cookies through your browser settings or device privacy controls. Required session cookies may be needed for sign-in and verification, so removal can interrupt access until you sign in again.

Use the account-help route beside the cashier path and label the request as privacy-related. Include your account identifier, but never include a wallet PIN or one-time security code.