Imported source rows, transaction descriptions, merchant fields, account and IBAN data, filenames, and raw question or conversation history.
A narrow data boundary by design
Raw financial records stay in your browser.
Fain keeps source rows local and sends only approved aggregate results, assumptions, and provenance for hosted narration.
The boundary
Useful narration does not require a copy of your statement.
Fain separates local calculation from hosted language generation. The hosted layer does not become a financial system of record.
A normalized supported intent, approved aggregate results, explicit assumptions, warnings, and versioned provenance.
Authentication, billing, allowlisted measurement, and non-financial operational metadata required to operate the account.
Math before language
Numbers originate in a deterministic engine.
The dashboard and Ask experience use the same versioned calculations. Narration explains approved results; it is not allowed to create a metric.
A cash balance needs evidence
Fain uses a reconciled statement ending balance or asks you to confirm the current balance. It does not infer current cash from transaction net flow.
Runway needs complete periods
Runway is unavailable until a trustworthy cash balance and at least one complete burn period exist. Transfers and financing are excluded from operating flow.
Narration cannot change the chips
Displayed numeric chips come from the engine. Unsupported numerals are rejected, and deterministic wording remains the fallback during provider failures.
Currency scope
USD totals without implied conversion.
Source currencies are preserved locally. Non-USD accounts are excluded from USD totals with a visible warning; currency preservation is not a claim of consolidated foreign-exchange insight.
If browser data is cleared, the local financial records and conversation history can be lost. Export or reset controls remain an important part of customer control.
Measurement boundary
Allowlisted events, not a shadow financial dataset.
Measurement can describe a registered content, call-to-action, plan, supported intent, or usefulness reason. It must not include financial values, filenames, questions, email addresses, account identifiers, full URLs, referrers, or arbitrary text.