Reference

salam jitu Privacy Policy Explained

The salam jitu Privacy Policy shows what we collect when you open an account, sign in from a mobile browser, or choose DANA and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
salam jitu salam jitu Privacy Policy Explained
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact route helps when a privacy question appears beside a login or wallet status issue.

Account help path Open account help beside the cashier path when you need to ask about sign-in…
Wallet record check For DANA, OVO, GoPay, or QRIS questions, send the payment reference and date through…
Correction request To request an account-data correction or access copy, use the support link and describe…
HANDLING DETAILS

How salam jitu Handles Policy Requests

The Privacy Policy is practical: it connects your account step, device path, wallet record, and contact request to a defined handling process.

Account creation

We use the details submitted during account creation to establish your account record and complete phone verification before account access.

Mobile browser signals

When you sign in on a phone, we may record browser, device, and session signals.

Cookie controls

Cookies can keep a session active and remember necessary settings.

Wallet separation

A DANA, OVO, GoPay, or QRIS reference helps us match a payment status.

Retention choices

We keep personal and transaction records for security, service administration, dispute handling, or legal duties, then remove or restrict them…

Request verification

Before sharing, correcting, or deleting account data, we may verify that the request comes from you.

Privacy Policy Questions Answered

These Privacy Policy answers address the account and wallet questions you may have before opening an account. We focus on the records you create, the mobile path you use, and the steps available when you want to ask about your data. Where access is discussed, it depends on local law.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use phone verification to confirm account access and help protect sign-in activity. It also lets us identify the correct account when you request a data copy or correction.

No. A payment reference can help us match DANA, OVO, GoPay, or QRIS status, but we do not ask for your wallet PIN, password, or one-time verification code.

Use the support link in account help, state that you want an access request, and identify the account phone number. We may verify your identity before sending the available records.

Yes, send a correction request through account help and name the inaccurate field. We review the account record, may confirm your identity, and explain any restriction that depends on local law.

We retain records for security, service administration, dispute handling, or legal duties. Once the relevant need ends, we remove or restrict the record according to the applicable requirement.

Yes. Contact us through account help with your device and browser details. We can explain necessary cookie use, while your browser settings may limit features needed for sign-in.