Trust and policy · reviewed 14 August 2026
How Local CAMT Processing Works
The public site explains capabilities; the separate workspace parses, validates, exports, and transforms files in the browser.
Separate origins
The public acquisition site and private workspace are separate applications. The workspace has no advertising, third-party analytics, remote fonts, account system, or statement-processing API.
Worker-held data
File bytes, parsed trees, search indexes, comparison documents, and transformation mappings stay inside the dedicated worker and are purged on request or reset.
Honest capability gates
Exact-XSD execution, generated CAMT, MT940-to-CAMT, and semantic repair remain disabled until their schema or profile evidence exists. Comparison, conservative formatting, camt.053-to-MT940, anonymisation, redaction, and lexical repair disclose their assumptions and limitations.