AI4Love Trust Center v2.6

Last updated: March 25, 2026

This is the canonical reference for how AI4Love handles your data, makes decisions, and behaves when things break. It is written for IT, privacy, and procurement teams evaluating AI4Love for their organization.

If you need a PDF, use your browser's Print function (Ctrl+P / Cmd+P). The page is formatted for clean export. The PDF is a snapshot; this URL is the source of truth.

---

What AI4Love Does Not Do

Before explaining what the system does, it is more useful to state what it will never do:

• No data custody. AI4Love does not operate an independent database of your supporter data. Your records live in your Airtable base. We read them to generate insights, then write those insights back to the same base. We don't maintain a copy, a replica, or a warehouse.
• No automated outreach. AI4Love does not send emails, texts, or messages to your supporters. It surfaces recommendations. Your staff decides what to act on.
• No autonomous decisions. The system detects patterns and writes text. It does not approve campaigns, move money, change records, or take action on anyone's behalf.
• No black box. Every insight traces to a specific agent, a specific rule, and specific input data. If you ask "why did the system say this?", the answer is auditable.

---

What AI4Love Does

AI4Love is a relationship intelligence layer for nonprofit organizations. It reads your existing supporter data (donations, volunteering, event participation, communications), runs it through deterministic analysis agents, and surfaces actionable insights for your development team.

The system is designed around three principles:

1. AI does not act. Humans act. The value is insight quality, not volume. Suppression over noise.
2. Your data stays in your house. We provide tools and insights. You own the house and everything we add to it.
3. Deterministic core, generative surface. Pattern detection is rule-based math. Only the final insight text is LLM-generated — and even that is constrained by templates and validation.

---

Data Classification

AI4Love processes supporter engagement data: donation history, volunteer activity, event participation, and communication records.

AI4Love does not require and does not process:

• Protected health information (PHI)
• Financial account numbers, credit card data, or banking details
• Government-issued identifiers (SIN, SSN, driver's licence)
• Biometric data

If your Airtable base contains fields outside the engagement data scope, AI4Love applies allow-list field filtering before passing data to any sub-processor (see AI Behavior).

---

Trust Anchors

Principle	What It Means
Zero Custody	No independent data store controlled by AI4Love. All supporter data resides in your dedicated Airtable base.
Read-Only Integrations	We never write back to Blackbaud, Mailchimp, or Environics. Data flows one direction.
Per-Org Isolation	Each organization gets its own Airtable base, its own credentials, its own access keys. No shared tenancy at the data layer.
No AI Training	Neither Anthropic nor OpenAI uses your supporter data to train their models. API-tier usage only.
Immediate Revocation	Disconnect any integration or user from the dashboard. Takes effect on the next request.
Deterministic Analysis	Pattern detection is math — rollups, formulas, thresholds. Not LLM inference.

---

Navigation

Section	What You'll Find
System Architecture	Exact data flow diagram. What connects to what and why.
Data Handling	Zero custody, credential storage, encryption, residency, retention.
AI Behavior	How agents work, what the LLM does and doesn't do, data minimization.
MCP Access Model	How AI assistants query your data — tools, filtering, rate limits, audit trail.
Security Controls	Auth, access model, rate limiting, internal access.
Failure Modes	What happens when things break. Suppression, fallbacks, incident response.
Changelog	Real system updates. Not marketing.
Requests & Contact	SOC 2 reports, pen test results, DPA templates.