Built like the records it keeps.
A wealth file holds the softest data a firm touches inside the hardest regulatory frame. The architecture answers were made before the features were.
Row-level security enforced in the database. Agent access through a narrow tool surface with per-firm vault tokens. Collectors are read-only by construction — they can fill the systems column, never write a note.
Quotes verified deterministically — string-match with stored character offsets, not model self-grading. Nothing overwritten, ever. Facts that fail verification are held in the open.
Advisor export in documented JSON/CSV — contractual, verifiable quarterly. Firm export and escrow on termination. Transcripts never train shared models.
What we will put in writing
The export clause
Advisor-authored notes are exportable at any time, in documented JSON/CSV, attributed, without vendor approval or fees. Verifiable quarterly by the customer.
The escrow commitment
Full firm data escrowed with an independent agent. On termination or vendor failure, the escrow releases to the firm — the file outlives the vendor.
The no-training commitment
Client transcripts, notes and artifacts are never used to train shared or foundation models. Per-firm voice tuning stays per-firm.
Subprocessors & notice
Complete subprocessor list published; 30-day advance notice of any change, with termination rights on objection.
Retention & books-and-records
Audio and transcript retention follows the firm’s policy — a switch your CCO sets, not one we assume. Defaults to retain.
IF A PROMISE ON THIS PAGE IS NOT IN YOUR CONTRACT, TREAT IT AS NOT MADE — AND TELL US, BECAUSE THAT IS A BUG IN THE PAGE.
Read the architecture before you trust it.
The review pack has the contract behind every promise on this page — export, escrow, subprocessors, retention.
Request the security review pack