Reference

Privacy Policy for eropa4d Accounts

Our Privacy Policy shows how eropa4d handles the data you provide when you open an account, verify your phone, enter the lobby or use DANA and QRIS.

Clear data purposesWallet activity contextPhone verification detailsRequest and contact path

Browse the lobby Read FAQ

Your Privacy Policy across DANA and QRIS

eropa4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies when you create an account, complete phone verification, sign in from a mobile browser or use the cashier with DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use account details to provide access, confirm wallet status, detect unusual sign-in activity

1
and respond when a payment receipt needs checking. Transaction records may include the selected rail, amount, time and status supplied by the payment process; we do not describe these records as a reason to send unrelated messages. Where access is discussed, it depends on local law.
2
You can ask us what data we hold, request a correction, or ask about deletion where a legal or operational record does not need to remain. The current policy applies to the eropa4d account path and should be read before you proceed.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WHEN DATA STALLS

Get Privacy Policy help beside wallets

A clear support path matters when your account data or wallet status does not look right.

SIX DATA PRACTICES

How we protect wallet and account data

This Privacy Policy is tied to practical account handling rather than broad promises. We separate the data needed for sign-in, phone verification and payment status from optional browser details, and we use…

Account details

We collect details needed to create and maintain your account, including contact data used during the phone verification step. We use that data for account access and support, not as a reason to request unrelated personal details.

Payment records

When you choose DANA, OVO, GoPay, QRIS, bank transfer or virtual account, we retain the account-linked status needed to identify the transaction. Receipt time and rail can help us resolve a stalled cashier step.

Cookies

Cookies can keep a mobile browser session connected while you move from login to the lobby. They may also remember limited preferences. You can manage browser cookie settings, though removing them may interrupt account access or require another sign-in.

Account security

We use sign-in and verification records to protect your account from unusual access. If you notice a session or phone detail you do not recognise, contact support through the account route and avoid sharing your private sign-in code.

Retention periods

We keep personal and transaction data only for the period connected with account operation, security checks, support handling or a required record. When a record no longer has that purpose, our handling follows the applicable deletion process.

Changes and contact

You can request a copy, correction or suitable deletion review through account support. We may confirm ownership before acting, then explain the result and any reason a specific payment or security record still needs to remain.

Privacy Policy answers for your account

These Privacy Policy answers focus on the questions you may have before opening an eropa4d account or using an Indonesian wallet. They explain the account step, device behaviour, payment records and contact process in plain language. If your situation is not covered, use the account support route and mention the exact policy question so we can direct it correctly.

It covers data connected with account creation, phone verification, sign-in, mobile browser cookies, support requests and payment status. It also explains how we handle records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect the correct account to the access step and supports account security when a sign-in issue occurs. We use the verified contact detail for those account purposes and may confirm ownership before handling a data request.

Yes. The Privacy Policy covers account-linked payment status and receipt details needed to identify a QRIS, DANA, OVO or GoPay event. We may use the rail, time and displayed status to investigate a cashier issue without requesting your private wallet code.

Cookies can keep your mobile browser session working as you move from login to the lobby and may retain limited preferences. You can change cookie settings in the browser, but removing them can end a session or require another sign-in.

You can use the account support route to request access to your data or ask for a correction. State the account detail involved, and be ready to confirm ownership. We will explain what can be changed and why some records may remain.

Retention depends on the purpose of each record, such as account access, phone verification, security handling, support or a payment event. We keep a record while that purpose applies or another required reason exists, then follow the applicable deletion process.

Yes. Access and eligibility depend on local law, including rules that may apply to your location in Indonesia. The Privacy Policy remains the place to check our data handling, while the account path determines whether access is available where local law permits.

Privacy Policy for eropa4d Accounts

Get Privacy Policy help beside wallets

How we protect wallet and account data

Account details

Payment records

Cookies

Account security

Retention periods

Changes and contact

Privacy Policy answers for your account

01 What does the eropa4d Privacy Policy cover?

02 Why does eropa4d need phone verification data?

03 Does the Privacy Policy cover QRIS and wallet receipts?

04 How do cookies affect eropa4d on my phone?

05 Can I request a copy or correction of my data?

06 How long does eropa4d keep account data?

07 Does Privacy Policy access depend on Indonesian law?

Related Pages