Reference

satuan4d Privacy Policy For Account Data

Clear choices for your account, DANA and QRIS records are at the centre of this Privacy Policy.

Account recordsWallet activityCookie choicesContact requests
satuan4d satuan4d Privacy Policy For Account Data
HELP WITH YOUR RECORDS

Get Privacy Help Near Account Access

A clear contact route helps when your account record or wallet reference needs attention. We ask you to use the support link beside the login or cashier path, describe the issue, and avoid sending a full password or private wallet PIN. We may request account details needed to confirm ownership before changing or disclosing information.

Team online

Account access request

Use the support link beside login when you cannot reach your account. We check the details needed to confirm ownership before discussing stored records or changing contact information.

Wallet record question

For DANA, OVO, GoPay or QRIS references, include the date and visible transaction reference only. We use those details to locate the record without asking for your wallet PIN.

Correction request

Tell us which account detail appears incorrect and what should change. We may ask for a clear account step or verification detail so the request reaches the right record.

HOW WE HANDLE DATA

Privacy Choices Across Your Account Journey

We keep this policy practical by linking each privacy choice to a recognisable account action.

Collection at account opening

When you create an account, we collect the details needed for account access and verification. We also record the device and sign-in event so an unusual attempt can be checked.

Payment reference handling

A DANA, QRIS, bank transfer or virtual account reference helps us match a cashier event to your account. We do not need your wallet PIN to investigate that reference.

Cookies and device settings

Cookies and similar device records can keep a session working and help us recognise repeated access. You can manage browser cookie settings, though disabling them may interrupt account steps.

Account protection steps

We use sign-in checks, verification details and session records to reduce unauthorised account access. Never send your password, wallet PIN or one-time code through a support message.

Retention and deletion

We retain account, support and payment references only while needed for the stated service purpose, security checks or a legal duty. A deletion request may be limited by required records.

Requesting policy changes

To ask for access, correction or deletion, contact us through the support path beside login and identify the relevant account detail. We confirm ownership before applying or sharing a change.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain account records, wallet references, cookies, device access and contact steps without asking you to share sensitive credentials. If your situation is unusual, use the support route beside login and describe only the minimum detail needed.

It covers account details, verification records, device and session data, cookie use, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

A device and session record helps us identify unusual access and investigate login problems. We use it for account protection and service operation, not as a substitute for your password or wallet PIN.

Yes. The policy covers references linked to QRIS, DANA, OVO and GoPay requests. We use visible transaction details to match status, investigate errors and maintain records required by the service or local law.

Use the support link beside the login path and ask for an account-data copy. We first confirm ownership, then explain which records can be provided and any restriction that depends on local law.

Yes. Send a correction request through the account support path and identify the inaccurate field. We may ask for a verification detail before changing contact, account or payment-reference records.

Cookies can maintain your sign-in session and preserve steps between pages on a phone. Browser controls can remove or block them, but some account and wallet-status functions may then require another sign-in.

We remove or anonymise records when they are no longer needed for the stated purpose, security checks or a legal duty. Some payment or support references may remain when retention depends on local law.