For financial advisors, the right record of a client call is the note. Not the recording.

Every pitch for an AI notetaker for financial advisors leads with a consent banner and a SOC 2 badge. Your regulator asks a different question: what records did the tool create, where do they live, and can you produce them on request?

The $2 billion lesson: records in places you don’t control

The defining books-and-records story of this decade is the off-channel communications sweep. It started in December 2021, when J.P. Morgan Securities paid a $125 million SEC penalty because its people did business over WhatsApp and personal text, and the firm never captured any of it. Since then the SEC has collected more than $2 billion in penalties from over a hundred broker-dealers and investment advisers for the same failure.

Read the orders and notice what the violation was not. It was not the content of the messages. It was that business communications existed on a channel the firm did not capture, so the firm could not retain them under SEC Rule 17a-4 and could not produce them when examiners asked.

An AI notetaker is a new channel. Every client call it touches creates artifacts: an audio file, a verbatim transcript, an AI summary, and whatever copies get synced into a CRM. If those artifacts sit in a vendor’s cloud under a rep’s personal login, you have rebuilt the WhatsApp problem with a nicer interface. Some firms responded by banning notetakers outright. The better response is to know exactly which artifacts your tool creates, and to choose a tool that creates fewer of them.

What the rules actually require, and what they don’t

Start with the part vendors rarely say out loud: no SEC or FINRA rule requires an advisor to record client calls. FINRA Rule 3170, the “taping rule,” is the narrow exception, and it applies only to firms that hire heavily from disciplined firms. For everyone else, recording is a choice, not an obligation.

Notes are different. Under Advisers Act Rule 204-2(a)(7), written communications relating to recommendations, advice, or the movement of client funds are records you keep for five years, the first two in an easily accessible place. FINRA Rule 4511 defaults to six years where no period is specified. And under Reg BI and fiduciary duty, contemporaneous meeting notes are how you prove a recommendation had a basis, and that the conversation happened the way you say it did. Examiners ask for meeting notes. They are an asset.

So the artifacts split cleanly:

• The note documents the advice. You must retain it, and you want to.
• The recording is a separate artifact with separate liabilities: all-party consent in a dozen states (the map is in Is It Legal to Record Client Calls?), discoverability in any later dispute (see The AI Notetaker Legal Risk), and a verbatim capture of every hedge, joke, and offhand market opinion, preserved on a vendor’s server with your name attached.

Since June 3, 2026, Reg S-P covers every firm. Your notetaker’s cloud is in scope.

The SEC amended Regulation S-P in May 2024. Larger firms had to comply by December 3, 2025. Smaller firms’ date was June 3, 2026. As of last month, every covered broker-dealer and registered investment adviser needs a written incident response program and must notify affected clients within 30 days of becoming aware of unauthorized access to their information.

Now think about what client call audio contains. Holdings, account numbers, health situations, divorces, inheritances, tax problems, all spoken aloud in one stream. It is customer information in its densest form. Stream it to a notetaker vendor, and through them to a speech-to-text subprocessor, and every one of those systems becomes a place where “unauthorized access” can happen. Their breach becomes your 30-day notification event, your client letters, your exam finding. The amended rule also expects oversight of service providers handling customer information, which means diligence files, contract reviews, and annual reassessment for a tool someone on your team installed in an afternoon.

The cheapest way to shrink that scope is to not send the audio anywhere.

The architecture: keep the note, never create the recording

This is the posture Fazit was built around, and it is architectural, not contractual:

• Audio is captured into a fixed-size ring buffer in RAM. It is never written to disk, never uploaded, and continuously overwritten as the call proceeds. Persisting it would require a deliberate, reviewable code change, which is the subject of Why “Never Records” Is Not Marketing.
• Transcription runs on-device on Apple Silicon. No audio and no transcript reaches any vendor, so there is no subprocessor to diligence and no third-party system inside your Reg S-P incident-response scope.
• What survives the call is one Markdown note in your own Obsidian vault, stamped audio_retained: false. It is a plain file on your Mac (see Files, Not Rows), which means your retention policy actually reaches it, your backup strategy covers it, and exam production is a search away: grep -rl "401k rollover" ~/Vault/Calls/

Retention duty attaches to the note either way, cloud or local. The difference is everything else:

WHAT A CLIENT CALL LEAVES BEHIND

Cloud notetaker:  audio ................ vendor cloud
                  verbatim transcript .. vendor cloud
                  AI summary ........... vendor cloud
                  synced copies ........ CRM, email, mobile app

Fazit:            one Markdown note, in your vault, on your Mac

Retention duty attaches to the note either way.
Exposure attaches to everything else.

What an examiner gets is the note you retained under your own policy. What a plaintiff’s lawyer cannot get is the recording, because it never existed.

Five questions your CCO will ask any notetaker vendor

If you bring a notetaker to compliance, these are the questions coming back. Fazit’s answers, one line each:

• Where does call audio go, and who are the subprocessors? Nowhere. Processing is on-device; there are no subprocessors.
• Is client content used to train models? No. Nothing leaves the machine to train on.
• Can we produce every note for a client across five years without the vendor’s help? Yes. They are Markdown files in a folder you control.
• What happens to our records if we cancel? Nothing. The notes are already yours; there is no export step.
• Does the tool create records outside our books-and-records capture? It creates exactly one artifact per call, the note, and you decide where it lives and how it is archived.

The full security posture is documented at getfazit.com/security.

FAQ

Do financial advisors have to record client calls?

No. Neither the SEC nor FINRA imposes a general call-recording requirement. FINRA Rule 3170 requires taping only at firms with a high concentration of hires from disciplined firms. Meeting notes, by contrast, are records examiners routinely request, and notes memorializing recommendations should be retained under Rule 204-2 or Rule 4511.

Can financial advisors use an AI notetaker?

Yes, but the tool’s artifacts become the firm’s problem: audio and transcripts held by a vendor are records on someone else’s systems, subject to your retention, supervision, and now Reg S-P vendor-oversight obligations. FINRA reminded firms in Regulatory Notice 24-09 that its rules are technology-neutral: using AI does not change what you must capture and supervise.

Are AI meeting notes subject to books-and-records rules?

Treat notes that memorialize recommendations, advice, or client instructions as records: five years under Advisers Act Rule 204-2 for RIAs, six under FINRA Rule 4511 where no other period applies. The practical question is whether you can actually produce them in an exam. Plain files in a vault you control are easier to produce than rows in a vendor database you can only reach through their UI.

Does an on-device notetaker help with the amended Reg S-P?

It shrinks the scope. Reg S-P’s incident-response and 30-day notification duties attach to systems holding customer information. Audio that is processed in RAM and never persisted, on hardware you already control, adds no new vendor system holding client data, so there is no new third party to oversee and no new breach surface to paper.