Reference

daya 4d Privacy Policy Explained

Our Privacy Policy explains how daya 4d handles your account details, phone verification, device signals and wallet records when you open an account.

Account dataWallet recordsCookie choicesPhone verification
daya 4d daya 4d Privacy Policy Explained
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps when you want to check a Privacy Policy question or correct an account record.

Account support path Use the support route inside your account for Privacy Policy questions, data access requests…
Wallet record check For DANA, OVO, GoPay or QRIS questions, send the transaction reference and account contact…
Privacy request follow-up Keep the request reference we provide when you ask for deletion, restriction or clarification.
HANDLING YOUR DATA

How We Apply Privacy Controls

Privacy controls work alongside the account steps you already recognise: phone verification, login checks and payment matching.

Account data use

We use contact details and phone verification records to create your account, confirm that a request comes from you and send account-related replies. We do not treat wallet passwords as account details to collect.

Cookie settings

Cookies help keep a login session active and remember basic page choices. You can manage cookies through your browser settings, although changing them may require another login before the lobby opens.

Device signals

Our security checks may use browser type, device signals and login timing to spot unusual account access. These signals support account protection and are not a request for files stored on your phone.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match a payment instruction with your account. We check references and status details, not your wallet password or banking login.

Record retention

We keep account, support and transaction records only as long as needed for security checks, dispute handling and applicable legal duties. When a record is no longer needed, our process removes or separates it.

Change requests

Ask us to correct eligible data, explain its use or request removal through the account support path. Include your account contact and request reference; we may verify ownership before making a change.

Privacy Policy Questions Answered

These Privacy Policy answers cover the practical points you may check before opening an account or returning from a mobile browser. We keep the wording tied to account records, cookies, phone checks and local wallet references, with access available where local law permits.

It explains how we handle account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm account ownership before access and before certain data requests. We use the verified contact to respond to account matters, not to request your wallet password.

Yes. The Privacy Policy covers browser and device signals used for session continuity and account security. We do not treat that process as permission to read unrelated files stored on your phone.

We use transaction references and status details to match DANA or QRIS activity with your account. We do not need your wallet password, and you can ask support to check a receipt reference.

You can request access to eligible account data or ask for a correction through the account support path. Include your account contact and request reference so we can verify ownership.

We retain account, payment and support records for security checks, dispute handling and applicable legal duties. When those purposes end, records are removed or separated under our retention process.

Use the support link connected to your account and describe the Privacy Policy question clearly. For a wallet matter, include the DANA, OVO, GoPay or QRIS receipt reference without sharing login credentials.