How does the form actually send a message?
This site is static. Submit opens your email client to hello@kodenirlaba.org with the body you typed. If the client does not open, copy the message and send it manually. We do not post a hidden form to a data broker. Your mail server and ours will see the contents like any ordinary email.
Do not paste third-party secrets. If you attach beneficiary data, that is a bad operational signal and we will ask you not to repeat it.
Are there tracking cookies or ads?
We do not place ad pixels. Language preference is not stored in a third-party cookie. Hosting server logs (Cloudflare) may record IPs technically, as other sites do; that is not a marketing profile we build. We do not sell an email list.
If analytics is ever added, this page changes on the same date and consent will be explained. Today that promise is not switched on because the feature does not exist.
How long are messages kept?
As long as needed to reply and to decline or accept into scoping; we do not promise an eternal archive. There is no automatic “download all my data” portal because we are not an account platform. Ask for deletion via the same email; we will delete the application thread we hold.
Partners who later use custom software will have a separate agreement about their operational data. That agreement is not this page.
How do PDP-law rights relate to this site?
If you are an individual in Indonesia sending your own personal data, you may ask to access or delete the application message. We do not process beneficiary data through this public site. This is not legal advice. The text of Law No. 27 of 2022 is in the BPK source linked from the PDP guide.
Privacy contact: hello@kodenirlaba.org. There is no fictional data-protection officer with a title we invented.
What must you not send through this site?
Do not send copies of ID cards, family cards, passports, health data, beneficiary bank details, or spreadsheets of children’s names. This form is a partnership or volunteer application, not a case-referral channel. If you send third-party data, we will ask you to stop and we will delete the copy that reached the inbox we hold.
That bad operational signal also feeds the partnership filter. An organisation used to pasting identity files into a public email is not ready for custom software that stores data more centrally. Fix the habit first; the PDP-law and digitising guides explain the order.
Volunteers sending a portfolio may link public code. Volunteers must not send production data from other jobs. We are not a drop-box for evidence.
Who are the technical processors behind this static site?
Pages are uploaded as static assets. The content network (Cloudflare) may record requests technically. We do not place ad pixels and we do not sell logs. Email you send passes through your mail provider and the hello@kodenirlaba.org inbox. Those are two processors distinct from the site; we do not control your mail provider’s policy.
If an account database, analytics or a donation gateway ever exists, each will be named on this page on the same date. Today none of those three features exist. The absence of an analytics-vendor name is not a trick; the feature is not installed.
Markdown files, the RSS feed and the CSV catalogue are public copies. Do not put personal data in a public Git issue under the guise of a “correction.” A correction needs a URL, a sentence and a source.
How are access or deletion requests handled without an account portal?
Email from the same address as the application, mention the approximate date, and ask for access to or deletion of the thread we hold. We are not an account platform, so there is no automatic download button. We do not promise to delete copies on your mail server or in archives we do not control.
A third-party request about someone else’s data needs a clear basis. We will not hand over an application to a person who merely claims to be “the board” without context we can match to an existing thread.
Rights described in Law No. 27 of 2022 are wider than a website page. This is a channel summary, not legal advice. Read the BPK source linked from the PDP guide if you follow up formally.
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.