Reference

tata4d Privacy Policy for Your Account

Our tata4d Privacy Policy explains what account details we collect, why wallet records matter, and how you can ask for a correction or deletion.

Account clarityCookie choicesWallet recordsContact steps
tata4d tata4d Privacy Policy for Your Account
CONTACT ROUTES

Ask About Privacy Through Your Account

A clear contact route helps when you want to understand a data entry, change an account detail or question a cookie.

Account support path Open support from your signed-in account and choose the privacy topic.
Wallet status question For a DANA, OVO, GoPay or QRIS record, include the date and reference shown…
Correction request Tell us which account detail appears incorrect and what should change.
HANDLING PRACTICE

Six Practical Privacy Checks

We keep this policy practical by linking each privacy choice to an account action you can recognise.

Data we receive

We may receive the contact details you enter, account verification results, login timestamps, device signals and payment references.

Cookie controls

Cookies can remember a session and help us understand page movement.

Account protection

We use account checks around sign-in, profile changes and privacy requests.

Retention periods

We retain records only for the period needed for the stated account, payment, security or legal purpose.

Requesting changes

You can ask us to correct account details, explain a record, restrict a use or remove eligible data through account…

Device access

A mobile browser may create a new session when cookies are cleared or the device changes.

Privacy Policy Answers For tata4d

These questions address the privacy points you are most likely to check before opening an account or using the wallet path. Each answer refers back to our Privacy Policy and the practical steps available from your account, including requests about data, cookies and access.

It explains the account, device, cookie and payment-reference details we may handle, the purposes for using them, retention considerations, security steps and how you can contact us about your records.

Our Privacy Policy distinguishes payment status and reference data from wallet credentials. Do not send a wallet password or PIN to us; use the account support path for a payment-record question.

Open support from your signed-in account, identify the detail that needs correction and provide the intended value. We may confirm account ownership before changing the stored record.

You can submit a removal request through account support. We assess which records are eligible, because some account, payment or legal records may need to remain for a stated period.

Cookies can keep a browser session available and support page measurement. If you clear or block them, you may need to sign in again, including when sending a Privacy Policy request.

Use the email or phone linked to your account, describe the record or purpose you are asking about, and add a payment date or reference when checking DANA, OVO, GoPay or QRIS activity.

The policy is written for account activity connected with Indonesia, while access and eligibility depends on local law. Where local law permits, you can use the stated contact path for privacy requests.