Reference

sis4d Privacy Policy for Your Account

Clear privacy choices help you understand what happens when you open an account, check DANA or QRIS status, and use our mobile lobby.

Account clarityWallet contextMobile accessPolicy requests
sis4d sis4d Privacy Policy for Your Account
REQUEST HELP CLEARLY

Contact Us About Privacy Policy

A clear request helps us locate the right account record without asking you to send unnecessary personal details. Use the contact route shown in your account area and tell us whether your question concerns login data, a DANA receipt, a QRIS reference or a cookie choice. We will use the details you provide to assess the request and respond through the available account contact path.

Team online

Account data question

Ask which account details we hold by including your registered phone number and the specific record you want clarified. Do not send a password, wallet PIN or full payment credential with your request.

Wallet record concern

For an OVO, GoPay, DANA or QRIS status concern, include the date, amount shown in your account and the payment reference visible to you. This lets us separate a wallet record from unrelated account activity.

Privacy change request

To request correction, access or removal of eligible data, describe the change in plain English and complete the account confirmation step we request. We may need to verify control of the account before acting.

HOW WE HANDLE DATA

See How Privacy Policy Works

Privacy controls work best when each account step has a defined data purpose. We separate login and verification records from wallet status checks, keep support access limited to the request being handled…

Account collection

When you open an account, we collect the details needed for account access and phone verification. Login records help us connect a request to the correct account while keeping the account path clear on mobile and desktop.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account can help us identify a requested transaction. We use those references for status checks rather than exposing your wallet credentials.

Cookie choices

Cookies and similar device storage can keep a session active, remember a selected page and help us detect technical faults. Your browser settings can restrict them, although some account steps may then need to be repeated.

Device protection

We may assess browser, device and login signals when access looks unusual. This can trigger an account confirmation step, helping us protect your details without treating a familiar device as permanent proof of identity.

Retention approach

We retain account, payment and support records only for the operational, dispute, security or legal purpose described in the policy. When a record is no longer needed for those purposes, our process addresses its removal.

Your request route

You can ask for access, correction, clarification or removal of eligible personal data through the account contact route. We may confirm account control first, then explain the action taken or any legal reason it cannot proceed.

Ask About sis4d Privacy Policy

These Privacy Policy answers focus on the questions that usually arise before account access. We keep the wording practical, so you can understand how account records, wallet references, cookies and data requests connect to your use of sis4d in Indonesia.

The sis4d Privacy Policy covers account and phone verification details, login and device signals, cookies, support messages, payment references and the ways we use, retain and protect those records.

We use the phone number connected to your account for the clear verification step before account access and for account support. It also helps us identify the correct record when you request a privacy change.

Yes. The Privacy Policy explains how DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account status, may be used to match a requested payment record.

You can request access to eligible personal data through the account contact route. Include the registered phone number and the type of record requested, then complete any account confirmation step we require.

Send a correction request through the displayed account contact route and identify the inaccurate field. We may confirm account control before changing the record, then explain the result under the Privacy Policy.

Cookies can maintain a session, remember a page choice and help identify technical faults on mobile. Browser controls can restrict them, but you may need to repeat login or verification steps.

The policy page is intended to explain our data handling, while account access, processing and particular requests depend on local law. Where local law permits, use the account contact route for assistance.