Explain legacy code in plain language for Nonprofit

You are an expert in this kind of work, and you know the Nonprofit sector from the inside.

## Your task
I inherited this code at a nonprofit organisation funded by donors and grants and need to understand it before changing it. Explain what it does step by step in plain language, list its inputs, outputs and side effects, point out anything risky or outdated, and suggest where a test should go first.

## About my situation
- Who this is for: donors, volunteers and beneficiaries
- What we must respect: limited budgets, grant terms and transparency to donors
- How we measure success: donor retention and cost per beneficiary

## What matters in Nonprofit
- Rules and standards that usually apply: charity registration and reporting (12A/80G and FCRA in India, 501(c)(3) in the US); grant terms and restricted funds; donor privacy; safeguarding of children and vulnerable people; transparent use of funds.
- Common risks to plan for: funding gaps; donor fatigue; compliance lapses; mission drift; damage to reputation.
- Tools commonly used: Google Workspace; a donor CRM; Canva; crowdfunding platforms.
- Words people in this field use: grant; CSR; impact report; theory of change; restricted and unrestricted funds; M&E; beneficiaries.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
Code:
[PASTE CODE]

## How to work through it
1. Give a one-paragraph summary of what the code does and why it probably exists.
2. Walk through it step by step in plain language.
3. List inputs, outputs, side effects and external dependencies.
4. Flag risky, outdated or confusing parts.
5. Suggest the first test to write and the safest first change.

## What to deliver
- Plain-language summary
- Step-by-step walkthrough
- Inputs, outputs and side effects table
- Risk list
- Where to start

## Rules
- Make every point specific to my situation and my industry; replace generic advice with detail that fits.
- Use plain language, short sentences, and tables where they make the answer easier to scan.
- Use only the facts I give you. Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- It is written for a nonprofit organisation funded by donors and grants; nothing in it would read the same for any other business.
- Nothing in it breaks limited budgets, grant terms and transparency to donors.
- Every item under "What to deliver" is included.