Reference

Open salamjp Privacy Policy Before Account Access

Our Privacy Policy explains what we collect when you open a salamjp account, check Andar Bahar or Fishing God, and use DANA or QRIS from an Indonesian device.

Account dataWallet recordsCookie choicesContact requests
salamjp Open salamjp Privacy Policy Before Account Access
CONTACT OPTIONS

Reach Us About Your Privacy Policy

A clear contact path helps you ask what data is held, why it is used, or how an account record can be corrected. Use the support route connected to your salamjp account and include the phone number on file, the relevant date and the specific Privacy Policy request. For wallet questions, a receipt or status reference helps us locate the right record without requesting your wallet password.

Team online

Account access desk

Ask about phone verification, sign-in records or a device entry through account help. We use the account details you provide to locate the Privacy Policy request and may ask for an account check.

Wallet status route

For DANA, OVO, GoPay or QRIS records, send the transaction reference and date rather than wallet credentials. We can check whether the account record matches the payment status shown to you.

Receipt request path

If a bank transfer, virtual account or QRIS receipt needs clarification, contact us from the account path. Keep the reference visible, while removing unrelated card, bank or wallet details.

DATA PRACTICES

Explore salamjp Data Handling Choices

We keep this Privacy Policy practical: account records support access checks, payment references help reconcile wallet status, and device signals help identify unusual sign-in activity.

Account details

We use the phone number and verification result you submit to connect account access with the right profile. Please tell us if your number changes so the record can be corrected through the account path.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help match a transaction with your account. We do not need your wallet password to investigate a receipt or status question.

Device activity

Sign-in time, browser type and device signals can be used to spot an unfamiliar account entry. If you see an access record you do not recognise, contact us from your account route.

Cookie controls

Cookies can keep a session open and remember selected settings on mobile or desktop. You can adjust cookie controls in your browser, although disabling them may affect account access and policy preferences.

Retention checks

We retain account, verification and transaction references only for the operational, legal or dispute-handling period that applies. A removal request may be limited where an active record must still be kept.

Change requests

Ask us to access, correct or clarify your personal data through account support. Include the requested change and phone number on file; we may verify ownership before changing or sharing a record.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers cover the account, wallet and device questions you may have before opening access. If your case involves a specific receipt, phone verification result or unfamiliar sign-in, use the account contact path with the relevant reference.

It covers account details, phone verification, device and sign-in records, cookies, payment references and contact requests connected with your salamjp account and access where local law permits.

We use the verification result to connect account access with the correct profile and help address sign-in questions. It also gives us a practical way to check an account change request.

Yes. The policy covers transaction references and status details connected with DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity, but not your wallet password.

Contact us through the account support route, state which record is incorrect, and include the phone number on file. We may verify account ownership before applying a correction.

We may use sign-in time, browser type and device signals to connect sessions with your account and identify an unfamiliar entry. These details support access checks rather than wallet-password collection.

Retention depends on the purpose and any applicable legal or dispute-handling requirement. Account, verification and transaction references may remain while an account or related payment matter needs to be resolved.

Yes. You can ask how cookies or account data are used and request removal where local law permits. Some records may need to remain when an active account or transaction requires retention.