Reference

Privacy Policy For Your aye4d Account

Our Privacy Policy explains how we collect, use and protect the details connected with your aye4d account, including contact data, device signals and wallet activity.

Account dataWallet recordsCookie choicesAccess depends on local law

Explore Our Lobby Read FAQ

How Wallet And Account Data Moves

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

We use account details to create access, confirm your phone before account entry and respond when a payment status needs checking. When you choose DANA, OVO, GoPay or QRIS, we record the transaction reference and status needed to match your account activity; we do not need

1
to store every detail held by your wallet provider. Device and browser signals can help us recognise unusual sign-in attempts and protect the account. We may retain records for as long as needed for account administration, dispute handling, security checks or legal duties. Where local law
2
permits, you can ask what personal data we hold, request a correction or ask about deletion, subject to records we must keep.

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

CONTACT YOUR WAY

Get Help With A Privacy Request

A clear contact path helps when your account details, cookie choice or wallet record needs attention.

DATA CONTROL

What We Protect And Retain

Privacy controls work alongside the account steps you already use: phone verification before access, a sign-in session on your chosen device and a payment record that can be matched to the cashier…

Collection

We may collect your account contact details, phone verification status, sign-in activity, device or browser signals and transaction references. The purpose is to provide account access, investigate security events and match a wallet status with the correct account record.

Security

Phone verification helps us distinguish an account owner from an unapproved sign-in attempt. Keep your access details private, avoid sending security codes in a support message and contact us if a device or session appears unfamiliar.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether an account page loads correctly. You can manage cookie permissions in your browser, although restricting them may interrupt login or require another verification step.

Retention

We retain account, security and payment records only for the operational, dispute or legal period that applies to them. A request to remove data may not erase records that are needed to resolve a transaction or meet a legal obligation.

Your requests

You can ask us to describe the personal data linked to your account, correct an inaccurate field or explain a processing purpose. Where local law permits, you may also ask about deletion or restriction, subject to required records.

Device changes

Moving from desktop to a mobile browser can create a new session signal. If that change triggers phone verification, it is an account-security step rather than a new data request; finish verification only through the aye4d account page.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account and payment questions we expect before you open access. We keep the wording practical: what we collect, why a device may ask for verification, how wallet references are used and how to contact us. If your situation is not covered, use the site contact route and identify the exact privacy point you want us to address.

The aye4d Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references and support requests. It also explains how we use, protect and retain those records, plus the request options available where local law permits.

Phone verification helps confirm that the person entering the account has the expected access detail. We may use the verification status to protect a session, investigate an unusual sign-in or respond to an account request without revealing private data to someone else.

Yes. The Privacy Policy covers the transaction references and status details connected with DANA, OVO, GoPay and QRIS activity. We use those records to match a payment event with your account and resolve status questions, while the wallet provider handles its own data.

You can contact us to ask about an inaccurate account field, such as a phone detail or contact record. Explain the correction you need and provide enough account context to locate it. We may confirm ownership before changing or discussing personal data.

Cookies can maintain a mobile-browser session, remember a setting and help identify a page-loading problem. If you clear site data or block cookies, the account may request phone verification again. Your browser controls the available cookie permissions on that device.

We keep payment references for the period needed for account service, security checks, disputes and legal duties. The exact period can differ by record type and applicable rule. You can ask support which purpose applies to a particular DANA, OVO, GoPay or QRIS reference.

Use the contact route displayed on the aye4d site and state that your request concerns the Privacy Policy. Name the account issue, cookie question or payment reference involved, but do not send a password or security code. We may request ownership confirmation before replying.

Privacy Policy For Your aye4d Account

Get Help With A Privacy Request

What We Protect And Retain

Collection

Security

Cookies

Retention

Your requests

Device changes

Privacy Policy Answers For Indonesia

01 What does the aye4d Privacy Policy cover?

02 Why does aye4d ask for phone verification?

03 Does the Privacy Policy cover DANA, OVO, GoPay and QRIS?

04 Can I ask aye4d to correct my account data?

05 How does aye4d use cookies on mobile?

06 How long does aye4d keep payment records?

07 How do I contact aye4d about this Privacy Policy?

Related Pages