Reference

Privacy Policy for ids338 Accounts

Our ids338 Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay or QRIS.

Account recordsCookie choicesWallet detailsPrivacy requests
ids338 Privacy Policy for ids338 Accounts
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should not leave you searching through unrelated account screens.

Privacy request Ask about personal data held for your ids338 account through our privacy contact route.
Wallet question If DANA, OVO, GoPay or QRIS appears beside the wrong account status, contact account…
Login assistance When the privacy request page does not open on your phone, use the account…
WHAT WE PROTECT

Privacy Controls Across Your Account

Privacy choices work best when they match the way you actually use the account. Our handling separates profile records, wallet status, device sessions, cookies, and support correspondence so…

Data collection

We collect information you provide during account creation and verification, then add operational signals such as browser type, device session…

Cookie controls

Cookies can remember a sign-in session, language choice and privacy preference on the browser you use.

Account security

We use account identifiers, verification checks and session signals to reduce the chance that another person reaches your profile.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, status and time record connected…

Retention periods

We retain account, security, payment-status and support records only for the period needed for the stated purpose or an applicable…

Change requests

Where local law permits, you may request access, correction, deletion clarification or limits on certain processing.

Privacy Policy Answers for ids338

These Privacy Policy answers cover the questions we expect before you open an account or connect an Indonesian wallet. They explain the practical route for data access, device sessions, cookies, payment records and account changes. If your situation is not covered, contact us through the privacy path and include only the account detail needed to locate your record.

It covers account details, verification, device and browser signals, cookies, support messages, and payment-status records linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains how to request access, correction or deletion clarification where local law permits.

We collect the details you enter for the account, information needed for account verification, session and device signals, cookie choices, and relevant support or payment references. We do not need your wallet PIN or full banking password to answer a normal Privacy Policy request.

Use the privacy contact route and identify your account with the email or phone detail attached to it. State that you want an access request and name the record categories you need. We may confirm account ownership before sending private data, where local law permits.

Yes. The policy covers payment references, status, timestamps and account links created when you use DANA, OVO, GoPay or QRIS. The payment provider keeps its own wallet credentials, so do not include a PIN, password or full banking login in an ids338 request.

Cookies can keep a session active, remember a selected privacy setting and support the account path you opened in your browser. If you clear them, you may need to sign in again or repeat a verification step. You can ask us about a cookie category before changing it.

Where local law permits, you can request a correction or ask what deletion options apply to a record. Send the account email or phone detail and describe the change. Some security, payment-status or support records may need to remain for a stated operational or legal reason.

Try the same signed-in browser session, then use the account help route if the request page still fails. Tell us your device type, browser and the step where access stopped. Do not send wallet PINs, banking passwords or unmasked payment credentials with the message.