Reference

pin4d Privacy Policy for Your Account

Our Privacy Policy explains what pin4d collects when you open an account, sign in from a mobile browser, check wallet status, or contact support.

Account dataCookie choicesWallet recordsAccess requests
pin4d pin4d Privacy Policy for Your Account
CONTACT YOUR WAY

Get Privacy Help Beside Account Support

A clear contact route helps when you want to ask about a cookie, correct an account detail or question a wallet record.

Account support path Open support from your signed-in account and choose the privacy request route. We use your account identifier to locate the relevant record, while you should never send a password, wallet PIN or complete card credential.
Payment record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, provide the transaction reference and date. We can check the stored status without requesting your wallet password.
Access without login If the login screen blocks your request, use the contact route shown on the privacy page and state that you need a data access or correction request. Share a reachable contact detail, not secret credentials.
CONTROL YOUR RECORD

Account, Cookie And Device Controls

Our Privacy Policy gives you practical controls rather than a general statement. You can review the account details attached to your sign-in, adjust cookie permissions in your browser, and ask support to…

Account security

Before account access, we may use phone verification to connect a sign-in with the correct account. Keep your verification code private, and contact support if a code arrives when you did not request one.

Cookie settings

Cookies can remember a session and support security checks between the login page and your account area. Use your browser settings to remove or restrict them; some account steps may then need to be repeated.

Mobile browser signals

When you move from a phone login to the lobby, we may record browser type, device signals and session times. These details help identify unusual access and are handled under this Privacy Policy.

Payment matching

A wallet or bank reference helps us connect a payment request with your account and resolve a status question. We record the transaction details needed for that purpose, not your DANA, OVO or GoPay secret.

Retention periods

We keep account, support and transaction records for as long as needed for account operation, dispute handling and applicable legal duties. When a record is no longer needed, our retention process removes or restricts it.

Changes to your data

Ask us to correct an inaccurate name, phone detail or account record through support. We may verify the request against the account before making a change, so one person cannot alter another account.

Privacy Policy Questions From Indonesia

These answers cover the requests we expect when you check the Privacy Policy before opening an account. They explain the data connected with sign-in, mobile access, cookies and local payment records, while support can handle a request that needs account-level checking.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone detail for account identification and the verification step before account access. It helps connect the correct person with a sign-in and helps support locate the right account.

Yes. When you sign in from a phone, we may handle browser type, device signals and session timing for account security. The same Privacy Policy applies whether you use a phone or desktop.

We may store a payment reference, amount, time, account identifier and status supplied by DANA, OVO, GoPay, QRIS, a bank transfer or a virtual account. We do not need your wallet password.

Use the privacy contact route in account support and ask for a data access request. Include your account identifier and reachable contact detail; we may verify ownership before sharing account records.

Yes. Send a correction request through support and identify the detail that is inaccurate. We may ask for an account check before changing a phone number, name or related record.

Retention depends on the purpose of the record, such as account operation, payment disputes or legal duties. We remove or restrict records when the applicable retention need has ended.