Reference

alexsistoto Privacy Policy, Clearly Explained

The alexsistoto Privacy Policy shows what we collect, why we use it and how you can ask us to correct or remove eligible details.

Account clarityWallet contextLocal access rulesDirect requests
alexsistoto alexsistoto Privacy Policy, Clearly Explained
REQUEST HELP

Privacy Questions Reach Our Account Team

A clear request helps us locate the right account record without asking you to share unnecessary secrets. Use the support route shown inside your account help area, especially when a login, wallet status or receipt check is connected to your privacy question. We may ask for an account identifier and verification detail before discussing personal data.

Team online

Account privacy request

Ask us to access, correct or clarify personal details through the account help path. We use the account identifier you provide to locate the relevant record before responding.

Wallet record question

If your question concerns DANA, OVO, GoPay or QRIS references, include the transaction date and visible status. Please do not send a password or full wallet security code.

Security concern

For suspected account misuse, contact support through the signed-in help area and change your account password. We can review session and device records linked to the reported event.

HANDLING DETAILS

Six Practical Privacy Commitments

Privacy work is part of the account flow rather than a separate promise. We separate identity details from payment references where operationally possible, restrict internal access and retain records only for a…

Account data

We use your account details to create access, confirm a phone step, protect sign-in activity and respond to requests. We do not need your password when handling a privacy enquiry.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us match payment status. We use transaction references and outcomes for reconciliation rather than requesting wallet passwords.

Cookies and sessions

Cookies or similar storage can remember a session, security preference or page setting. On mobile, clear them in your browser privacy controls if you want to remove local session data.

Security checks

A phone verification step can be required before account access, and unusual sign-in activity may trigger additional checks. These controls help us separate your account from an unauthorised session.

Retention approach

We keep records for as long as needed for account operation, payment matching, security review or a legal obligation. When a record is no longer needed, our process removes or de-identifies it.

Changing your details

You can ask us to correct eligible account details through the support route in your account area. We may verify ownership first, then explain any field that cannot be changed immediately.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions we expect before an Indonesian customer opens an account or checks a wallet record. If your situation is not covered, use the account support path and describe the specific data or access issue without sending confidential credentials.

It explains how we use account identifiers, phone verification results, sign-in records and security details to provide access, protect the account and respond to your requests. We avoid collecting unrelated details.

Yes. Send a correction request through the support path inside your account area. We first confirm account ownership, then update eligible details or explain why a particular record must remain unchanged.

Yes. The policy covers payment references and status records connected with DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account matching. We do not ask for wallet passwords.

We may use device and session details to keep a signed-in visit working, identify unusual access and protect account activity. You can clear browser cookies and site storage from your device settings.

We retain records while needed for account operation, payment reconciliation, security checks or legal duties. After that purpose ends, the record is removed or de-identified under our retention process.

Use the signed-in account help route and state that you want a copy or explanation of your personal data. Include your account identifier, but never include your password or wallet security code.

Yes. Account access and eligibility depend on local law or apply where local law permits. Our support team can explain the account request path, but cannot change a local legal restriction.