Reference

Privacy Policy for your Indonesia account

Your DANA, OVO, GoPay and QRIS account details are covered here before you open your account, so you know what we collect, why we keep it, and how…

DANA, OVO, GoPay, QRISCookie controlsSession historyPrivacy help 09:00-01:00 WIB
link4d Privacy Policy for your Indonesia account
CONTACT ROUTES

Privacy help through clear local channels

Fast privacy support depends on matching your request to the right account record. Before we change personal data, we may ask you to confirm your mobile number, last login time, or a…

Live chat privacy queue Use live chat from 09:00 to 01:00 WIB when you need us to check login records, cookie choices, or a payment-linked privacy concern. We will ask account questions before discussing personal data.
Help page mailbox Send a privacy request through the Help page when you need correction, export, or deletion of eligible account data. Include your registered mobile number and one DANA, OVO, GoPay, or QRIS reference.
Account security check Open Profile > Security > Active Sessions if you want to see current device access before contacting us. If a session looks unfamiliar, tell support the device type and approximate login time.
CONTROL CHECKS

Your controls across wallet and devices

Privacy on link4d is handled around real account events, not vague promises. We separate payment references from wallet credentials, limit staff access to support and security tasks, and log changes made to…

Payment data separation

When a DANA, OVO, GoPay, or QRIS payment is recorded, we keep the reference, status, amount, and time. We do not ask for your wallet PIN or full app login credential.

Game session privacy

When you open Speed Blackjack, Aviator, or Basketball Betting, we store session time, device marker, and wallet impact. This helps us answer disputes without building a public profile about your activity.

Cookie choice

Cookies keep your session active, remember display choices, and flag repeated failed logins. You can clear them in your browser; after that, we may ask you to verify the account again.

Retention handling

We keep account and transaction records only for account operation, legal needs, security checks, or unresolved disputes. When data is no longer needed, we remove it or detach it from direct account identity.

Access requests

You can ask what account data we hold, request a correction, or seek removal of eligible records. We verify your identity first, then reply through the same channel used for the request.

Device protection

Profile > Security > Active Sessions shows where your account is open. End any device you do not recognize, change your password, and contact us if a payment record also looks unfamiliar.

Privacy questions before you open account

These answers explain how we apply this Privacy Policy to account setup, payments, cookies, device sessions, and support contact. They are written for you before you join, and they also help existing account holders understand what can be changed, what must be verified, and what may need to stay on record under applicable rules.

We collect the details needed to run your account, such as mobile number, login credential, wallet name, device marker, and support messages. Payment records may include DANA, OVO, GoPay, or QRIS reference data.

No. We receive payment status, amount, time, and a reference code from the payment flow. We do not need your wallet PIN, app password, or full wallet login to process account records.

Send the request through live chat or the Help page mailbox. We will verify your mobile number, recent login, or a payment reference first, then provide eligible account data in a clear format.

Yes, if the correction is supported by account checks. We may ask for your current mobile number, last login time, and one recent DANA, OVO, GoPay, or QRIS reference before making a change.

Some wallet and account records may be kept for accounting, dispute handling, security checks, or legal needs. When a record is no longer needed, we remove it or detach it from direct identity.

Cookies keep you signed in, remember display choices, and help detect repeated failed logins. You can clear browser cookies, but you may need to verify your account again on the next login.

Open Profile > Security > Active Sessions, end any device you do not recognize, then contact live chat during 09:00 to 01:00 WIB. Share the device type and approximate login time.