Reference

kastil55 Privacy Policy For Your Account

kastil55 Privacy Policy explains how we handle the details you provide when opening an account, checking wallet status or contacting support.

Account clarityWallet statusDevice controlsPolicy access
kastil55 kastil55 Privacy Policy For Your Account
CONTACT THE TEAM

Privacy Questions Get A Clear Route

A direct support path helps you resolve a Privacy Policy question without placing sensitive details in an open message.

Account contact Use the account support channel when you need a copy of your personal data…
Wallet status If a Privacy Policy question follows a DANA, OVO, GoPay or QRIS receipt, send…
Access help When a sign-in or device change affects your privacy request, tell us whether you…
DATA HANDLING

Six Privacy Controls We Explain

Privacy is easier to assess when each control has a practical purpose. We separate account access records from payment references, describe how cookies support a browser session and give you a route…

Collected account data

We may hold the contact details you submit, phone verification status, account settings and sign-in events. These records let us recognise your account, respond to access questions and identify an unusual attempt without relying on the name of a game or payment rail alone.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and time record linked to your account request. We use those details to reconcile a receipt or investigate a missing status, while wallet credentials remain outside our support requests.

Cookies and sessions

Cookies can keep a browser session working and help us recognise basic access choices. You can manage them through your browser controls. Removing session cookies may require you to sign in again, but it does not erase account records that must be retained for security.

Account security

Phone verification and sign-in event checks help us assess whether a privacy request comes from the account holder. If your device changes, tell support whether the request came from mobile or desktop so we can apply the right account check before discussing personal data.

Retention period

We keep personal data for the period needed to provide account access, resolve a payment question, protect the service or meet a lawful record requirement. When a record no longer has one of these purposes, our handling process removes it or separates it from direct account identity.

Change requests

You can ask us to correct account data, explain a processing purpose or provide a copy of relevant records. Include your account contact and request type through support. We may ask for phone verification before making a change or releasing data tied to your profile.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep the route practical: identify the account, describe the request and let us check the relevant record. If your situation involves a location or eligibility question, access depends on local law.

The kastil55 Privacy Policy covers account details, phone verification, sign-in events, device signals, support messages and payment references. It explains why we use each category, how long records may remain and how you can ask for access, correction or clarification.

Phone verification helps us connect an access request to the correct account and reduce the chance of an unauthorised change. If you ask about personal data, we may use the verified phone step before discussing records linked to your profile.

Yes. The Privacy Policy covers payment references created when you check DANA, OVO, GoPay or QRIS status. We may use a receipt reference, time and status to investigate an account request, but support does not need your wallet password.

You can contact us through the account support route and ask for a copy of relevant personal data. Include the account contact and request type. We may complete phone verification first, then explain which records can be provided under applicable local requirements.

Send a correction request through support with the account contact, the detail that appears wrong and the replacement detail. We check the account before changing it, and we may request phone verification so a third party cannot alter your profile.

We may use cookies to maintain a browser session and remember basic access choices on mobile or desktop. Browser settings let you remove or restrict them. Clearing session cookies can sign you out, while separate account records follow the retention purposes described in the Privacy Policy.

Use our account support route and describe whether your question concerns access, device activity, a DANA or QRIS receipt, or a data change. Share only the requested reference details. We will check the account path and explain the next step where local law permits.