Advertising and sponsorship policy

AdSense readiness rules

• Google AdSense scripts load only when a valid publisher client id is configured in the Cloudflare Worker environment.
• Noindex pages, API responses, status pages, dataset placeholders, and thin charity profiles do not load advertising scripts or ad slots.
• The /ads.txt endpoint returns a Google seller line only when a real publisher id is configured; placeholder publisher ids are rejected.
• Ads must not cover source links, correction routes, methodology notes, data caveats, or nonprofit benefit eligibility warnings.

Editorial independence

• Advertisers, sponsors, affiliate partners, and software providers cannot change charity metrics, profile indexability, source dates, or relationship signals.
• Nonprofit benefit pages must keep official-source links, verification status, regional caveats, and discontinued-program warnings even when a provider advertises.
• Sponsored placements, if ever added, must be labelled clearly and kept separate from computed rankings, insight tables, and public-register facts.
• The site does not sell favourable charity profile treatment, indexability exceptions, or removal of legitimate public-source caveats.

Acceptable advertising categories

Relevant advertising may include charity technology, compliance tools, fundraising operations, accounting, cybersecurity, cloud services, training, and nonprofit software. Ads for misleading financial products, unsupported grant promises, fake charity verification, or services that obscure official sources should be rejected.

Review and corrections

Advertising concerns can be raised through the contact and corrections routes. If an advertisement conflicts with source integrity, user safety, or charity-data caveats, the policy preference is to remove or block the ad rather than weaken the editorial page.