NGO Analytics
Subprocessors
Vendors that can see Grant Ops or Fiscal Sponsor OS customer content, credentials, or production infrastructure. Last updated 31 August 2026. We update this page before a new vendor receives production customer content. Notice: [email protected].
| Vendor | Use | Region | Customer content |
|---|---|---|---|
| Supabase | Auth, Postgres, Storage | Hosted project (supabase.co) | All tenant data, files, and authentication |
| DigitalOcean App Platform | Next.js app and daily retention job | NYC | Request traffic and runtime secrets |
| Cloudflare | DNS; Email Routing for security@ | Global edge | Mail envelope to [email protected] |
| GitHub | Source and deploy from main | United States | Source code, not the tenant database |
| Optional OAuth sign-in | United States | Email and profile if the user chooses Google | |
| Stripe | Subscriptions and payment methods | United States | Billing email, card last4, customer and subscription IDs |
| Resend / Amazon SES | Transactional send on send.ngoanalytics.com | us-east-1 | Addresses and body when we send product email |
Optional: an LLM only if a workspace admin enables it. Drafts stay in a human review queue. The vendor contract must forbid training on that content. Not a second system of record. Consumer ChatGPT / Claude.ai are not used.
Out of boundary: Lovable hosts ngoanalytics.com only.
Request a DPA or inherited host SOC 2 reports (where the vendor allows) at /dpa.