Reference

klik365 Privacy Policy For Your Account

Our Privacy Policy explains what data we collect when you open a klik365 account, use DANA or QRIS, browse the lobby, or contact support.

Clear data purposesWallet record checksAccount access controlsPolicy request path
klik365 klik365 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Privacy Policy

A direct support route helps you understand a data question without explaining your whole account history repeatedly. Use our website support channel for requests about access, correction, deletion or a copy of your records. Include the account phone number and the subject of your request, but do not send a wallet password or one-time code. Our team handles account and payment-status questions during the published support hours, and we can ask for a verification step before discussing private account data.

Team online

Account data request

Send a request through the website support channel when you want to see, correct or delete account data. We first confirm that you control the account, then explain which records can be changed and which must remain for legal or transaction reasons.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrect, share the transaction reference through support rather than posting it publicly. We compare the wallet record with the account ledger and tell you what data was checked and what action is available.

Access concern

When a login or phone verification stalls, contact support from the account page and describe the device path you used. We may request a fresh verification step, but we will not ask for your password or one-time code through an open chat.

HANDLING DETAILS

How klik365 Handles Account Data

Privacy depends on practical controls, not only a page of legal wording. We separate account details from routine device signals where our systems allow, restrict internal access by work need, and record…

Account details

We use your account contact details to create the profile, complete phone verification and send replies about account access. Keeping your phone number current reduces failed checks. You can ask support to correct a detail after we confirm the account belongs to you.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us trace a cashier request. We use it to reconcile status and investigate a missing record, while the wallet provider remains responsible for data held on its own service.

Device signals

Browser type, device category, session time and security events can help us detect an unusual login or diagnose a page failure. These signals are not a substitute for identity checks, and support may ask you to repeat phone verification before changing access.

Cookie choices

Cookies can preserve a login session, remember a page setting or help us measure a technical fault. Your browser lets you remove or block them. If you block essential cookies, the account page may ask you to log in again or may not retain a selected setting.

Retention periods

We keep account, security and transaction records for as long as needed for the purpose collected, then review whether deletion is appropriate. Some payment or access records may need a longer period where local law permits or requires that record to remain.

Change requests

To request a copy, correction, restriction or deletion of personal data, contact us through website support with a clear request. We verify the requester, explain any limits, and confirm the result through the account contact path rather than an unverified address.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account and wallet questions you are most likely to have before opening or using your klik365 profile. They explain the practical request path, the data linked to DANA and QRIS activity, and the checks used when you ask us to change private records. If your situation is not listed, contact website support with the smallest useful set of account details.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security access and the route for requesting changes.

We use your phone number to create or locate your account, complete the phone verification step and respond to account requests. We may use it to confirm that a person asking about private data controls the account. We do not ask for your one-time code in support chat.

Yes. The Privacy Policy covers payment references that reach our account records from DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account matching details. The relevant wallet or bank also has its own terms for data held on its service.

You can request a copy or correction through the website support channel. Tell us whether the request concerns your profile, phone verification, device record or payment reference. We verify account control first, then explain the available action and any record that must remain.

We retain data for the operational, security, support or legal purpose for which it was collected, then review it for deletion or further retention. Transaction and access records may remain longer where local law permits or requires. Support can explain the category involved.

Use your browser controls to remove or block cookies, then contact website support if you need help understanding a session record. Cookies can support login continuity and fault diagnosis. Blocking essential cookies may require another login or affect account-page settings.

Yes. Requests, account eligibility and the extent of data access depends on local law. We assess your request against the rules applicable to your location, verify account control, and explain clearly if a legal or transaction record cannot be removed.