Learn · For financial advisors, RIAs & wealth management
Client intake software for financial advisors that never reads a prospect’s net worth.
Brun is secure client intake software for financial advisors and RIAs. When a prospect requests a consultation or portfolio review, their inquiry — net worth, account numbers, SSNs — is encrypted in their browser before it sends, so the provider only ever stores ciphertext it cannot read. Only your advisors hold the key.
For a prospect, that means a portfolio-review request never sits somewhere a breach could turn a household’s net worth into a spreadsheet row. Keep your existing website and CRM — Brun is the zero-knowledge layer in front of the form you already have.
What is secure client intake for an advisory firm?
Secure client intake means a prospect's submission is locked on their own device before it ever transmits. A readable version of the inquiry never exists on the wire, in a form vendor's inbox, or in a CRM's database — every byte stored on the vendor side is ciphertext.
For an advisory practice, that means a prospect’s net worth, account numbers, and SSNs never sit anywhere as a plaintext line item — not in a backup, not in a support ticket, not in a training set. See the full definition of zero-knowledge intake.
Why an ordinary advisor intake form is a Reg S-P liability.
When a prospect fills out the “schedule a consultation” or “request a portfolio review” form on an advisor's website, that submission often contains net worth, account numbers, and SSNs. Under the 2024 Reg S-P amendments that data is “customer information” the firm must safeguard and breach-notify on, so every readable copy is a liability before the advisor has even responded.
Every vendor in the path can read it
Your consultation-request form’s vendor — the widget, the inbox relay, the database behind it — receives a prospect’s assets, account numbers, and SSN exactly as typed. So does your backend or a downstream CRM like Wealthbox or Redtail: copies land in logs, in a database, in the email it triggers.
- Net worth, investable assets, and account balances
- Brokerage and bank account numbers
- Social Security numbers and tax IDs
- Household and beneficiary data — spouse, dependents, estate details
- Risk tolerance, income, and held-away account information
Reg S-P leaves no exemption
SEC Regulation S-P, as amended in June 2024, requires RIAs and broker-dealers to maintain written safeguarding policies and an incident-response program, plus 30-day breach notification covering all customer information in the firm's possession — including data a website form captures. A plaintext inquiry sitting in a form provider's database or a generic CRM is exactly the unauthorized-access surface that rule, alongside SEC Rule 204-2 and FINRA retention, was written to close.
How does Brun keep a prospect inquiry unreadable?
Ciphertext at every stop, from a prospect’s screen to a lead on your board.
Sealed in their browser.
Nothing about your website form changes for them: same fields, same branding, no Brun logo, no account or app to install. They enter their goals, assets, and contact details and hit send. The instant they press submit, a script running on their device locks the fields with your firm's public key — the half of the pair that can seal data but never open it. Net worth, account numbers, and SSNs leave the browser already as ciphertext, never as plaintext on the wire.
Screened. Never opened.
We check that the envelope is structurally sound, accept it, and store it as ciphertext — full stop. No key capable of opening it ever reaches our servers, so a stolen backup or a subpoena served on us returns a household's finances as noise, not as a Reg S-P breach-notification event.
We store gibberish.
stored on our serversOff-limits to us: every prospect inquiry, lead, and advisor note. On the record for running your account: your firm’s email, billing status, and any support message you send.
Unlocked on your board.
An advisor opening the inbox triggers decryption on the advisor's device itself; the key belongs to your firm alone. Readable customer information appears on exactly one screen — theirs. The decrypted inquiry, sealed again under your firm's key, lands on a simple board as a prospect you can note, assign, and move from New to Won, then re-enter in Wealthbox, Redtail, or whatever CRM you already run once you're ready to onboard.
Your consultation-request page can’t unlock a thing — the public handle it references identifies your firm, nothing more, and can’t decrypt without your advisors’ key. Full mechanics →
Ordinary advisor intake form vs. Brun zero-knowledge intake.
Every row below asks the same question a different way: does a plaintext copy of a household's finances exist anywhere outside your advisors' browsers? With an ordinary form, yes — sitting inside your Reg S-P scope. With Brun, no.
| Ordinary advisor intake form | Brun zero-knowledge intake | |
|---|---|---|
| Where it's encrypted | In transit only (TLS), then decrypted on arrival | In the prospect's browser, before it sends |
| Can the form or CRM vendor read it | Yes — net worth and account numbers land in their plaintext database | No — they store ciphertext only |
| Can your server read it | Yes — your backend receives plaintext SSNs and balances | Only your advisors' browsers, after decrypt |
| What a vendor breach leaks | Readable customer information — Reg S-P breach-notification event | Ciphertext only |
| What a subpoena to the vendor returns | Readable prospect financials | Ciphertext only |
| Reg S-P safeguarding scope | Full plaintext copy sits inside your safeguarding scope | No readable copy for the vendor to safeguard |
| Setup | Often a rebuild or a hosted form | Two changes to the form you already have |
Do I have to rebuild my form or migrate my CRM?
No. You keep the consultation-request form you already have and the CRM you already run. Wiring it up takes two edits — nothing rebuilt, nothing hosted elsewhere, no backend work, and nothing your prospects can see.
- <form action="/your-old-endpoint">
+ <form action="…/public/intake/your-handle">
+ <script src="…/intake.js">Financial advisor client intake questions, answered.
Do I have to replace my current website or advisor CRM to use Brun?
No. Brun is designed to sit behind the contact, consultation-request, or portfolio-review form you already have on your advisory website. You keep your existing site, branding, and any CRM like Wealthbox or Redtail you use downstream. Brun just intercepts the submission, encrypts it in the prospect's browser before it ever leaves their device, and gives your team a simple board to decrypt and work the new lead.
How does Brun protect prospect data like net worth and account numbers under Reg S-P?
Every field a prospect types — investable assets, account numbers, household details — is encrypted in their browser before transmission. Brun stores only ciphertext it cannot read, so there is no plaintext copy of customer information sitting in a vendor database for an attacker, or a vendor employee, to access. That directly shrinks the safeguarding and 30-day breach-notification surface the SEC's 2024 Regulation S-P amendments hold RIAs responsible for.
Who can actually read an inquiry submitted through our intake form?
Only your firm's team can read the inquiry itself. Decryption keys live with your advisors, not with Brun. We cannot read inquiries, our staff cannot read them, and to a subpoena or a breach of our servers your inquiry and lead content stays ciphertext. (Account and billing data we need to run the service — your account email and subscription status — is server-readable; the prospect's financial details are not.) This is the difference from a typical secure form vendor that advertises encryption in transit but still holds a readable copy of every prospect's financial details on their side.
Can Brun collect the same fields as a standard financial advisor client intake form template?
Yes. You can capture the usual new-client intake fields — contact details, investment goals, risk tolerance, asset and income ranges, and even SSN or account numbers where you need them — using the form you already have. The difference is purely on the back end: instead of those answers landing in plaintext, they are encrypted client-side so the sensitive data is never readable outside your team.
How is this different from Wealthbox, Redtail, PreciseFP, or a Jotform secure form?
Those tools are excellent at workflow, planning, and data-gathering, but they hold your prospects' inquiries in readable form on their infrastructure, which keeps the full plaintext copy inside your Reg S-P safeguarding scope. Brun is narrower and complementary: it is the zero-knowledge intake layer in front of your form. Inquiries are unreadable to everyone but you; once you decrypt one, you carry it over to your existing CRM yourself. Brun does not replace your CRM; it de-risks the moment of capture.
What does Brun cost for a small RIA versus a multi-advisor firm?
Plan options and pricing appear at signup when you pick your plan, sized for a solo advisor up through a multi-advisor firm. Every plan carries the same encryption — there is no cheaper tier that can read a prospect's financials. Because Brun layers onto your current website and CRM rather than replacing them, you're not paying for a platform migration or a six-figure wealth-suite implementation.
Go deeper on encrypted intake.
- What zero-knowledge secure intake isMinus the jargon: the browser does the encrypting, and your team holds the only key that opens the result.
- Why your intake must be encryptedHow readable inquiries become breaches, subpoena results, and training data — and how client-side encryption prevents all three.
- Secure intake and regulated dataWhere client-side encryption helps a regulated practice — and where a compliance program must take over.
- Brun overviewIntake, board, and team in one small product, built for advisory teams of one to five.
- Intake by industryHow zero-knowledge intake translates across fields — law, therapy, real estate, recruiting, and more.
Not legal advice
This page describes Brun's architecture and how it relates to safeguarding customer information; it is general information, not legal advice. Your obligations under Reg S-P depend on your specific firm — confirm your compliance posture with qualified counsel.
Prospect inquiries only you can read
Start securing your client intake.
Brun is zero-knowledge client intake software for financial advisors and RIAs: prospect inquiries arrive sealed, stay ciphertext on our side, and open as leads for your advisors alone. Two changes connect the form you already run — start this afternoon.