Reference

Privacy Policy for Your kilat365 Account

kilat365 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse Dragon Tiger or use DANA and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
kilat365 Privacy Policy for Your kilat365 Account
PRIVATE HELP ROUTES

Get Privacy Help Beside Your Account

A direct support request gives you a clear route when a privacy question is tied to login, a wallet reference or a device session. We ask for enough account detail to locate the request, but never ask you to send a password or one-time verification code. When you contact us about Privacy Policy, include the email or phone linked to your account and the action you want us to take.

Team online

Account access

If you cannot reach your account after phone verification, contact support through the account help route. We can check the access record, explain what data was used and tell you which step is needed without asking for your password.

Wallet privacy

For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference and approximate date through support. We use those details to locate the record while avoiding unnecessary wallet credentials or unrelated account data.

Data request

Ask to access, correct or remove eligible account data through our support path. State your preferred contact route and the specific record involved, such as a device session, cookie choice or bank transfer reference.

DATA CONTROL LAYER

What Privacy Controls You Receive

Privacy controls work best when each account step has a clear purpose. We separate sign-in security from wallet matching, use cookies to remember selected settings, and keep transaction…

Collection purpose

We collect contact details for account opening and phone verification, plus technical details such as browser type and sign-in time.

Cookie choices

Cookies can remember a selected language, sign-in setting or page preference on your device.

Account security

Phone verification is required before account access, and we use session details to identify unusual sign-in activity.

Retention approach

We keep account, support and payment references only as long as needed for account administration, dispute handling, security checks or…

Correction requests

If your phone number, contact detail or account record is wrong, send a correction request through support.

Policy contact

Privacy questions can be raised through the same support route used for account help.

Privacy Policy Questions About kilat365

These Privacy Policy answers address the searches we hear most often about account data, cookies, wallet records and access. Each answer points you toward a practical next step, whether you are checking a phone verification record, using a mobile browser in Denpasar or asking for a change to your stored details.

The Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use each category, how long records may be retained and how you can request access, correction or removal where applicable.

We use phone verification before account access to confirm that the sign-in step belongs to you and to help protect the account. The related record may include a verification result and time. We do not need your password or one-time code in a support request.

Yes. The Privacy Policy includes payment references and status details returned through DANA, OVO, GoPay and QRIS, as well as bank transfer or virtual account references. We use them to match an account request, investigate a status and handle a payment query.

Contact us through the account support route and ask for a data access request. Include the contact detail linked to your account and describe the records you want, such as sign-in history, cookie settings or a QRIS reference. We may verify ownership first.

You can request a correction or ask whether removal is available for a specific record through support. Tell us which detail is affected and why. Some account, security or payment records may remain when needed for disputes, protection or a valid legal request.

The same Privacy Policy applies when you sign in from a phone browser, tablet or desktop. We may record device type, browser path and session time to protect access. Cookie settings can be changed in your browser, although some account preferences may need repeating.

Yes. Access and eligibility depends on local law. Our Privacy Policy still explains data handling for an account request, including phone verification, device records and wallet references. If you need clarification about a local access question, contact support with your location and account step.