Reference

Open angel4d Privacy Policy Clearly

Our angel4d Privacy Policy explains what we collect when you create an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account detailsWallet referencesDevice accessPolicy contact
angel4d Open angel4d Privacy Policy Clearly
CONTACT OUR DESK

Ask About Privacy From Your Account

A direct contact path helps when you want a Privacy Policy answer rather than a general account reply. Send your request through the account support route and include the phone number linked to your profile, the subject of your request and any relevant payment reference. We use those details to locate the correct record without asking you to share a wallet password. If your access from Surabaya or another Indonesian location depends on local law, we can explain the applicable account response.

Team online

Account support

Use the support route after signing in and state whether you need access, correction or deletion help. We match your request with the phone verification record on your account, then respond through the contact path attached to that profile.

Wallet status

For a DANA, OVO, GoPay or QRIS question, include the transaction reference and date rather than private wallet credentials. Our team can check the stored payment status and explain which account record was used to reconcile the request.

Access concern

If a new phone or browser blocks account access, tell us the device path and the last successful sign-in. We can review the security signal, explain the next verification step and keep the conversation focused on your Privacy Policy request.

DATA HANDLING

Browse Your Privacy Controls With Context

We keep this policy practical by linking each data use to an account action you can recognise.

Account records

We use the details you provide during account creation, including contact information and phone verification, to maintain your profile and respond to requests. Please keep those details accurate so a correction request can be matched to the right account record.

Cookie choices

Our site may use cookies or similar browser storage to remember a session, support page navigation and recognise basic device settings. You can manage browser permissions, although removing necessary storage may sign you out or require another account verification step.

Device signals

When you move from a mobile browser to desktop, we may record technical signals such as browser type, session time and access pattern. These details help us assess an unfamiliar login without reading the private contents of your device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references showing amount status, timing and reconciliation state. We use those references to trace an account action, while wallet credentials remain with the relevant payment service.

Security checks

A sign-in from a changed device or an account action needing confirmation may trigger an additional check. We use the phone verification route and related security records to protect your profile, and we do not ask you to send a wallet password.

Retention requests

We keep data only for the period needed for account operations, security checks, dispute handling or a legal requirement. To ask about access, correction or deletion, contact support with your linked phone number so we can verify the request.

Find Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before account creation. Each response points to a practical step, from checking a device session to asking about DANA or QRIS references. If your question involves eligibility or access, the answer remains subject to local law and the records connected with your account.

The angel4d Privacy Policy covers account details, phone verification, sign-in and device signals, cookie use, support messages and payment references. It explains why we use each category, how we protect it and how you can ask about access, correction or deletion.

Yes. Privacy Policy treatment includes the payment reference, timing and status needed to match DANA, OVO, GoPay or QRIS activity with your account. We use that record for reconciliation and support, while your wallet password stays with the payment service.

Sign in, open the account support route and request access to your data. Include the phone number linked to your profile and describe the record you need, such as device activity or a payment reference. We may verify account ownership before responding.

We record relevant phone and browser signals to maintain a session, identify an unfamiliar sign-in and support a phone verification step. These signals help protect your account; they do not give us access to private files, messages or wallet credentials on your device.

You can request a correction or ask about deletion through account support. We first verify the linked account, then assess the request against active security, payment reconciliation and legal record needs. Some records may need to remain stored for a valid operational reason.

When you switch from a mobile browser to desktop, Privacy Policy handling may include the new browser type, session time and access pattern. If the change looks unfamiliar, we may ask for phone verification before restoring account access, where local law permits.

Use the support route attached to your account and write Privacy Policy in the subject. Include your linked phone number, request type and any relevant receipt reference. Do not send a DANA, OVO, GoPay or QRIS password; we only need the transaction reference.