UKU - Pinjaman Dana Digital

Opening the app and the first hurdle

Downloading UKU from the Play Store takes about a minute. The app size is around 80 MB. Opening it for the first time, the user is greeted with a registration screen. The app asks for a phone number, full name, and ID card (KTP) details. The interface is clean and uses Indonesian throughout. There is no language toggle. The app assumes the user is Indonesian. The registration flow is quick. The user fills in personal data, takes a photo of their ID, and submits the application. The app requests camera, microphone, and location permissions during this process. These permissions are presented as requirements for identity verification. The user must grant them to proceed. The app claims to be OJK licensed and AFPI member, displaying logos prominently. This builds initial trust. The user selects a loan amount between 500,000 and 30,000,000 IDR and a tenure of 90 to 180 days. The app shows the interest calculation. For a 1,000,000 IDR loan over 90 days, the interest is 62,876 IDR, making the total repayment 1,062,876 IDR. The user submits the application. Then the first hurdle appears. The app performs an automated verification. Many users report being rejected within seconds, even after filling all data correctly. The rejection is instant and unexplained. The user is left with no feedback on why they were rejected. This is the onboarding reality: quick registration, quick rejection, and no path forward.

The app's approval process is opaque. The user who is approved receives funds within 24 hours. However, the amount disbursed often does not match the application. Users report receiving significantly less than expected. The app deducts fees upfront. The Play Store description says "no hidden fees," but users describe first installments that are nearly 98% of the loan amount. This is the central friction point. The app presents itself as a transparent, OJK-regulated platform. The actual experience for many users is a confusing process with unexpected deductions and unresponsive customer service.

How OJK licensing and upfront fees create a financial trap

The app prominently displays its OJK license number (KEP-46/D.05/2021) and AFPI membership. These credentials are meant to signal safety and legitimacy. The app also claims ISO/IEC 27001:2022 certification for data security. These are real regulatory achievements. However, the user complaints reveal a different story. Multiple users report that the funds disbursed are much lower than the approved amount. One user reported receiving only 680,000 IDR on an approved loan, with no explanation. Another user noted that the first installment was nearly 98% of the total loan amount, meaning the user effectively receives almost nothing after the first payment. The app charges interest upfront. The Play Store description states "maximum service fee will not exceed 25.5% per year." This sounds reasonable. But the actual deduction structure is not clearly explained. The user is told they are approved for a certain amount. They receive a smaller amount. They are then expected to repay the full amount with interest. The regulatory framework—OJK license, AFPI membership—creates a false sense of security. The user assumes the app is safe because it is regulated. The regulation does not prevent the app from using aggressive upfront deduction structures. The original analysis here is that the OJK license and AFPI membership are used as marketing tools to build trust, while the actual loan terms create a financial trap. The user who needs quick cash may not read the fine print. The app's terms and conditions are available on the website, but they are not presented prominently during the application process. The user who is approved and receives less than expected has limited recourse. Customer service is often unresponsive. One user reported contacting CS multiple times with no response. The app's legitimacy is real, but the user experience is predatory.

The app's data collection is another concern. The app requests camera, microphone, and location permissions. The privacy policy states that data is encrypted in transit and users can request deletion. However, the app also shares device IDs and other data with third parties. The user who is rejected still has their personal data stored. The app does not provide a clear data deletion process. The user who is approved has their data shared with collection agencies. The app's data practices are not fully transparent. The user who is concerned about privacy may find this troubling. The app's security certifications are real, but they do not address the financial and data risks.

Real-world performance: bugs, crashes, and the update cycle

The app's version history shows frequent updates. Version 6.9.21 was released in December 2024 with a size of 50.8 MB. Version 7.0.6 was released in April 2026 with a size of 80.8 MB. Version 7.0.14 was released in April 2026 with a size of 82.6 MB. The app size has increased significantly. The changelog for these versions is consistently vague: "Perbaikan bug dan peningkatan kecil" (Bug fixes and minor improvements). The user has no idea what specific issues were addressed. The app's performance on different devices is unknown. The app requires Android 4.4+ for older versions and Android 8.0+ for newer versions. This is a reasonable requirement. The app should work on most modern devices. However, users report occasional crashes and freezes during the application process. The app's interface is functional but not polished. The user who encounters a crash during the application submission may lose their progress and have to start over. The app does not save draft applications. The user must re-enter all data. This is a significant friction point. The app's performance is adequate for a financial app, but the user experience is not optimized for mobile. The app feels like a web form wrapped in a mobile interface. The user who expects a modern fintech experience may be disappointed.

The app's customer service is another weak point. Users report long response times and unhelpful support. The app provides WhatsApp numbers and a phone number for support. However, users describe being ignored or receiving generic responses. The app does not have an in-app chat feature. The user must contact support through external channels. This creates additional friction. The user who has a dispute about fees or disbursement has limited options. The app's terms of service include a clause that holds the user responsible for all activity on their account. The user has no direct recourse if a dispute arises. The app's legal structure is designed to protect the company, not the user. The user who is unhappy with the service may file a complaint with OJK. However, this process is slow and uncertain. The app's real-world performance is acceptable for basic functionality. The real issues are policy and transparency.

Permission model: what the app actually accesses on your device

The app requests three main permissions: camera, microphone, and location. The camera is used for ID verification. The user must take a photo of their KTP and a selfie. The microphone is used for voice verification or customer support calls. The location is used for fraud prevention and to verify the user's address. The app's privacy policy states that these permissions are necessary for identity verification and security. The app does not request access to contacts, storage, or SMS. This is a positive sign. The app's permission model is focused on what it needs to function. The user who is uncomfortable with location tracking may still need to grant it to proceed. The app does not offer a reduced-permission mode. The user must accept all permissions or not use the app. The app's data collection is extensive. The privacy policy states that the app collects personal information, location, and device IDs. This data is shared with third parties for analytics and fraud detection. The user can request data deletion, but the process is not clearly documented. The app's security certifications (ISO/IEC 27001:2022) provide some assurance that data is handled securely. However, the user must trust the developer. The developer, PT Teknologi Merlin Sejahtera, is based in Jakarta and appears to be a legitimate company. The company has been covered by Indonesian media. The app's legitimacy is not in question. The question is whether the user is comfortable with the data collection and the financial terms. The user who values privacy may find the permissions acceptable. The user who is concerned about data sharing may be wary. The app's permission model is standard for a fintech app in Indonesia. It is not excessive. It is appropriate for the app's function.