Reference

Privacy Policy for Your ata4d Account

Our Privacy Policy explains what ata4d collects when you open an account, browse Dragon Tiger or use DANA, OVO, GoPay and QRIS.

Account dataWallet referencesCookie choicesAccess requests
ata4d Privacy Policy for Your ata4d Account
CONTACT ROUTES

Get Privacy Help Near Account Support

A clear contact path helps when a privacy request and a wallet status question arrive together.

Data request Ask us to confirm the account details we hold, explain their use or provide a copy where the request can be verified. Include your registered phone detail and the subject Privacy Policy so our team can route it correctly.
Correction path If your name, phone detail or account record needs changing, send the requested correction through the account support path. We may ask for an account step or phone verification before changing a record tied to DANA, OVO, GoPay or QRIS.
Access concern When a sign-in or device change raises a privacy concern, tell us which device path you used and when the issue appeared. We can check account security records without asking you to disclose a password, PIN or wallet login.
DATA PRACTICE

Know What ata4d Keeps And Why

We keep this policy practical: each data category has a reason connected to account access, payment matching, security or support.

Account creation

When you open an account, we collect the contact details and verification result needed to create and protect that account. We use the registered phone detail to connect the correct profile and reduce confusion when you return from another device.

Payment references

DANA, OVO, GoPay and QRIS may provide transaction references and status, not your wallet password. Bank transfer and virtual account records help us match a payment to the right account while keeping the payment trail separate from private login credentials.

Cookies

Cookies can keep a session active, remember a page choice and support security checks. You can adjust browser cookie controls, but restricting essential cookies may interrupt sign-in or send you back to the phone verification step.

Device security

We may record browser type, device signals, session times and failed access attempts to identify unusual account activity. These records help us investigate a sign-in concern without reading unrelated files on your phone, tablet or computer.

Retention period

We retain account, payment and support records for as long as needed for the stated purpose, account protection, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we assess it for deletion or removal of identifying detail.

Request changes

You can ask for access, correction or deletion through the support route connected to your account. We verify the request before acting, explain any record that must remain, and tell you what further step is needed where local law permits.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the searches we hear most often before an account is opened. We explain the practical path for account records, wallet references, cookies, device security and requests from Indonesia. If your situation is unusual, use the support route in your account area and include enough detail for us to locate the correct record. Any access or eligibility question depends on local law.

The ata4d Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security and how to request access or correction.

Phone verification connects you to the correct account and helps us identify an unusual sign-in or account change. It is also a practical way to route a privacy request safely. We do not ask you to share a wallet PIN or password through support.

No. The Privacy Policy describes payment references and status used to match a DANA or QRIS transaction, not your wallet password. OVO, GoPay, bank transfer and virtual account records follow the same payment-matching purpose, with account security handled separately.

Use the support path shown in your account area and ask for an account data request under the Privacy Policy. Include your registered phone detail, explain the record you want, and complete any identity check we request before we release account-specific details.

Yes, you can request a correction or removal through the account support path. We first confirm that you control the account, then check whether the record is still needed for security, payment matching, dispute handling or a legal requirement before taking action.

Essential cookies help maintain your session and support security checks as you move between account pages. Browser controls can restrict them, but sign-in may stop working or return you to phone verification. Non-essential cookie choices can be adjusted in your browser.

Access and eligibility depends on local law. The Privacy Policy applies to account and device records when you use the service where local law permits. If you are unsure, check the rules applying to your location before opening an account or sending payment details.