Security

How Vaulted protects your portfolio

What is in place today, and what isn't yet. Written to be accurate rather than impressive, so you can rely on it.

What Vaulted holds, and what it doesn't

  • Vaulted holds what you need to run your loans: names and emails of you, your team, your borrowers and your investors; each loan's property address, terms, payments, draw requests, expenses and messages; and your fund and investor figures.
  • Vaulted does not hold Social Security numbers, dates of birth, bank account numbers or card numbers. There is no field for any of them, and Vaulted refuses a Social Security number or date of birth typed into a loan document field, whether the field is named for it or not.
  • Borrowers can upload documents their lender asks for, such as an insurance binder or a scope of work. Vaulted can't read inside a file, so a file holds whatever is printed on it. Borrowers are asked not to send Social Security numbers or bank details, and Vaulted refuses a request whose title or note asks for one.
  • The one tax ID Vaulted holds is an EIN for a business (an LLC, corporation, partnership or trust), and only when the account owner enters one for year-end tax figures. It is encrypted before it is stored, only the last four digits are ever shown on screen, and only the account owner can see, change or export it. Vaulted never stores an EIN or any other tax ID for an individual.
  • Card payments for your subscription are handled by Stripe. Vaulted never sees your card number.
  • Vaulted records the payments your borrowers make. It does not collect or move that money.

Who can see what

  • There are three kinds of login: lender, borrower and investor. A borrower sees only their own loan, and an investor sees only their own investment.
  • Borrower and investor pages never take a loan reference from the browser. The loan is looked up from the signed-in person's own record, so there is nothing for them to change to reach someone else's.
  • Every page and request checks who you are and which portfolio you may open, against the database, on every click. Removing a team member takes effect immediately.
  • A request for a record that belongs to another lender is answered "not found", so it can't be used to learn that the record exists.
  • Automated tests read the source code and fail the build if a new page or route skips these checks.

Signing in

  • Email and password, or Google sign-in. Passwords are stored only as bcrypt hashes, never in a form that can be read back.
  • Repeated sign-in attempts, password-reset requests and signups are rate limited.
  • Password-reset links work once and expire after an hour. Only a hash of each link is stored.
  • Sessions end after 7 days without use and are kept in HttpOnly, Secure cookies.
  • Borrowers, investors and team members invited with a temporary password must choose their own at first sign-in. A temporary password that goes unused for 14 days stops working.
  • Changing or resetting your password signs you out everywhere else, and Settings has a button to sign out of every other device.
  • Two-step sign-in with an authenticator app can be turned on in Settings for password sign-ins, with one-time recovery codes. The app's secret is encrypted before it is stored, and recovery codes are kept only as hashes.

Connections and hosting

  • HTTPS only. Plain HTTP is redirected, and browsers are told to use HTTPS for two years.
  • Browser security headers deny framing, turn off content-type sniffing and block camera, microphone, location and payment access.
  • The application and its database run on Railway. DNS is at Cloudflare, subscription billing at Stripe and email at Resend.
  • Railway encrypts stored data at rest with AES-256, including the database, its backups and file storage. The database is backed up daily and archived continuously for point-in-time recovery.
  • Known-vulnerable dependencies are checked automatically, and the full test suite and a production build run on every change before it can go live.

Uploaded documents

  • Each file is encrypted (AES-256-GCM) before it is stored, with a key kept apart from the files, and is deleted automatically one year after it was uploaded. Every file shows the date it will be deleted.
  • There are no public links to files. A file is downloaded through Vaulted, which checks on every download that you are the lender on that loan or the borrower on it.
  • Files are checked by their contents, not their names: PDFs, JPEG, PNG and HEIC photos, and Word and Excel files are accepted, up to 20 MB each. Anything else is refused.
  • Closing your account deletes every file on every loan in it.

AI features

  • Loan details are sent to Anthropic's API only when you use an AI tool yourself: Deal Memo Writer, Risk Analyzer, Alert Drafter, or reading a term sheet you upload. Nothing is sent in the background.
  • Vaulted does not permit its AI provider to train on your data.
  • AI output is a draft for you to review. It never changes a loan until you confirm.

Not in place yet

  • No SOC 2 report and no independent penetration test.
  • Two-step sign-in is optional, not required, and borrower and investor logins can't turn it on yet.
  • Separation between lenders is enforced by the application and its tests, not by row-level security inside the database.
  • Apart from EINs and uploaded documents, data is not encrypted field by field inside the database; the disk underneath is encrypted by the host.

Found a security problem, or need more detail for a vendor review? Email [email protected]. A fuller written overview is available to customers on request.

Last reviewed November 2026.