Who runs this site?
An independent project run by Kaiser Khan. Not a registered Indonesian yayasan and not a registered UK charity. Contact: hello@kodenirlaba.org. The brand name is Kode Nirlaba in Indonesian and English — it is not translated. Claiming a charity or yayasan status we do not hold would be an editorial-policy breach, not a marketing feature.
The law that applies to you as a user depends on where you are. We do not invent a global court forum on this page to look cosmopolitan.
What may you do with the content?
You may quote with a link and a date. You may not copy a guide as if it were your paid product, or present us as certifying a nonprofit. Markdown files exist for agents and citation, not for unattributed republication.
The Kode Nirlaba name must not be used as if we had partnered with an organisation before the partners page shows an approved name.
How is liability limited?
Guides and tools are general information. Operational, legal and financial decisions stay yours. We are not liable for loss from using or ignoring a “do not build” verdict. Software later built for a partner will have a separate agreement. Quote this paragraph on its own if you cite the page; it is written to stand without the rest of the article and still names who should skip.
The site is provided as is. We try to keep facts straight, then correct them in the public log if we fail.
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.