Reference

alsitoto Privacy Policy For Your Account

Our alsitoto Privacy Policy explains what account, device, wallet and support details we collect, why we use them, and how you can ask about them.

Account dataWallet recordsCookie choicesPrivacy requests
alsitoto alsitoto Privacy Policy For Your Account
HELP WHEN NEEDED

Get A Clear Privacy Request Path

A privacy question should not disappear inside a general account conversation.

Account access request If your phone verification or browser session shows the wrong account detail, tell our…
Wallet record question For a DANA, OVO, GoPay or QRIS reference, share the transaction date and visible…
Policy clarification Ask which data purpose, cookie setting or retention step applies to your account.
ACCOUNT DATA CARE

Keep Your Privacy Choices Understandable

Privacy works best when each account step has a clear reason. We separate sign-in protection, wallet matching, device checks and support records, while cookies help remember selected settings on the browser path.

Data handling

We use phone, account and transaction references for stated operational purposes such as verification, wallet matching, security checks and responding to your privacy request.

Cookie settings

Browser cookies can remember practical settings and help connect a session to your account. You can ask us which cookie purpose applies before changing your browser choices.

Account security

Phone verification helps confirm account access, while device signals can help identify unusual sign-in activity. Never share your password or one-time code through a message.

Retention process

We retain account, wallet and support records only as long as needed for security, dispute handling and legal duties, then remove or restrict them under our process.

Correction request

If your phone number, account detail or transaction reference is inaccurate, send a request through support with enough context for us to locate the record.

Access request

You can ask what personal data we hold, why it is used and whether a restriction or deletion request applies. We may verify account ownership first.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the account and wallet questions we expect you to ask before opening access. We keep the wording practical: what we collect, how browser activity is handled, how a request is verified and where local law affects the response. If your case involves a specific DANA, OVO, GoPay or QRIS reference, include that context through our support path.

It covers account details, phone verification, device and browser signals, cookies, wallet references, support messages, security use, retention and requests to access, correct or restrict your data.

Phone verification connects you with the correct account record and helps protect the sign-in path. We may ask for an ownership check before discussing or changing account data.

No. Our policy concerns payment status and reference details returned through the account flow. We do not ask you to send a DANA, OVO, GoPay or QRIS password.

Cookies can remember browser settings and help associate a session with your account. You can ask which cookie purpose applies, then adjust browser choices or request further clarification.

Yes, you can send an access request through the privacy support path. We may verify account ownership, then explain the available records and any restriction required by local law.

Contact support with the incorrect detail and the matching account context. For a wallet reference, provide its date and visible reference rather than a password or verification code.

You may ask for deletion or restriction, but some records can remain for security, dispute handling or legal duties. The response depends on local law and the record involved.