Legal

Trust and Compliance

Effective Date: July 3, 2026

This page explains how ALFRED™ approaches trust and compliance — how the platform uses artificial intelligence, how readiness and verification rules are applied across ALFRED’s Small Business, CDFI, and Lender platforms, and how state assignments and file actions are tracked for review.

ALFRED is built on a simple governing principle: platform intelligence carries the logic of theP3 Framework™ through Readiness Intelligence™ It does not replace the decision authority of the lenders, CDFIs, or capital providers ALFRED serves.

ALFRED’s AI layer interprets, translates, and drafts within bounded system rules. It does not make underwriting judgments, policy exceptions, or autonomous release decisions.

Section 1

Responsible Use of AI

ALFRED uses artificial intelligence in specific, bounded ways to support the P3 Framework™ and Readiness Intelligence™:

  • Translating readiness findings into plain-language guidance
  • Supporting ALFRED Chat responses based on current file status
  • Summarizing available file information
  • Flagging changes in submitted, uploaded, connected, or public information that may require review

ALFRED Chat is a conversational interface, not an autonomous agent. It responds to user questions and may reference current file status, but it does not initiate actions or make decisions on a user’s behalf.

Section 2

Readiness State Logic

Readiness State is determined through ALFRED’s defined readiness logic, not by predictive or generative AI. It is the governing readiness output across ALFRED’s Small Business, CDFI, and Lender platforms.

In ALFRED’s Small Business platform, the Readiness Index presents both the readiness score and Readiness State together so a business can understand its current standing and progress.

A completed verified file is assembled only after required verification is complete, the applicable capital path is accepted, and the user authorizes submission. No file is transmitted to a lender, CDFI, or capital provider without that approval.

Section 3

CDFI Compliance and Dual-Gate Review

For institutional deployments, ALFRED enforces a dual-gate compliance review before any capital opportunity is surfaced to a user:

  • Target Market alignment — checking whether the business appears to align with a CDFI’s defined Target Market criteria
  • Minimum product eligibility — identifying whether the business appears to meet a program’s baseline eligibility parameters

Compliance is treated as a product attribute, not a universal gate — logic parameters are scoped to each institution’s specific programs. ALFRED’s engine structure remains constant across institutions; only program logic parameters change.

Section 4

Exception Handling and Safe Mode

ALFRED maintains a defined path for handling disputes, sync failures, contradictory data, or unexpected system behavior:

  • The affected automated action is paused pending review
  • Manual review is required before the action resumes
  • The outcome is added to the audit log
  • The prior file version is preserved where applicable

When ALFRED detects an anomaly, unexpected output, unauthorized write attempt, or policy conflict, Safe Mode may be triggered. In Safe Mode, ALFRED may continue to read and log activity, but external transmission, partner sync, and state advancement are disabled until a documented review restores normal operation.

Section 5

Data Isolation and Access Boundaries

ALFRED maintains defined access boundaries across user files, connected data, institutional programs, and capital provider information:

  • ALFRED operates only within the user’s authorized file, connected data, and engagement context.
  • ALFRED does not access, infer from, or apply information outside the user’s authorized record set when determining readiness or producing guidance.
  • Institutional program data is institution-bound and is not surfaced outside that institution’s implementation.
  • Capital provider identity is not exposed to the user before the user selects or accepts a surfaced capital opportunity.
Section 6

Audit Logging

ALFRED logs consequential readiness, verification, communication, and file-action events so institutional administrators can review activity for compliance, reporting, and operational oversight.

Action What Is Logged
State assignment Timestamp, reason codes, gate status, and engine version
Verification event Source reviewed, verification status, timestamp, and result
Readiness guidance generated Reason codes used, generation timestamp, and output reference
State regression Previous state, new state, triggering data change, and timestamp
Failed gate attempt Missing fields, reason codes, and timestamp of blocked advancement
Submission authorization User approval, destination selected, timestamp, and file version
Partner transmission Recipient institution, transmission timestamp, and confirmation status

For CDFI-related institutional deployments, audit logs and supporting records may be retained for a minimum of five years to support compliance, reporting, and review requirements. Records may be made available for institutional review or regulatory examination where required.

Section 7

No Financing Guarantee

ALFRED does not guarantee, promise, or imply approval for any financing product, loan, line of credit, or capital instrument. Readiness State, Readiness Index, and the completed verified file are indicators of readiness and preparation — not commitments to funding. All financing decisions remain the exclusive authority of the relevant lender, CDFI, or capital provider.

Contact

compliance@getalfredapp.com

ALFRED™ is a trademark of Fintech Reimagined LLC. All rights reserved.