Reference

kira505 Privacy Policy For Your Account

kira505 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account detailsWallet recordsDevice accessPolicy requests
kira505 kira505 Privacy Policy For Your Account
CONTACT PATHS

Use The Privacy Support Route

A clear contact path helps you raise a Privacy Policy question without repeating your account story across several teams.

Policy request Send your question through the policy contact route linked in the account area. Include your registered contact detail and the change, access, correction or deletion request you want us to assess.
Login concern If a phone verification step or sign-in record looks unfamiliar, tell our support team through the account help path. We can compare the device event with your account details before discussing the record.
Wallet record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the visible reference and status only. We use that detail to locate the relevant payment record without requesting your wallet PIN.
DATA CONTROL

Browse How We Handle Your Privacy

Privacy work is part of the account path, not a separate promise placed away from the cashier.

Account data

We collect details you provide during account opening, including contact data and phone verification results. We use them to create the requested account record, support sign-in and respond to a Privacy Policy request.

Payment references

A DANA, OVO, GoPay or QRIS action can produce a reference, amount status and time record. Bank transfer and virtual account checks use comparable references to match the correct account activity.

Cookies and devices

Cookies and device signals can keep a session connected, remember security choices and help identify unusual sign-in behaviour. You can clear browser data, though doing so may require phone verification again.

Account security

We use phone verification before account access and may compare sign-in device details when a request looks unusual. Never send us your password, wallet PIN or a complete payment credential.

Retention

We retain account, payment and security records only for the operational, dispute, legal or policy purposes described in this Privacy Policy. When a record is no longer needed, our process removes or de-identifies it.

Change requests

To request access, correction, deletion or a copy of eligible data, contact us through the policy route and identify your account. We may ask for a safe account check before changing personal details.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers cover the account actions Indonesian customers ask about most often. They explain what we need for phone verification, why wallet references appear in records, how device access is treated and where to send a request before you open an account.

The kira505 Privacy Policy covers account details, phone verification, sign-in devices, cookies, lobby access records, payment references, retention and requests to access, correct or remove eligible data.

We use phone verification to connect account access to the correct contact detail and reduce mistaken or unusual sign-ins. The verification result can remain in the account security record under this Privacy Policy.

Yes. The Privacy Policy covers reference details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, including status and timing used to reconcile your account.

We may record device and browser signals, sign-in time and session details needed for access security. Clearing browser data can remove a session setting and may lead to another phone verification step.

You can ask for access to eligible account data through the policy contact route. Provide your registered contact detail and request scope; we may complete an account check before responding.

Send a correction request through the Privacy Policy contact path and identify the detail that needs changing. We may ask for phone verification or another safe account check before editing the record.

Yes. Account access and related data handling depend on local law and apply where local law permits. If eligibility differs for your location, contact us through the policy route before opening an account.