Reference

Privacy Policy for Your tanjung4d Account

Our Privacy Policy shows how we collect, use and protect details linked to your tanjung4d account, including login data and payment status from DANA, OVO, GoPay and QRIS.

Account data explainedPayment records describedCookie choices includedRequest path available
tanjung4d Privacy Policy for Your tanjung4d Account
CONTACT ROUTES

Ask About Privacy Through Account Support

A clear support path helps when you want to ask about your Privacy Policy rights, correct an account detail or check why a payment record is…

Account data request Use account support to ask what personal details are held for your profile, why…
Payment record check If a DANA, OVO, GoPay or QRIS receipt looks unfamiliar, send the transaction reference…
Correction request You can ask us to correct an outdated phone detail or account record through…
DATA PRACTICE

Account Security Tips And Your Privacy Policy

Privacy works best when our handling and your account habits meet in the middle. We limit internal access to data needed for account service, payment matching, security checks and support.

What we collect

We may receive your account name, phone verification result, sign-in events, device signals, support messages and payment references. For a Bank Mandiri Deposit record, we use the reference and status needed to match the account action, not your banking password.

Why we use it

We use account data to provide access, match DANA or QRIS activity, answer support requests, detect suspicious sign-ins and keep policy records accurate. We do not use a payment reference as a reason to request your wallet PIN or full banking credentials.

Cookies and devices

Cookies can keep a sign-in session and selected settings working across the mobile browser path. Device signals help us compare a new sign-in with earlier activity. You can clear browser cookies, but doing so may sign you out and remove saved settings.

Account security

Phone verification comes before account access, and unusual sign-in activity may trigger an extra check. Keep your verification details private, sign out on shared computers and contact support if Account Security Tips or a login event looks unfamiliar.

How long we retain

We retain account, support and payment records only for the period needed for service, security, dispute handling or legal duties. When a record is no longer needed, we remove it or separate it from direct account identifiers where practical.

Who to contact

Send access, correction, deletion or policy questions through account support. Include your account identifier, the request type and any relevant receipt reference, but never include a wallet PIN, password or full card or banking credential.

Privacy Policy Questions For tanjung4d

These answers address the Privacy Policy searches we hear most often from Indonesian account holders. They cover the account step, local wallet records, device behaviour, correction requests and the support route. If your case involves a specific receipt or sign-in event, keep that reference ready and contact us through account support.

It covers details connected with your account, phone verification, sign-ins, device signals, cookies, support messages and payment references. It also explains why we use those records, how long we retain them and how you can ask for access or correction where local law permits.

No. Our payment record may show the account reference, receipt reference and transaction status for DANA or QRIS, but your wallet PIN is not needed for matching. Do not send a PIN or password to support when asking about a receipt.

Phone verification helps connect the account to the person completing the account step and gives us a security check before access. We use the result for account protection and support matching, subject to this Privacy Policy and local requirements.

You can contact account support with your account identifier and ask which personal records we hold. We may verify your identity before responding, and the scope or timing of a request depends on local law and any permitted exceptions.

Send a correction request through account support and identify the record that is wrong. For a payment detail, include the safe transaction reference rather than a wallet credential. We check the account record and apply changes where local law permits.

Cookies can retain session state and selected settings in your mobile browser. Clearing them may sign you out and remove those settings. You can manage cookies in the browser controls, while our Privacy Policy explains which session and security uses remain.

You may submit a removal request through account support. We assess which records can be removed and which must remain for security, payment disputes or legal duties. Any deletion or restriction is handled where local law permits, with the result explained to you.