Privacy

This page covers two different things, and it is worth keeping them apart. The first is the information you send uswhen you ask for pilot access on this website. The second is the borrower information a mortgage broker’s own team puts into the product. They are stored separately, used for different purposes, and described separately below.

What this website collects

Only what you type into the pilot-access form, plus two things your browser sends with it:

• Your name, work email, company, role, and monthly loan volume.
• The optional message, if you write one.
• The campaign tags in the link you arrived through, when a link carries them (utm_source, utm_medium, utm_campaign), so we know which post or email you came from.
• Your browser’s user-agent string.
• A one-way hash of your IP address — not the address itself. We use it to stop one machine flooding the form. We cannot read your IP address back out of it.

We use this to reply to you and to work out which channels reach brokers. We do not sell it, and we do not send it to an advertising network.

This website sets no cookies of its own, and loads no analytics or tracking scripts.

Deleting it. Email [email protected] and we will delete what you sent through this form, and tell you when it is done. There is no borrower information in it to complicate that.

Google Drive, if you connect it

A broker using LoanLoom may connect a Google Drive folder so the loan documents already sitting there can be worked on without re-uploading them. That connection is optional, and the product works without it.

We request two scopes, both read-only:

• drive.readonly — to read the documents in the folders you point us at.
• drive.metadata.readonly — to list those folders and see file names and dates.

We never request a scope that can write, move, or delete anything in your Drive, and the product has no code that could do so. We also do not copy your files out: there is no column anywhere in our database that holds a file’s contents. When a document is displayed for review it is fetched from Google at that moment. What we keep is the fields read off the document and a reference back to it.

LoanLoom’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting.You can disconnect Drive inside LoanLoom at any time, and you can revoke our access independently from your Google account’s permissions page. Revoking there stops all further access immediately, whatever we do.

How documents are read

Documents are classified and read by Anthropic’s commercial API. Under those commercial terms your inputs are not used to train models. Each document is a separate, stateless request — there is no chat history and no thread built up across a loan file — and no human at Anthropic reviews the content.

Borrower data inside the product

This section is a summary. The full, question-by-question version — including what is verified today versus what is on the roadmap — lives on the Privacy & Compliance page inside the product, which a broker can read before connecting anything.

• Every record belongs to exactly one workspace, and that separation is enforced by the database rather than only by application code. A query without a valid workspace context returns nothing.
• The application connects to the database with a restricted role that is not a superuser and cannot override that separation.
• Social Security numbers are shown masked to the last four digits on every operator-facing screen. The unmasked change history is restricted to the account owner.
• Every action on a loan — and every view of borrower data — is written to an append-only audit log in the same database transaction as the change itself. A change cannot be recorded without its audit entry, and the log cannot be edited or deleted afterwards.

Records are retained as an append-only chain of custody, consistent with mortgage recordkeeping expectations. If you are a borrower rather than a broker, your lender holds your file and is the right first contact about it — write to us at [email protected] and we will help you reach them.

Who else processes data for us

• Anthropic — reads documents to classify them and extract loan fields.
• Google — only if a broker connects Drive, and only read-only, as described above.
• Clerk — sign-in and account management for broker users of the product. Not used by this website.
• Railway — hosting and the managed database.

Changes, and getting in touch

If this page changes in a way that affects what we do with information already collected, we will say so here and update the date at the top. Questions, or a deletion request, to [email protected].