Reference

Privacy Policy for Your Indonesia Account

sensa383 Privacy Policy explains what we collect when you open an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet records explainedPhone access controlsIndonesia account context
sensa383 Privacy Policy for Your Indonesia Account
CONTACT PATHS

Privacy Help Through Your Account

A privacy question should not require you to repeat your payment history. Start from your signed-in account help path and include the phone number linked to the account, the subject of your request and any relevant reference without sending a wallet password. We use those details to locate the correct record and limit disclosure to the person who controls the account. If you are in Semarang or elsewhere in Indonesia, the same route applies; access depends on local law and our team may ask for an account check before responding.

Team online

Account help

Use the account help path for a copy of your stored details, a correction request or a question about how your phone verification record is used.

Payment status

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference so we can separate your request from another account.

Access concern

If a login or device concern involves personal data, tell us which device path you used and when it occurred; we may verify account control first.

HANDLING PRACTICES

Security Around Wallet and Lobby Data

We handle privacy as part of the daily account flow, not as a separate message after payment.

Account details

We collect information you enter for account creation and phone verification, then use it to provide access, answer requests and keep the correct account tied to its activity.

Cookies and devices

Cookies and device signals can remember a signed-in path, protect sessions and show whether a request came from a familiar browser. You can manage browser cookie settings on your device.

Wallet references

DANA, OVO, GoPay and QRIS references help us match payment status with your account. We do not ask support conversations to contain your wallet password or security code.

Account security

Phone verification, session checks and login records help us investigate unusual access. If you change devices, we may ask for an account detail already held before discussing private records.

Retention periods

We keep account, payment and security records only as long as needed for the stated service, dispute handling, security checks or legal duties where local law permits.

Your changes

You can ask us to correct inaccurate details, explain a data use or provide an account record through support. We assess each request against identity, security and local legal requirements.

Privacy Policy Answers for sensa383

These Privacy Policy answers focus on the account questions you may search before opening access from Indonesia. They cover the details collected during phone verification, the payment references created by DANA or QRIS, cookies on a mobile browser, correction requests and account closure. For a request tied to a specific record, use the signed-in help path so we can check account control without exposing private data.

It covers details you submit for an account, phone verification records, device and login events, cookies, payment references and support requests. It also explains why we use those records, how security checks work, how long records may remain and how you can ask for access or correction.

We may collect your name, phone number, verification result, contact preferences, device details, login events and account activity. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may receive a payment reference and status rather than your wallet password.

Your phone number supports account creation, phone verification, login checks and help with account control. It can also help us connect a payment status to the correct account. We use it for those stated purposes and may retain related records for security or legal duties where local law permits.

Yes. Send the request through the signed-in account help path and describe whether you need a copy, correction or explanation. We may ask you to confirm account control before releasing details, especially when the request concerns a DANA, QRIS, login or phone verification record.

Cookies can keep a browser session connected to your account, support security checks and remember limited access settings. A mobile browser may show a different device signal after clearing cookies or changing networks. You can manage cookies through your browser settings, though some account steps may then need repeating.

We use DANA, OVO, GoPay and QRIS references to match a payment request with its account status. Bank transfer and virtual account confirmations serve the same operational purpose. We use these records for reconciliation, support, security and permitted legal duties, without asking for wallet passwords.

Open the account help path and state the request clearly, such as access, correction, deletion or a question about a specific record. Include your linked phone number and reference where relevant, but do not send a wallet password. We may verify account control before discussing private data.