Reference

Privacy Policy for Your alexsis17 Account

Our Privacy Policy explains what we collect when you create an alexsis17 account, sign in, use DANA or QRIS, and contact our team.

Account dataWallet recordsCookie choicesAccess requests
alexsis17 Privacy Policy for Your alexsis17 Account
CONTACT ROUTES

Privacy Policy Help Near Login

A clear contact route matters when you want to understand our Privacy Policy or check a record connected with your account.

Account contact Use the contact channel shown beside your account area for a Privacy Policy request.
Wallet record check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment…
Login assistance If Password Reset Help leads to a Privacy Policy question, tell us which device…
DATA HANDLING

Six Privacy Policy Details We Keep Clear

We describe our Privacy Policy in practical terms because your account records can connect login, wallet and device activity.

Account details

We may collect your contact details, account identifier, verification result and sign-in events.

Wallet references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, amount status and time record.

Device signals

When you move from a phone to a computer, we may record browser type, device signals, approximate session timing and…

Cookie choices

Cookies can keep your session connected, remember a selected setting and help us spot repeated security events.

Retention timing

We keep account, payment and support records only while they serve an operating, security or legal purpose.

Change requests

To request access, correction or removal, contact us using your registered account detail and describe the record involved.

Privacy Policy Questions About alexsis17

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain how account data, cookies, wallet records, device access and contact requests fit together. If your case involves a particular DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, include that detail when you contact us. We will use the account path available where local law permits.

It covers data connected with account creation, sign-in, verification, wallet references, device sessions, cookies and support requests. It also explains how to ask for access, correction or removal of eligible records. The policy applies when you use the service where local law permits.

We may collect your contact detail, account identifier, verification result, sign-in events and security signals from the device you use. We collect these details to provide account access, protect sessions, answer requests and connect a payment reference with the correct account.

Yes. The Privacy Policy covers references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. A record may include status, time and reference details needed for account support. Do not send us your wallet password or full security code.

Contact our team through the account contact route and use the phone or email attached to your account. State that you are making a Privacy Policy data request, identify the record you need and complete any identity check required before we discuss private details.

You can request a correction or removal of eligible data through the same contact path. Tell us which record is wrong or no longer needed. We may retain certain account, payment or security records for an operating or legal purpose where local law permits.

Cookies can maintain your session, remember a setting and help identify repeated security events. Your browser lets you accept or block them. Some account functions may behave differently after blocking cookies, and the Privacy Policy explains why each cookie category is used.

We may record the browser, device signals, timing and security result connected with a new login. That context helps us check unusual access. If you used a phone in Bandung and later a computer, mention both devices when asking for a session record.