AI.FO

AI.FO TRUST

What we can honestly claim, and what we can't yet

This page states the truthful subset of AI.FO's trust posture: only what is currently true and currently verified, framed exactly the way it was verified. Where a claim is not yet true or not yet verified, we say so below rather than imply it.

Open the product demoHow verification works

WHAT IS TRUE TODAY

Six claims, each checkable and each framed the way it was verified rather than rounded up to sound stronger than the evidence supports.

ISOLATION

Cross-tenant isolation is enforced and was live-verified

Access to another tenant's data is fail-closed by construction: a request for a foreign tenant's target gets the same response shape whether that target exists or not. A live cross-tenant probe found no leak.

TENANCY

Tenancy is server-derived, not client-selected

Which company's data a request can touch is decided from the authenticated session on the server. Client input is never trusted to select the tenant.

DENIALS

Denials are evidence-backed

Access denials are written to an append-only denial ledger, so a refused request leaves a durable record rather than disappearing silently.

SOURCING

Every signal traces to a sourced methodology

Each signal's threshold cites a published methodology. A fabricated-citation guard and a constants audit run in CI to keep that sourcing honest as new signals ship.

VERIFICATION

The engine is re-verified nightly, independently

An independent, fail-closed verifier re-runs the engine every night. The current run's status is public at /proof, with figures derived from committed artifacts anyone can recompute.

INGESTION

Ingestion is read-only

Connecting QuickBooks Online uses an OAuth authorization that we access on a read-only basis; we do not write to your QuickBooks data. CSV upload is a user-initiated action, not a background pull.

WHAT WE DO NOT CLAIM

Said plainly, not implied by omission

What we claim

  • App-layer tenant isolation, live-verified with a cross-tenant probe
  • An independent, fail-closed engine re-verification, every night
  • 48 deterministic financial signals, each tracing to a sourced methodology

What we do not claim

  • No claim about what a model provider does with your data beyond generating your brief
  • No promise about how long any data is kept or when it is removed
  • No claim that isolation happens at the database layer; the isolation described above is enforced in the application layer
  • No outside body has reviewed or backed this page; these six items are self-reported and independently checkable, not sealed by a third party
  • No implication that any given company's signals all apply; which ones fire depends on that business

This list is deliberately conservative. As a claim above becomes true and verifiable, it moves out of this list and into the "what is true today" section, with the same standard of evidence.

HOW THE MATH IS VALIDATED

AI.FO connects to QuickBooks Online and validates the numbers behind every signal before any narrative is written. See how verification works for the three-stage, fail-closed path a number takes before it reaches a founder, and the nightly proof page for the standing archetype coverage guarantee and the live telemetry ledger behind it.

GET STARTED

See it against a real, simulated dataset for Integra Executive Services, our public demo company, or connect your own QuickBooks Online account.

Open the product demoGet access