Reference

daya138 Privacy Policy For Your Account

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

Clear data purposesWallet record contextAccount request pathIndonesia access terms
daya138 daya138 Privacy Policy For Your Account
CONTACT PATHS

Reach Support About Privacy Questions

A direct privacy question deserves a clear account path, especially when a wallet reference or phone check is involved.

Account privacy request Use the support contact path from your signed-in account to ask what personal data we hold, why it is used, or which account step created the record.
Wallet record question If DANA, OVO, GoPay or QRIS appears in a privacy question, share the visible reference and date rather than sending an entire wallet statement.
Access correction Tell us which phone, device or account detail needs correction. We may verify your account before changing the record so another person cannot alter it.
DATA HANDLING

Explore How Your Privacy Works

We keep this policy practical by linking each data category to an account action. A phone number supports verification, a device signal helps protect sign-in, and a payment reference helps trace a…

Account details

We use the details you enter during account opening to create your profile, send account notices and complete the phone verification step before access is provided.

Device signals

When you sign in on a mobile browser or desktop, we may record device and session signals to identify unusual access and help protect your account.

Cookie choices

Cookies can remember a session and selected settings. You can manage cookie controls in your browser, though removing them may require you to sign in again.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match account activity with a status question without treating them as public details.

Retention approach

We retain records only for the operational, security, dispute or legal purpose that requires them, then remove or restrict them when that purpose no longer applies.

Request handling

To request access, correction or deletion, contact support through your account path. We may ask for verification and will explain any lawful reason a request cannot be completed.

Browse Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account records, cookies, device access, local payment references and requests sent to our support path. If your situation is different, contact us with the smallest useful set of details.

The daya138 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, payment references, support messages, retention and requests to access or correct your data.

We use your phone number to create and protect your account, complete the phone verification step and help locate your record when you ask support about access or correction.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references may be used to match an account status question, while you should send only the needed reference.

Cookies can keep a sign-in session and selected settings available on your browser. You can change cookie controls in the browser settings, but removing them may require another account sign-in.

You can contact support through your signed-in account and request access to the personal data connected to your profile. We may verify your identity before sharing account records.

State which account, phone, device or payment reference is incorrect through the support path. Include the relevant date or visible reference, and we will check the request before making a change.

Access depends on local law. The Privacy Policy describes our data handling, but you remain responsible for checking whether account access is permitted in your location and circumstances.