Security & data

Tamper-evident, but open

Sealed documents, open formats

Every Standard Document FinStat produces — statement, chart, or declaration — is sealed: canonical JSON content plus a content hash plus a FinStat seal. Change one character and the seal breaks; verification reports it as a normal verdict, not a crash, and an edited or foreign-sealed document is refused at submission.

The same documents are deliberately open. The canonical schemas are published (guide_canonical_schema), any document opens to its complete reviewable JSON (open_standard_document), statements render to presentation PDFs and export to QuickBooks, OFX, CSV, Xero, and Sage formats. Your evidence is portable: any FinStat system can reproduce the books from the documents alone. Tamper-evident is not locked-in.

Every number has a basis

The books are not a text completion. They are a projection of admitted evidence: source document → statement rows → derived events → chart postings, each step recorded and traceable back to the page it came from. Submissions are atomic and stamped with a basis digest; a batch either admits whole or is refused whole, with item-specific reasons.

• Documents that do not reconcile are refused, with the reason named.
• Ambiguity becomes a review item for a human decision — FinStat does not quietly guess, and an empty review list is honest about being no assurance by itself.
• Balanced entries and source-tied numbers are properties of the engine, enforced by law checks, not conventions a long conversation can erode.

Access and isolation

• OAuth 2.1 sign-in: discovery, dynamic client registration, authorization code with PKCE. No shared API keys.
• Workspaces belong to the principal who created them; metered work in a workspace bills its owner and nobody else sees it.
• Source bytes are retained for provenance and re-download by their workspace, and their retention state is always reported truthfully (list_source_documents).
• Operational surfaces describe your books, not our infrastructure: status and processing reports never expose internal queues, hosts, or providers.
• See the privacy policy and subprocessor list for the data handling details.

Hard boundaries

FinStat records, reconciles, and reports. It does not move money, hold funds, or connect to payment rails. Destructive operations are explicitly annotated in the tool catalog; reads are read-only and marked so.