Reference

Privacy Policy for semar123 Account Data

Clear handling of account, wallet and device data is the purpose of semar123 Privacy Policy: we explain what we collect when you create an account, verify your phone…

Account recordsWallet referencesDevice choicesPrivacy requests
semar123 Privacy Policy for semar123 Account Data
PRIVACY CONTACT

Account Help For Privacy Requests

A clear contact path helps when you want to ask about a record, correct an account detail or understand a wallet reference. We connect privacy questions with the account-help route so you can provide the relevant phone number, request type and payment reference without repeating unrelated account activity. Use the route shown on this page and keep your request limited to details needed for verification.

Team online

Account access request

Ask us to confirm which account details are linked to your phone verification. We may request an account step before discussing records, so private details are not disclosed to another person.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date rather than wallet credentials. We use those details to locate the relevant payment record and explain its status.

Correction request

If your phone, device or account detail needs correction, tell us which field is wrong and why. We will use the account-help route to assess the request and respond with the next step.

SECURITY PRACTICE

Device Security And Account Records

We apply this Privacy Policy to the practical moments that matter: account creation, phone verification, mobile access, wallet matching and requests to change stored details.

Account security

Phone verification helps us connect an access request with the correct account. We may use device and login signals to identify unusual access, while keeping the purpose tied to account protection.

Cookie choices

Cookies can remember session settings and help us understand whether a page loads correctly. Our Privacy Policy explains their role, and you can review available browser controls before continuing.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference records. We use those references to match status with the right account, not to request wallet passwords.

Mobile devices

Opening the lobby from a mobile browser may provide device and session signals needed for access continuity. Our policy explains this use without treating your handset as a separate account.

Retention choices

We retain account, payment and support records for the period needed for stated service, security or legal purposes. The policy route lets you ask which category a particular record belongs to.

Policy changes

When our data handling changes, we place the revised Privacy Policy at the policy route and identify the update clearly. You can contact us if a change affects your account choices.

Privacy Policy Questions For Indonesia

These answers address the Privacy Policy searches we expect from Indonesian account holders. They cover the records created by login, phone verification and local payment references, along with requests to access, correct or question data. If your situation is not listed, use the privacy contact route and describe the specific record involved.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect an access request with the correct account and reduce mistaken disclosure. The Privacy Policy explains the purpose and the account step used before private details are discussed.

Yes. The Privacy Policy covers the transaction references and status details needed to match DANA and QRIS activity with your account. It does not require you to send wallet passwords through support.

You can use the privacy contact route to ask what account records are held about you. Include the relevant phone number and request type; we may verify account control before responding.

Describe the incorrect field, such as a phone or account detail, through the correction route. We may ask for an account step before changing records so the request comes from the account holder.

We keep payment references for the period needed for service, security or legal purposes. The exact category can depend on the record, and you can ask us to explain its retention basis.

Yes. Access and related account handling depends on local law and is provided where local law permits. Our policy contact route can explain which request process applies to your location.