Reference

2d 04 Privacy Policy Before Account Access

2d 04 Privacy Policy sets out what account, device and payment details we use, why we use them, and how you can ask for changes.

Account dataCookie choicesRequest path
2d04.xyz page image
CONTACT ROUTE

Reach Us When A Privacy Request Stalls

A clear support route helps when a privacy question is harder to resolve from the account screen. Use the support link shown in your account area and include the email or phone detail attached to your profile, without sending wallet passwords or one-time codes. We can then locate the relevant request, check its status, and explain the next account step.

Team online

Account request

Use the support path beside your account settings to ask for a copy, correction or removal of personal data. Include the request type and the contact detail attached to your profile.

Wallet receipt

If a DANA, OVO, GoPay or QRIS receipt is linked to the wrong account record, share the transaction reference through support. Do not send your wallet PIN or login code.

Access question

For a privacy question after phone verification, sign in on the same mobile browser where possible and use the account support link. We will explain the applicable request path where local law permits.

DATA PRACTICE

Explore Data Choices Beside Account Security

We handle privacy as an account operation rather than a distant legal page. Our process separates details needed for sign-in, payment matching and support from optional preferences, while…

What we collect

We may receive your contact detail, phone verification result, sign-in record, device session data and payment reference.

Cookie controls

Cookies can keep a mobile browser session connected and help us remember account settings.

Account protection

Phone verification comes before account access, and we use sign-in checks to reduce mistaken access.

Payment matching

For OVO, GoPay, DANA, QRIS, virtual account and bank transfer records, we keep the reference needed to match payment status.

Retention questions

Some records remain for the period needed to complete account, payment or legal tasks.

Change request

Contact the support team from your account path to request correction, access or deletion where local law permits.

Browse Privacy Policy Answers For Your Account

These questions cover the privacy points you are most likely to check before opening an account or choosing a local wallet. Each answer stays focused on the 2d 04 policy, the records connected to your account, and the practical route for asking us to act.

It covers account details, phone verification, browser and device records, cookies, payment references, support requests, retention and your available rights. Access depends on local law and the account process used.

We use the verification result to connect sign-in activity with the correct account and reduce mistaken access. We do not need your one-time code or wallet PIN to handle a privacy request.

We keep the payment reference and status needed to match a DANA or QRIS request with your account and receipt. We do not require the wallet PIN for that matching step.

Yes. Use the support link in your signed-in account area and request a copy of the data connected to your profile. We may confirm your account detail before responding.

Send a correction request through the account support path, identify the field that is wrong, and provide the updated detail. We will assess the request where local law permits.

Yes. The Privacy Policy explains how cookies can retain a mobile browser session and account preferences. You can change cookie controls in your browser, but another sign-in may then be needed.

Retention depends on the record and the account, payment or legal task it supports. Ask support about a specific DANA, GoPay, bank transfer or virtual account reference for a precise response.