Reference

Privacy Policy For Your oyen4d Account

Our Privacy Policy explains how we collect, use and protect details connected with your oyen4d account.

Clear data purposesWallet record controlsPhone verification context
oyen4d Privacy Policy For Your oyen4d Account
CONTACT ROUTES

Reach Us About Privacy Policy

A direct support request gives you a practical route for questions about the Privacy Policy.

Account privacy request Use the support route inside your account when you want to ask what personal…
Wallet record question For a DANA, OVO, GoPay or QRIS concern, send the transaction reference and approximate…
Access concern If a login or phone verification issue affects your privacy request, describe the device…
DATA PRACTICES

How oyen4d Handles Account Details

We keep this policy practical: each data category has a reason tied to account access, payment matching, security or support.

Account details

We use your account identifier and phone verification status to distinguish your profile from another account and to complete sign-in checks. If a detail is wrong, contact us with the account reference so we can assess a correction request under this Privacy Policy.

Payment references

A wallet name such as DANA or GoPay, a QRIS reference, or a BCA, BRI, Mandiri or BNI transfer reference may be stored with an account event. We use the reference to reconcile status without requesting your wallet PIN or bank password.

Cookies and browsers

Cookies can keep a mobile browser session connected to the correct account and remember basic page settings. You can clear or restrict cookies in your browser, though sign-in continuity and some account steps may then require another verification check.

Security signals

Login time, browser type and device signals help us investigate repeated access errors or activity that does not match your account path. These signals are used for account security and support checks, not as a reason to request private credentials from you.

Retention approach

We keep personal details only for the period needed for account operation, security investigation, support handling and applicable record duties. A deletion request may not remove records that are needed to explain a payment event or resolve an account dispute.

Your requests

You can ask what information is connected with your account, request a correction, or ask about deletion where local law permits. We may verify that you control the account before responding, using the existing phone verification path rather than asking for a password.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect from Indonesian customers before they open an account or contact support. Each answer stays focused on personal data, cookies, payment references, account access and requests to oyen4d. If your situation is not covered, use the account support route and describe the exact record or verification step involved.

It covers details connected with account creation, phone verification, sign-in, browser use, support messages and payment references. This includes records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those records are needed to operate or check your account.

Phone verification helps us identify the account owner during access and support requests. It can also help separate one account record from another when a wallet receipt is checked. We do not need your phone password, wallet PIN or bank password for this step.

Yes. The Privacy Policy covers payment references connected with your account, including DANA and QRIS records. We use a reference, status and related account event to investigate a receipt or wallet question. We do not treat a payment reference as permission to access your wallet.

Send a request through the support route inside your account and identify the detail you believe is incorrect. Include the account phone or email identifier, but exclude passwords and security codes. We may verify account control before checking the correction under local requirements.

You can ask about deletion where local law permits. We assess the request against active account needs, security checks, unresolved support matters and records needed to explain a transaction. Some records may remain for a required period even after other account details are removed.

Cookies can support sign-in continuity and basic browser settings on your phone or desktop. If you block or clear them, the account may ask for another sign-in or verification step. Your browser controls cookie removal, while our policy explains how related account data is used.

Yes. Account access and eligibility depend on local law. If you contact us about access from Indonesia, tell us the account step and device path involved. We can explain the relevant policy process, but we cannot treat this Privacy Policy as a change to local requirements.