Grant evidence pack · for funders

Evidence of community impact — FGCU circle

Prepared for grant applications and funder reviews. Unlike survey-based evidence, every claim below is backed by a recorded, timestamped, auditable event.

Why this evidence is different

• Inspiration is stored as a durable link between acts — the multiplier is measured, not inferred
• Volunteer hours carry a named verifier and an audit record
• Missing data is reported as missing; no imputation anywhere in the pipeline

What funding buys

At the observed 2.4× multiplication, each directly-funded act seeds 1.4 further unfunded acts. The full per-measure dataset accompanies this pack as the National TOMs CSV.

RippleCore grant evidence pack · gep_2026_fgcu · dataset export available on request

Sponsor prospectus · to recruit local partners

Back kindness. Be remembered for it.

RippleCore has no ads. Sponsors are the only brands members ever see — attached to moments of recognition, never to a feed.

How it works

• You fund a small reward (a coffee, a smoothie) — admins award it to recognize real acts
• Your name travels with the recognition: "coffee's on Perk Coffee Co."
• Members redeem in person; you tap once to confirm — that's the whole integration

What you get each quarter

A sponsor summary with issued/redeemed counts, footfall, and the acts your recognition inspired — every number from records you can check against your till.

RippleCore sponsor prospectus · curated community partners only · no feed ads, ever

Safeguarding & privacy assurance · for institutional counsel

Privacy by design, in writing

A one-page account of the controls a safeguarded circle gets, written for the people who must sign off on student platforms.

The controls

• Write-side audience clamp — fails closed: an unknown circle is treated as safeguarded
• Membership-gated visibility — strangers reach an act only if it is public, approved, and in a community circle
• Four map privacy levels — exact / approximate / town-only (default) / hidden; the member chooses
• Quick Acts are private — counted in aggregates, never itemised, even to admins' contributor lists
• Safeguarding is one-way — any admin can raise protection; only a platform admin can lower it
• Everything audited — every admin mutation records actor, IP, and user agent

Cross-boundary rule

Aggregate up, never expose down: rivalries, maps, and reports carry counts and display names across boundaries — never member identities, content, or activity detail.

RippleCore assurance summary · controls enforced server-side and covered by the backend test suite

Circle annual report · cover page

Contents: the numbers · the chains · the people · volunteering · sponsors · what's next