Reference

kasteltoto Privacy Policy For Your Account

Clear handling for your DANA, QRIS and account details is the purpose of the kasteltoto Privacy Policy.

Account data explainedWallet records clarifiedMobile access coveredPolicy requests welcome
kasteltoto kasteltoto Privacy Policy For Your Account
PRIVACY HELP

Contact Us About Privacy Access

A clear support path helps when your account record, wallet status or personal details need attention. Use the support route shown inside your kasteltoto account and describe the specific Privacy Policy request, such as correcting a phone number or checking a DANA reference. We may ask for account details needed to locate the record, never your wallet password. From a phone or desktop, keep the relevant page open so the request can be matched accurately.

Team online

Account access

Tell us if the phone verification step prevents access to your account. We use the account identifier and relevant device details to locate the privacy request without asking for your wallet password.

Wallet records

For DANA, OVO, GoPay, QRIS or bank transfer questions, include the transaction reference shown in your account. This lets our support route separate a payment-status query from a data correction request.

Policy requests

Ask for a copy, correction or clarification through the account support route. State what should change and why, so we can assess the request under the Privacy Policy and local rules.

DATA PRACTICES

See How We Handle Account Details

We keep this policy practical: the details gathered during account opening should have a clear purpose, a defined access path and a way for you to ask questions.

Data we receive

We may record account identifiers, phone verification results, device signals, lobby activity and payment references. These details help connect a session with the correct account and investigate an unusual access or wallet status.

Cookie controls

Cookies and similar device storage can remember session settings and help us understand which account page loaded. Your browser controls can manage or clear them, although clearing cookies may require another login.

Account security

Phone verification is used before account access, while device and session checks can help identify an unexpected sign-in. Never send a wallet password or one-time code through a support request.

Record retention

We retain account and transaction records only for operational, dispute, security or legal needs described in the Privacy Policy. Retention can vary by record type and requirements that apply to your access.

Changing your details

If your phone number, account name or contact detail is wrong, request a correction through support. We may verify ownership first so a third party cannot alter your account record.

Who receives data

Access to relevant records is limited to operational needs, such as matching a QRIS reference or resolving account security. We do not ask external contacts to handle your request outside our support route.

Find Privacy Policy Answers

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. If your situation is not covered, use the support route inside your account and describe the exact record or request.

It covers account details, phone verification, device signals, cookies, lobby activity, payment references and requests to correct or access records. It also explains retention, security handling and local-law conditions.

Do not send a DANA or QRIS password to us through chat. The policy concerns transaction references and status details needed to match your account, not your private wallet credentials.

Phone verification helps connect account access with the person opening the session. We may use its result as an account-security signal, especially when a device or login pattern needs checking.

Yes. Use the support route inside your account, name the incorrect detail and explain the requested change. We may verify account ownership before updating a phone number or contact record.

Cookies or similar storage can retain a session setting and help load the correct account page on your phone. Browser controls can clear them, but you may need to verify access again.

Retention depends on the record type and the operational, dispute, security or legal reason for keeping it. The Privacy Policy does not treat every wallet reference as having the same retention period.

You can ask through the account support route and identify the request by its account or transaction reference. We will explain the applicable handling path, subject to local law and account-security checks.