Reference

Privacy Policy for Your est4d Account

Our Privacy Policy explains what est4d collects, why we use it and how you can ask about your account data before opening an account.

Account dataWallet recordsCookie choicesAccess depends on local law
est4d Privacy Policy for Your est4d Account
PRIVACY HELP DESK

Get Help With an est4d Data Request

A direct support path helps when you want to ask what data is connected to your account or why a verification record is needed. We ask you to contact us through the support channel linked from the account area and include the email or phone detail used for access. For a wallet question, mention whether the reference came from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We may request account confirmation before discussing private records.

Team online

Account privacy

Ask us which account details, phone verification records and access history are associated with your profile. We use the account contact detail you provide to locate the correct record, then request an additional confirmation when the request could expose private information.

Wallet records

If a payment reference looks unfamiliar, send its method and status through our support channel. We can check the account-side record for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity without asking you to share a wallet password.

Correction requests

Tell us which personal detail needs changing and why it is inaccurate. We compare the request with your account step and phone verification status before making a change, helping prevent another person from altering the profile attached to your wallet records.

DATA HANDLING DETAILS

What We Keep Around Your Account

Our privacy process follows the practical actions you take: opening an account, confirming a phone number, signing in from a device, selecting a wallet and contacting support.

Account creation

When you open an account, we collect the details needed to create your profile and communicate with you. A phone verification step can be required before account access, helping us distinguish an account holder from an unverified sign-in attempt.

Device signals

A sign-in from a phone, tablet or desktop can generate device and session signals used to protect account access. These signals help us spot unusual activity and maintain a consistent path from login to the lobby without reading private content on your device.

Cookie controls

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can ask support how to change available cookie choices; disabling some cookies may affect sign-in or the way your privacy selection is stored.

Payment matching

A DANA, OVO, GoPay or QRIS reference is used to match a wallet instruction with the correct account record. Bank transfer and virtual account references may also be checked against the selected account step when a status needs confirmation.

Retention checks

We retain account, security and payment records only for the period needed for the stated operational or legal purpose. When you ask about deletion or retention, we first check whether a record must remain available for reconciliation, access protection or a pending request.

Your requests

You can ask to access, correct or clarify personal data connected with your profile. Send the request through our support channel, identify the account contact detail and describe the action you want; we may verify ownership before sharing or changing anything.

Privacy Policy Answers for est4d

These Privacy Policy answers cover the questions we expect before you open an account or connect an Indonesian wallet. They explain the data path in plain terms, including phone verification, cookies, device access and payment references. If your situation is not covered, our support channel can check the account record after confirming that you are authorised to ask about it.

The Privacy Policy covers information connected to your account, phone verification, device sessions, cookies, support messages and payment references. It explains why we use those details, how we protect access and how you can ask for access, correction or clarification where local law permits.

Phone verification helps confirm that the person requesting account access controls the contact detail attached to the profile. It can also help us investigate an unfamiliar sign-in or a wallet status question without discussing private account information with an unauthorised person.

Yes. The Privacy Policy covers account-side references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match an instruction, check a status and respond to a payment-related privacy request.

Contact our support channel from the account area and state that you want to ask for the personal data connected with your profile. Include your account contact detail and the scope of the request. We may confirm account ownership before providing a response.

You can ask us to correct information that is inaccurate or incomplete. Describe the field that needs changing and provide the account contact detail used for access. We may compare the request with phone verification and payment records before applying a change.

Cookies can remember your session and the privacy choices made on your device. If you clear or restrict them, sign-in and preference storage may work differently. Contact support if you want help understanding the available cookie choices or a setting that no longer appears.

We keep records for as long as they are needed for account security, payment matching, dispute handling, support history or a legal requirement. You can ask us about a specific record through support, and we will explain the applicable retention reason where local law permits.