What happens to a document in Broker Lens
Broker Lens is a validation-stage demo for reviewing bank statements and payslips. The browser does the work where it can, and when a processing path sends anything elsewhere, this page states exactly where it goes.
Each path works differently
Know what a path transmits before you use it for a client document.
| Processing | What it does | What leaves the browser |
|---|---|---|
| Bank statements | Read in your browser by rule-based parsers, with no AI involved. Balance, date and transaction checks run on the rows they read. | Nothing, unless you enable automatic categorization for the case. |
| Payslips | An external AI service reads the payslip text and layout into rows for you to review. The checks then run by rule in your browser. | After you confirm, the payslip text and layout positions are sent to a configured external AI service, up to three times per extraction. The PDF file and page images stay on this device. |
| Automatic categorization | Optional and off by default. Suggests expense categories for statement transactions once you enable it for a case. | Transaction descriptions and direction are sent to OpenAI through our Worker, with recognizable account numbers redacted. Descriptions may still identify people or businesses. Amounts and PDFs are not sent. |
- Bank statements
- What it doesRead in your browser by rule-based parsers, with no AI involved. Balance, date and transaction checks run on the rows they read.
- What leaves the browserNothing, unless you enable automatic categorization for the case.
- Payslips
- What it doesAn external AI service reads the payslip text and layout into rows for you to review. The checks then run by rule in your browser.
- What leaves the browserAfter you confirm, the payslip text and layout positions are sent to a configured external AI service, up to three times per extraction. The PDF file and page images stay on this device.
- Automatic categorization
- What it doesOptional and off by default. Suggests expense categories for statement transactions once you enable it for a case.
- What leaves the browserTransaction descriptions and direction are sent to OpenAI through our Worker, with recognizable account numbers redacted. Descriptions may still identify people or businesses. Amounts and PDFs are not sent.
External AI processing always shows a disclosure and asks for explicit confirmation first. The provider’s own retention, training, and regional policies are outside this page’s scope — confirm them for your deployment before a client document is used. Local model processing is an internal experiment and is not available on the hosted service.
What the browser keeps
- The selected PDF is used in browser memory for the active review. It is not a File or Blob field in the persisted case store.
- The case store keeps the broker’s case and applicant labels, source filenames, extracted structured records, provenance, and check results in this browser’s IndexedDB.
- Removing a Case removes its applicants and document-slot records from that store. A different browser or device has no access to this browser’s cases.
What this page does not promise
- This page describes how the product behaves today. It is not legal advice, and it does not claim that any deployment meets a privacy or compliance obligation.
- A check result is a flag for human review, not a conclusion that a document is genuine, altered, fraudulent, or suitable for a lending decision.
- Do not use a customer document until the deployment’s configured provider, destination, and terms are appropriate for that use.