Sponsor / donor
Sponsor a child privately
Start the donor-side relationship. You support Four Hunger, then receive private reviewed updates through secure links.
Compounding Love access layer
One promise outside. One governed system underneath.
Donors should feel a simple path to help. Operators should get a simple path to record truth. Reviewers should have clear authority before private updates or public proof go out.
Access rules
Clear boundaries by role.
Sponsors
Private updates only for their own secure links.
Field operators
Can submit check-ins and evidence, not publish.
Reviewers
Can approve media, messages, and proof readiness.
Founders/admins
Can manage records, communications, and publication.
Choose the right path
Different people need different doors.
Field team
Submit a monthly check-in
Windell or a pod leader records child rows, meal notes, attendance, and optional sponsor-only media for review.
Reviewer / admin
Review before anything leaves
Zach or a second reader checks evidence, privacy, consent, media, and the public proof boundary before approval.
Participant organization
Join the proof network
For organizations that want this trust layer: start with standards, roles, evidence boundaries, and a pilot workflow.
Operating thesis
The public promise is only as strong as the private process.
This is why the software cannot just be a donation page. The management side is the guarantee: consent, evidence, media review, sponsor privacy, publication boundaries, and an audit trail.
01Public site explains the human promise.
02Stripe creates the sponsor/payment event.
03Field workflow records monthly operational truth.
04Reviewer approves media, message, and proof boundaries.
05Sponsor receives secure private updates.
06Public sees aggregate proof, never public child profiles.
Demo-ready next step
Walk Zach through both sides together.
Show the sponsor checkout first, then the operating dashboard: pod check-in, media review, secure sponsor update, and public aggregate proof.
Auth: Supabase magic links for operators and reviewers.
Sponsor access: secure token links, not public accounts yet.
Org onboarding: request access before multi-tenant automation.