Reference

obral4d Privacy Policy For Your Account

obral4d Privacy Policy explains how we collect, use and protect the details connected with your account, including login records and wallet selections such as DANA, OVO, GoPay and…

Account dataCookie choicesAccess requestsWallet records

Browse Home Lobby Read FAQ

Explore How Privacy Applies In Indonesia

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

We use account details to create access, confirm phone ownership, protect login sessions and match payment records with the correct account. A deposit reference may identify DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, while the transaction amount and status help us resolve a

1
receipt question. Device and browser signals can help us detect unusual access, but we do not use them to describe your personal interests. Cookies support session continuity and remembered settings. We retain records only for operational, security or legal needs, then remove or reduce them when
2
they are no longer required. Access depends on local law, and where local law permits, you may request access, correction or deletion through our support route. The policy applies to account activity connected with obral4d and should be read before opening an account.

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

CONTACT PATH

Open A Privacy Request Through Support

A clear support path helps you ask what data we hold or explain a concern about account access.

Data copy Ask for a copy of account details linked to your access, such as the phone verification record, login history or payment references for DANA and QRIS. We use the account identifier you provide to direct the request and may confirm ownership before releasing any data.

Correction route If your account details are inaccurate, contact us through the support route shown after login and explain the change needed. For a wallet or bank reference, include the relevant receipt detail without sending a password, PIN or one-time security code.

Access concern When a login record or device alert looks unfamiliar, tell us through the same account support path. We can check session details, phone verification and payment status together, including records connected with OVO, GoPay, bank transfer or a virtual account.

DATA PRACTICE

Switch Through Your Privacy Controls

Our privacy process follows the way your account actually works, from the first phone check to a later wallet receipt or device change.

Collected details

We may receive your phone number, account identifiers, login events, device signals and payment references. A QRIS or DANA receipt can show a transaction reference and status, while we use those fields to match activity rather than to create a separate profile about you.

Cookie use

Session cookies help keep you signed in while you move from account settings to a policy page, and preference cookies can remember choices on the same device. Clearing browser storage may sign you out or remove saved settings, but it does not erase account records by itself.

Account protection

Phone verification is checked before account access, and unusual device or login activity may trigger an additional review by our support team. Never share your password, PIN or one-time code in a privacy request; we do not need those secrets to locate your account.

Payment matching

When you use OVO, GoPay, bank transfer or a virtual account, we retain the reference needed to match a receipt with your account and status. We do not need the wallet password or banking PIN, and you should remove those details before sending any screenshot.

Retention period

We keep personal data while it supports account access, payment reconciliation, security checks or a legal requirement. After that need ends, we remove it, anonymise it or restrict access according to our internal retention process and applicable local law.

Request changes

You can ask for access, correction, deletion or a restriction on certain processing through the support contact route. Include your account identifier and a clear request; we will confirm ownership, explain any local-law limitation and publish the current support hours beside the contact option.

Browse Privacy Policy Answers Before Access

These Privacy Policy answers address the questions we hear before an account is opened or when a wallet record needs checking. We keep each answer tied to the data process, device path or account step involved. If your situation is not covered, use the support route connected with your account and tell us which record you want us to locate.

The obral4d Privacy Policy covers account details, phone verification, login and device records, cookies, payment references and requests to access or correct data. It applies to activity connected with your account, including records from DANA, OVO, GoPay, QRIS, bank transfer and virtual account use.

We use your phone number to create and protect account access, complete the phone verification step and help support locate the correct record. It can also help us investigate an unfamiliar login. We do not ask you to send a password, PIN or one-time code.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, including a transaction reference, amount and status needed for reconciliation. We use those details to match a receipt with your account and do not need your wallet password or banking PIN.

Use the support contact route shown in your account area and ask for a data copy. Include your account identifier and describe the records you need, such as login events or a GoPay receipt reference. We may confirm ownership before sending account data.

You can request a correction through the account support route. State which field is inaccurate and provide the relevant context, such as a phone verification detail or bank transfer reference. We will check ownership and explain the next step where local law permits.

We retain account data while it is needed for access, security checks, payment matching or a legal requirement. When that purpose ends, we remove, anonymise or restrict the record under our retention process. The exact outcome can depend on local law and the record type.

Yes. Your mobile browser settings let you clear or restrict cookies, while the account menu provides access to this Privacy Policy without a separate application. Clearing cookies may end your session or remove preferences; it does not automatically delete account or payment records.

obral4d Privacy Policy For Your Account

Open A Privacy Request Through Support

Switch Through Your Privacy Controls

Collected details

Cookie use

Account protection

Payment matching

Retention period

Request changes

Browse Privacy Policy Answers Before Access

01 What does the obral4d Privacy Policy cover?

02 Why does obral4d need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a copy of my data?

05 Can I ask obral4d to correct my details?

06 How long does obral4d keep account data?

07 Can I manage cookies on my mobile device?

Related Pages