Reference

4dprise Privacy Policy for Your Account

Our 4dprise Privacy Policy puts your account, wallet and device choices into one readable path before you open the lobby.

Account dataWallet activityDevice choicesPolicy requests
4dprise 4dprise Privacy Policy for Your Account
CONTACT ROUTES

Contact 4dprise About Privacy Policy Access

A clear contact route helps when you cannot find a policy detail or need a data request handled against the right account. Sign in first when possible, then use the contact path shown in your account area so we can match your request without asking you to send wallet credentials in an open message. Our team can also check a payment receipt or status reference without exposing unrelated account data.

Team online

Account contact route

Open your account area and use the displayed contact path for Privacy Policy questions. Include your registered phone number only through that protected route, never inside a public message.

Wallet status request

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, send its transaction reference through support. We compare the reference with your account record and avoid requesting your wallet password.

Data change request

Ask us to correct an account detail or explain stored data through the same account contact path. We may verify your phone before applying a change to protect your account.

SECURITY PRACTICE

Six Privacy Controls For Your Account

We handle this policy area through practical account steps rather than broad promises. Phone verification helps connect a request to the correct account, while session and device signals help us investigate unusual…

Account data

We use your registration details, verified phone and account settings to create access and answer requests. We do not need your wallet password to match a DANA or QRIS reference.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event may carry a reference, amount and status. We use those fields to reconcile the account record.

Cookies and sessions

Cookies and session markers help keep the mobile path signed in and remember essential settings. You can clear browser data, although signing in again may be required.

Device security

We may record browser, device and sign-in signals to identify unusual account activity. These signals support access checks and are not a substitute for your phone verification.

Retention choices

We keep records for account operation, payment matching, security checks or legal needs. When a record is no longer needed for those purposes, we remove or anonymise it.

Policy changes

If this Privacy Policy changes, we place the updated wording on the policy path and show the effective date. Check that path before changing account or wallet settings.

Privacy Policy Questions About 4dprise

These answers cover the searches we hear most often before an account is opened or a wallet is connected. They explain the Privacy Policy in plain terms, while the full wording remains available through the policy path in your account. If your request concerns a specific record, use the protected contact route so we can verify ownership first.

The 4dprise Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references, retention practices, policy changes and requests to access or correct your data.

We do not need your DANA, OVO, GoPay or QRIS wallet password to match a payment. We use the account-linked reference and status needed to reconcile the transaction.

Device and browser signals help us recognise an active session, investigate unusual sign-ins and protect the correct account. They can also support a phone verification check when access looks unfamiliar.

Use the contact path inside your signed-in account and ask for a data access request. We may verify your registered phone before confirming which records belong to you.

Yes. Send a correction request through the account contact route, describe the inaccurate field and provide the updated detail. We may request phone verification before changing the record.

We retain payment references while they support account operation, status checks, security work or legal needs. After that need ends, we remove or anonymise the applicable record.

Yes, the Privacy Policy sets out our handling of data for Indonesian account access, while availability and eligibility depends on local law. Check the current policy wording before submitting details.