Reference

salam555 Privacy Policy: DANA, QRIS and Device Access

Clear account, wallet and device rules help you understand what happens when you open salam555 from Medan or elsewhere in Indonesia.

Account dataWallet recordsDevice accessPolicy requests
salam555 salam555 Privacy Policy: DANA, QRIS and Device Access
REQUEST A HAND

Privacy Requests Beside Wallet Support

A clear support route matters when you want to ask about a Privacy Policy request, an account record or a wallet receipt. Start from the support path linked with your salam555 account and include the phone number or account identifier connected with your request. If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, tell us the payment rail, date and visible status so we can locate the correct record without asking you to send an unnecessary password.

Team online

Account privacy

Use the account support path to ask what personal details are connected with your salam555 access. We may ask you to complete a phone verification step before discussing account-specific records.

Wallet record

For a DANA, OVO, GoPay or QRIS question, include the rail and receipt reference visible to you. We use those details to match the request with the right wallet event and avoid exposing another account's data.

Change request

Ask us to correct an account detail through the same support route. We check the request against your account access before changing a phone, contact detail or other record held under your profile.

DATA HANDLING

Live Blackjack Prestige Data Path

The Privacy Policy is practical: it explains what we collect, why we use it and how you can ask about it.

Account details

We may hold the phone number, account identifier and verification result used to connect you with your account. These details support sign-in checks and help us respond to a request about your own records.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can show a rail, reference, amount status and timing. We use these fields to trace a receipt or resolve a wallet-status question.

Cookies

Cookies and similar browser storage can preserve a session choice or help us understand whether a sign-in is continuing on the same device. You can manage browser permissions, though some account steps may then need repeating.

Account security

A phone verification step may be required before account access or before we discuss private records. Device and login signals can help us identify unusual activity around the lobby, wallet page or support path.

Retention period

We keep personal and payment records only for the period needed for account service, security checks, payment questions and applicable requirements. When a record is no longer needed, our handling follows the policy and relevant law.

Your request

You can ask what data we hold, request a correction or ask about deletion where the law allows it. Send the request through account support with enough detail for us to identify your profile safely.

Privacy Policy Questions for salam555

These Privacy Policy answers cover the searches we hear most often before account access. They explain how salam555 treats identity details, payment records, cookies, devices and requests for changes. If your question concerns a particular DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry, include its visible reference when you contact support so we can check the relevant record.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, payment records and requests about your data. It also explains why we use those records, how long we may retain them and how to ask for access or correction.

Yes. The policy covers records connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account paths. We may use a receipt reference, timing and wallet status to match a payment question with your account.

Depending on the account step, we may handle your phone number, account identifier, verification result, sign-in details and support messages. Device type, browser signals and login timing may also be recorded to protect access and connect activity with the right profile.

Use the support path connected with your account and clearly ask for access or correction. Include your account identifier and the specific record you mean. We may complete a phone verification check before sharing or changing account-specific data.

Cookies or similar browser storage can keep a session choice and help us recognise whether a sign-in continues on the same device. You can adjust browser permissions, but turning them off may require you to repeat an account or verification step.

We retain payment and account records for the period needed to provide account service, check security, answer receipt questions and meet applicable requirements. The exact period can depend on the record and applicable law, as described in the Privacy Policy.

Yes. Contact account support and mention the device type, approximate sign-in time and account identifier. We can use those details to discuss an access record without asking you to send a password or private wallet credential.