ProofGive: Give Openly, Without Exposing Who You're Helping
# ProofGive: a donation tracker that protects the people it's helping Submission for the DEV Weekend Challenge: Generosity Edition · #weekendchallenge What I built ProofGive is a small giving ledger I built

# ProofGive: a donation tracker that protects the people it's helping
Submission for the DEV Weekend Challenge: Generosity Edition · #weekendchallenge
What I built
ProofGive is a small giving ledger I built for Kar Se Khar, an NGO I'm part of back home. It has two views: a public donor view showing exactly how much came in, how much went out, and to how many people — and an admin view where our team logs donations and distribution batches. The twist is what stays out of the public view: real beneficiary names and per-person amounts never get published, stored in the app's state, or sent anywhere. Only the aggregate numbers do.
On top of that ledger, Google's Gemini API writes a short, plain-language transparency report straight from the public numbers, and answers donor questions through a small Q&A box — always sourced only from what's actually published. If someone asks something the ledger doesn't cover, like a specific beneficiary's details, it says so plainly instead of guessing.
Why I built it
Charity has a trust problem in both directions. Donors often have no way to verify their money did what it was supposed to. NGOs, meanwhile, sometimes over-correct by publishing more personal detail about the people they're helping than those people ever agreed to — which trades one harm for another. I wanted to see if I could give an NGO a way to be radically transparent about outcomes without being invasive about individuals.
This also isn't hypothetical for me — Kar Se Khar is an NGO I actually volunteer with, so this is something I'd genuinely like to keep using and improving past the weekend.
How the privacy split works
Every donation and every distribution batch (a label, a beneficiary count, a total) is public by design — that's what accountability requires. But the moment someone on our team types real beneficiary details into the private notes field, that text is read only to confirm the field isn't empty; its content is never stored in the app and never leaves the browser. Gemini only ever sees the redacted, aggregate ledger — it's structurally incapable of leaking a name it was never given.
Tech
Plain HTML/CSS/JS, no backend or database — the ledger lives in the page's memory for the session and Gemini handles the report writing and Q&A. Built this way to enter the Best Use of Google AI category.
What I'd build next
Move the API key behind a real backend instead of the browser, add proper authentication for the admin side instead of a shared passcode, and eventually let the ledger persist across sessions instead of resetting.
Try it
- Source: github/Arbaz-Shahbaz03/Proofgive-Karekhar
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.
