How LOAF handles your documents

Short and specific. This describes how the pilot works today.

What happens to a contract

If you add several files, your browser joins them into one PDF first, on your computer. Then it sends that PDF straight to encrypted storage. The key is your company's own, created for that business day.
Social Security and account numbers found in the contract's text are masked.
The contract is read by Claude through Amazon Bedrock inside our private AWS environment. Amazon Bedrock does not store prompts or answers and does not use them to train models.
The result is saved, encrypted, for your company's team for the rest of the business day. If a teammate uploads the same file, they get the saved result.
After your business day ends, the contract and the result are deleted and the day's key is retired, so anything left behind cannot be read.

What we keep

An audit record of activity: that a document was uploaded, finished or deleted, with IDs, dates and page counts. It never contains contract text, file names or borrower details. The record is write-once so it cannot be altered afterward.

Scanned pages

Scanned and photographed pages are read as images. Numbers on those pages cannot be masked first, so use them only when you are comfortable with that.

Who can see what

Each company's data is isolated from every other company's by the cloud environment itself, not only by our code. People in your company share the company's documents and free-document balance.

Questions about privacy or security can go to your LOAF contact during the pilot.