Reference

Open salam jitu Privacy Policy Clearly

salam jitu Privacy Policy explains what we collect when you open an account, how we use device and payment details, and how you can ask us to change…

Account dataWallet detailsDevice choicesPolicy requests
salam jitu Open salam jitu Privacy Policy Clearly
ASK ABOUT PRIVACY

Contact Us About Your Privacy Policy

A clear request helps us locate the right account record without asking you to repeat private details. Use the account help route to raise a Privacy Policy question, identify the relevant activity and tell us what outcome you want. We can then explain the next step for access, correction or removal where the request is allowed. Keep your login details private while contacting us, and use the support path shown after you sign in.

Team online

Data access request

Ask for the personal data connected with your salam jitu account through the account help route. Include your registered contact detail and the records you want checked, such as login events or QRIS activity, so we can narrow the request.

Correction request

If your contact detail or account record is wrong, tell us what needs changing and why. We may ask you to complete the account verification step before editing data connected with DANA, OVO, GoPay or another wallet.

Privacy assistance

When a Privacy Policy question concerns a stalled login or wallet status, use the same support route and mention the device path involved. Our team can separate a data request from a normal account issue without needing your password.

HOW WE HANDLE DATA

Explore Privacy Controls Inside Your Account

We handle Privacy Policy matters through practical account controls rather than vague promises. Login records, wallet references and device activity help us protect an account and investigate a payment path, while your…

Data we collect

We may collect contact details, account credentials, verification information, payment references and technical signals from the phone or desktop used to sign in. For a wallet action, DANA or QRIS activity can help us connect the request to the correct account record.

Why we use it

We use account and device data to create your login path, protect sessions, confirm requested changes and reconcile payment status. A record connected with Live Baccarat or Mega Fishing is handled as account activity, not as a reason to collect unrelated personal details.

Cookies and sessions

Cookies and similar storage can keep a signed-in session working and remember selected account settings. You can adjust browser controls, but blocking required storage may interrupt the path from login to the lobby or require another verification step.

Account security

We use login checks, verification steps and device signals to reduce unauthorised account access. Never share your password or verification code. If your phone changes, sign in through the normal account path and raise a security request before changing wallet details.

Retention approach

We keep records only as long as needed for the stated account, security, payment matching or legal purpose, subject to applicable requirements. When a retention period ends, the data is removed, anonymised or restricted according to our internal handling process.

Requesting a change

To request access, correction, deletion or a restriction where available, use the account help route and describe the record involved. We may verify ownership before acting, because changing a profile or bank transfer reference without that check could affect your account.

Find Privacy Policy Answers Before Joining

These Privacy Policy questions cover the points you are most likely to check before opening an account with salam jitu. We explain what reaches our systems during sign-in, how local wallet records are used, what happens on a mobile device and where to send a request. If your situation is unusual, use the account support route and describe the specific record rather than sending sensitive credentials.

It covers account details, verification records, login and device activity, cookies, payment references, retention and requests about your data. It also explains how we use records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps.

Device signals help us recognise a normal login path, protect your account and investigate an access problem. We may record browser or device details when you move from sign-in to the lobby, but you should not send us your password or verification code.

We use payment references to connect a requested wallet action with the correct account and to check its status. DANA and QRIS activity can therefore appear in account records. We do not treat choosing one rail as permission to use unrelated personal data.

Yes, you can submit a data access request through the account help route and identify the records you want checked. We may verify that you control the account before responding. The available response depends on local law and the type of record requested.

You can ask us to correct inaccurate contact, verification or account details. State the old and requested values without sharing a password. Before changing information linked with GoPay, OVO or a bank transfer, we may complete an ownership check.

We retain information for the period needed for account security, payment matching, stated service purposes or applicable legal requirements. After that period, we remove, anonymise or restrict it according to our handling process. The exact period can differ by record type.

Use the support route shown in your signed-in account and label the matter as a Privacy Policy request. Describe whether you need access, correction, deletion or an explanation. If eligibility or access is discussed, the outcome depends on local law.