Reference

semar500 Privacy Policy for Your Account

Our semar500 Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA and QRIS for a transaction.

Account dataWallet recordsCookie choicesAccess requests
semar500 semar500 Privacy Policy for Your Account
PRIVACY HELP ROUTES

Contact Us About Your Privacy Policy

A clear contact path helps you ask about a record without exposing your account details in a public message.

Account contact route Open the support area after login and select the privacy request path.
Payment record check For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, share the transaction…
Access assistance If login stalls on a phone or desktop, contact support through the account help…
DATA CONTROL DETAILS

Explore How semar500 Handles Your Data

Our handling process follows the account journey rather than treating every record alike. Login and verification details support account security; payment references help us reconcile status; cookie controls support the browser session.

Account security

We use account verification and sign-in signals to help identify unusual access. Keep your login details private, and contact us through the account route if a phone or desktop session does not look familiar.

Cookie controls

Cookies can remember session choices and help us understand page performance. Your browser settings provide a way to remove or restrict them, although some account pages may then need another sign-in.

Payment records

A wallet or bank transaction record normally contains a reference, rail, amount, time, and status. DANA, OVO, GoPay, QRIS, and virtual account entries help us answer cashier-status questions.

Data access

You can ask for a copy or explanation of personal data connected with your account. Include your linked contact detail so we can check identity before discussing private records.

Corrections

If your contact detail or account record is inaccurate, tell us which field needs changing and why. We may request an account verification step before applying a correction.

Retention questions

We keep data only for its stated operational purpose, account support, disputes, or applicable legal duties. Ask through the privacy route which category and retention reason applies to your record.

Browse Privacy Policy Questions

These answers address the Privacy Policy questions we expect you to ask before opening an account. They cover account access, device data, cookies, Indonesian wallet references, correction requests, and the steps for contacting us about your personal records.

The semar500 Privacy Policy covers account details, sign-in and device signals, cookies, verification status, payment references, retention, access requests, corrections, and contact steps for your personal records.

We use transaction details such as the rail, reference, amount, time, and status to reconcile payments. We do not need your DANA or QRIS wallet password to display that status.

Device and login signals help us recognise the account session, support sign-in checks, and investigate unusual access. They can be created when you move between a phone and desktop browser.

Use the privacy contact route in your account support area, identify the email or phone linked to your account, and ask for the categories or records you want us to locate.

Yes. State which account field is inaccurate and provide the corrected detail through the privacy route. We may complete an account verification step before changing information tied to your access.

Cookies can retain session choices and help measure page performance. You may restrict or remove them in your browser, but account pages may ask you to sign in again afterward.

Access and eligibility depends on local law. Where local law permits, this Privacy Policy applies to the account, device, cookie, and payment records created through your semar500 access.