Why Indonesia, rather than a global marketplace?
Because the legal, language and operating context for Indonesian nonprofits is specific: yayasans, NGOs, the PDP law, and work that often runs on WhatsApp. Indonesian is the primary language because it is the working language of partners. English is a toggle for international volunteers and donors, not a default that field staff must absorb.
Many “global pro bono” projects write in English and hope partners adapt. We reverse that. Verdicts, forms and guides are written first for Indonesian users.
The geographic focus is also a capacity filter. We do not pretend we can support organisations on every continent. If you are outside Indonesia and your need is not about operations in Indonesia, we will almost certainly decline.
What will you not claim about impact?
We will not invent beneficiary counts or volunteer hours. The partners page lists live public-interest sites and states honestly that they are not Indonesian yayasans. Impact we publish is only what a public source dated, without turning it into an advert.
The standard feels strict because it is. Nonprofit sites often copy the language of large institutions before the work exists. We refuse that pattern. An empty slot is more trustworthy than a fictional case study.
When a number appears, it will carry a source and a capture date. If we do not know, we write that we do not know.
How does the mission run without yayasan status?
As Kaiser Khan’s independent project, with volunteers, without claiming a legal status we do not hold. Partners keep ownership of their data and their mission decisions. We are not your board, not your counsel, and not a donation channel. If you need an intermediary legal body, that is not us.
Status honesty matters more than looking “official.” A false yayasan or charity claim is a defect, not marketing. See the note in the footer of every page.
Volunteer funding does not buy editorial verdicts in the guides. The guides name when a free tool wins, even if that means we build nothing.
How should a board use this page in one meeting?
Read the short answer first, then the skip box, then the tables. If the verdict is “do not apply” or “do not build,” stop the meeting there. Do not send beneficiary data because this page exists. Bring the matching tool if you need the same test in interactive form. Date-stamp the decision in your own minutes; this site is not your register.
A board meeting does not need every paragraph. It needs a decision: apply, wait, or use an off-the-shelf tool this week. Print the filter table if there is one. Name a data owner out loud. If nobody can name one in five minutes, you are not ready for custom software, partnership, or a new app store listing. That pause is cheaper than a demo.
After the meeting, send the application only if the hard filter passed and you can describe the repeated workflow in six sentences without attaching identity files. If you were declined, keep the written reason. It is usually “a free tool already fits” or “finish domain email first.” Those are operational instructions, not insults. Re-apply when the facts change, not when the branding mood changes.
Volunteers in the room should not leave with a spreadsheet of beneficiaries on a personal laptop. The privacy policy and the PDP-law guide exist for that moment. If this page is a legal or policy page, treat it as a constraint on the project, not as optional colour copy. Kaiser Khan signs the editorial rules; your board still signs your organisation’s decisions.