Reference

Privacy Policy for Your eropa4d Account

Our Privacy Policy explains how we collect, use and protect the details you provide when opening an eropa4d account.

Clear data purposesWallet records explainedAccount access stepsIndonesia-focused wording
eropa4d Privacy Policy for Your eropa4d Account
CONTACT DATA HELP

Get Privacy Policy Support

A direct support route matters when your account details or wallet record do not look right.

Account privacy request Use the account support path when you want to ask what personal details we hold or why a phone verification record appears. We may ask you to confirm the registered phone number before discussing account-specific data, so the request reaches the correct account.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact us from the cashier support path and include the transaction date and status shown on your account. Do not send a wallet PIN, password or complete card credential in your message.
Access and correction When your name, phone detail or account record needs correction, tell us which field is inaccurate and provide the account confirmation requested by support. We review the request against our records before making a change, with access handled where local law permits.
DATA HANDLING DETAILS

What We Do With Account Data

We apply the Privacy Policy to the information needed for account access, payment status and service security rather than treating every device signal as a profile detail.

Account creation

When you open an account, we collect the details needed to create your login and start phone verification. We use those details to recognise your account across the mobile browser and desktop path, while access or eligibility depends on local law.

Payment matching

A payment reference from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account helps us identify the status of a requested cashier action. We use the reference for matching and support checks, not as a reason to request your private wallet PIN.

Cookies and sessions

Cookies and session signals help keep your login state, language choice and account route consistent while you browse on a phone or computer. You can manage browser cookie settings, though switching them off may interrupt the secure path between account access and the lobby.

Security checks

We examine login and device signals when an account action appears unusual, such as a new device or repeated access attempt. These checks help us protect account records and may require another phone verification step before account-specific support can continue.

Retention of records

We retain account, support and transaction records for as long as needed for the stated service purpose, security checks and applicable legal duties. When a record is no longer needed, our handling follows the deletion or anonymisation process available under the relevant rules.

Change requests

To request access, correction or deletion of eligible personal data, contact us through the secure account support route and describe the record involved. We may verify your account first, then explain what action is possible under the Privacy Policy and local law.

Privacy Policy Answers for eropa4d

These Privacy Policy answers address the account questions you are most likely to have before opening an eropa4d account or using the lobby from Indonesia. We explain the data connected with phone verification, mobile sessions, payment references and support contact. If your situation is specific, use the secure account path rather than sharing personal details in an open message. Access remains where local law permits.

The eropa4d Privacy Policy covers account details, phone verification, device and session signals, cookie use, support messages and payment references. It explains why we use each category, how we protect account access and how you can ask about, correct or delete eligible personal data.

We use your phone number to create and verify the account path, help distinguish your login from another account and confirm certain support requests. Phone verification may be requested again after an unusual device signal, and access depends on local law.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account status. We use those references to match a cashier action and investigate a receipt question without asking for your wallet PIN.

Our mobile browser path may use cookies and session data to keep your login route, language choice and account state consistent between account access and the lobby. Browser controls can remove or block cookies, but doing so may interrupt verification or account navigation.

Send a request through the secure account support path and state whether you want access, correction or deletion of an eligible record. Include the registered phone number only inside that protected route. We may verify account ownership before explaining the available action.

We keep account, support and transaction records for the period needed for the purpose described in the Privacy Policy, security checks and applicable legal duties. Once a record is no longer needed, we follow the deletion or anonymisation process available under relevant requirements.

Yes. Contact support through the cashier path with the transaction date, payment method and status shown on your account. We can explain a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference after confirming that you control the account.