Reference

Privacy Policy for original4d Accounts

original4d Privacy Policy explains how we handle the details connected with your account, including phone verification, wallet status and activity on desktop or mobile.

Account dataWallet recordsCookie choicesSecurity requests
original4d Privacy Policy for original4d Accounts
CONTACT PATH

Privacy Policy Help for Account Requests

A clear contact route matters when a Privacy Policy question involves your own account, phone verification or a wallet record.

Account questions For a copy, correction or explanation under this Privacy Policy, use the account support path and identify the phone number linked to your account. We may ask for a verification step before discussing personal details, so the request reaches the right account holder.
Wallet records When your request concerns DANA, OVO, GoPay or QRIS status, include the relevant reference and date shown in your account. We use those details to locate the record while avoiding requests for your wallet PIN, password or complete card credentials.
Access concerns If a Privacy Policy page or account screen does not load on your phone, use the contact route visible in your account or return from a desktop browser. Tell us the device path and screen involved so we can separate access trouble from a data request.
HANDLING DETAILS

Six Practical Privacy Controls

We handle this policy area through the account steps you actually use: phone verification, sign-in, wallet checks and support requests.

Account details

We may handle the phone number and account details you provide during account opening and phone verification. Those details help us connect sign-in activity, support messages and account changes to one record instead of treating each request as unrelated.

Wallet references

A DANA, OVO, GoPay or QRIS request can create a reference, status and support trail. We use the minimum detail needed to check whether the account event was received or needs attention, and we do not ask for your private wallet PIN.

Cookie controls

Cookies or similar storage may remember a session, preserve a page choice or show us that a mobile page failed to load. You can manage browser storage through your device settings, although removing it may require another sign-in or reset a saved preference.

Account security

Phone verification and sign-in checks help us distinguish an account request from an unverified message. Keep your access details private and contact us through the account route if a device, phone number or wallet status appears different from your own record.

Retention questions

We retain records for the period needed to provide account support, resolve a wallet reference, protect access or meet a legal obligation. The period can differ by record type, so ask through support when you need a retention explanation for a specific account event.

Change requests

You can ask us to correct account details, explain a data use or clarify a cookie record through the support path. Include the requested change and the phone number linked to your account; we may verify ownership before changing or disclosing personal data.

Privacy Policy Questions About original4d

These Privacy Policy answers address the account and device questions you are most likely to have before using original4d from Indonesia. Each answer points to a practical step, from phone verification to a DANA or QRIS reference. Where access or eligibility is involved, it depends on local law, and the account support path remains the place to ask about your own record.

The Privacy Policy covers account details, phone verification, sign-in events, cookie use, wallet references and support requests. It explains how we use those records to provide account access, check a DANA, OVO, GoPay or QRIS status, protect the account and respond to your data questions.

We may receive the details you enter for account creation, including a phone number used for verification, plus records created when you sign in or contact support. A wallet request may also create a reference and status record. We use those details for the account purpose described here.

Use the support path shown inside your account and state whether you want a copy, correction or explanation. Include the phone number linked to the account and the specific record, such as a QRIS reference. We may verify account ownership before completing the request.

Yes. The Privacy Policy explains that cookies or similar storage may keep a mobile session, remember a page choice or help identify loading trouble. You can manage storage in your browser or device settings, but clearing it may sign you out or remove a saved preference.

We use account access checks, phone verification and support verification to reduce the chance of discussing personal details with the wrong person. For DANA, OVO, GoPay and QRIS requests, share the reference needed for checking, never your password or private wallet PIN.

Retention depends on the type of record and why it was created. We may keep account, support or wallet references while needed for account service, security, dispute handling or a legal obligation. Ask through support for an explanation about a particular record linked to your account.

Access depends on local law. The Privacy Policy applies to the personal data connected with an account when access is available where local law permits. Before opening an account, check the access notice shown for your location and contact support if you need clarification about your own account.