Secure AI Note-Takers for RIAs: SOC 2 Certification and Audio Retention Compared

Most AI note-taker vendors say "SOC 2 certified" somewhere on their security page. A few mean a Type II audit completed last quarter by a licensed CPA firm. Others mean a Type I snapshot from two years ago. Several tools that clear either bar still retain your audio recordings for weeks or months after the meeting ends. SOC 2 quality and audio retention are different risks, and conflating them is how firms end up with a compliance gap they didn't know they had.

63% of Schwab-custody RIAs use AI in some capacity (Schwab/Logica Research, n=533, Jan 2026), and meeting note-takers are where the most client non-public information (NPI) flows through third-party infrastructure. A tool that retains an audio file containing a client's name, account balance, and estate planning discussion is a breach notification event waiting to happen.

Why SOC 2 and audio retention are two separate questions

SOC 2 certification tells you a vendor has been audited against the AICPA's Trust Service Criteria: security, availability, processing integrity, confidentiality, and privacy. What it does not tell you is what the vendor actually stores, for how long, or where. A SOC 2 Type II audit covers whether the vendor's controls operated as designed over a period of time. It does not require that audio be deleted after transcription.

Vendors use "SOC 2 certified" as shorthand for "secure." The right question is: what data does this vendor hold, and for how long? An audio recording from a client meeting is NPI under Reg S-P. It is also a potentially discoverable record under Rule 204-2 if it relates to investment advice given. A tool can hold a valid SOC 2 report while keeping your client's voice on a server indefinitely.

Under amended Regulation S-P (effective June 3, 2026 for smaller advisers under $1.5B AUM), you must maintain a written program for vendor oversight that covers what each vendor holds, how long they hold it, and what your notification rights are in a breach. A SOC 2 badge does not substitute for reading the data processing agreement.

Five criteria before you deploy

All five map directly to Reg S-P vendor oversight and the SEC's 2026 "Emerging Financial Technology" exam section, which directs examiners to assess whether a firm's controls are consistent with its disclosures and whether automated tools meet advisory obligations.

1. SOC 2 Type II, not Type I

Type I is a point-in-time snapshot that says controls were designed correctly on the audit date. Type II covers a minimum of six months and requires the auditor to verify that controls actually operated during that period. For a tool processing client meeting recordings, Type I is not enough. Ask for the most recent Type II report and confirm the audit period. Reports older than 12 months may not reflect current infrastructure.

2. Audio deletion policy, in writing

Does the tool delete audio after transcription? If so, how quickly, and is that window guaranteed in the DPA or only stated in a help article? "We don't store audio" and "we delete audio within 24 hours of processing" are different claims. A stored audio file carries more NPI risk than a text transcript alone. Get the specific retention window in writing before signing.

3. Training data exclusion, contractually guaranteed

Does the vendor use your recordings or transcripts to train or improve its models? This should be addressed explicitly in the DPA, not just on a marketing page. Consumer-tier tools typically include training rights. Enterprise-tier tools from reputable vendors typically exclude it, but "typically" is not good enough for Reg S-P purposes. The exclusion needs to be in the agreement.

4. Data residency

Where are recordings and transcripts physically stored? For firms subject to state-level data laws, or clients whose agreements restrict offshore data processing, US-only storage can be a requirement. Some tools offer configurable data residency at the enterprise tier; others route through EU infrastructure regardless of subscription level. Ask before you sign and require the answer in the DPA, not just in a sales call.

5. Data processing agreement availability

Will the vendor sign a DPA that names NPI handling, breach notification timelines, data retention, and subprocessors? A vendor that declines to sign a DPA, or sends a generic terms-of-service addendum that does not address financial NPI, is not the right tool for a registered adviser. If your firm lacks an AI policy and vendor-oversight framework, the written AI policy guide covers the required sections before you start onboarding tools.

How the major tools compare

Tool	SOC 2 Type II	Audio captured and retained?	Trains on your data?	DPA for RIAs	Notable compliance notes
Zocks	Not publicly stated	No (text-only; audio never transmitted)	No	Yes	Strongest data-minimization posture by architecture, not policy
FinMate	Yes (+ ISO 27001, AES-256, audit logs)	Not stated; structured-data focus	No	Yes	Explicit data residency; HNW/UHNW orientation; lags on workflow automation
Fathom	Yes	Yes	No (stated policy; no training on client data)	Yes	No advisor CRM integrations; no major compliance actions as of research date
Jump	Not confirmed publicly	Yes (audio + video retained)	Not confirmed	Inquire directly	Market leader for advisor CRM integrations; Type II report not publicly available
Otter.ai	Yes (E2E encryption on paid tiers)	Yes	Free tier: yes; enterprise: excluded in DPA	Enterprise tier required	Brewer v. Otter.ai (N.D. Cal., filed Aug 15 2025): consent and training claims
Fireflies.ai	GDPR-compliant; SOC 2 not confirmed	Yes	Not confirmed	Inquire directly	Cruz v. Fireflies (BIPA, 2025): voiceprint claims; Illinois client gap
Zoom AI Companion	Via Zoom enterprise license	Configurable; native-transcript mode avoids bot recording	Enterprise license: excluded; verify explicitly	Via Zoom enterprise DPA	Highest bundled adoption; lowest advisor satisfaction per T3 surveys

Zocks takes the strongest Reg S-P posture by design: it captures text only. No audio or video is ever transmitted to Zocks' servers. The data-minimization result is architectural, not a setting that can be misconfigured. If reducing the NPI footprint in third-party systems is the priority, a tool that never receives audio is in a different category from one that receives it and then deletes it.

FinMate carries the strongest enterprise security credentials of the advisor-specific tools: SOC 2 Type II, ISO 27001, AES-256 encryption, audit logs, and explicit data residency. It skews toward HNW and UHNW practices and falls behind Jump on workflow automation.

Fathom has a SOC 2 and a clear policy against training on client data. It does not offer direct integrations with Redtail or Wealthbox, which limits its usefulness for firms that need meeting-to-CRM workflows. No significant compliance or litigation actions were identified as of the research date.

Jump is the market-leading advisor-native tool, with deep integrations into Redtail, Wealthbox, and Salesforce. It stores audio and video. A publicly available, current SOC 2 Type II report had not been confirmed as of the research date. If Jump is your tool, request the Type II report directly from the vendor and ensure the DPA addresses NPI before deployment.

Otter.ai is subject to Brewer v. Otter.ai (N.D. Cal., filed Aug 15 2025), a lawsuit alleging recording without consent and use of recordings for model training. The case surfaced what Otter's terms permit on the free tier. Otter.ai does hold a SOC 2. If your firm uses it, the enterprise tier with a signed DPA covering NPI is the floor, not the recommendation.

Fireflies.ai is subject to Cruz v. Fireflies (2025), a BIPA (Biometric Information Privacy Act) class action alleging voiceprint collection without consent. Illinois BIPA requires written consent before collecting biometric identifiers. Fireflies had no published biometric data retention policy at the time of the filing. For firms with Illinois-domiciled clients, that gap matters regardless of how the litigation resolves.

Wealthbox launched a native AI note-taker in October 2025 at no marginal cost to existing subscribers. If your firm is already on Wealthbox, the note-taker runs under the existing Wealthbox DPA and data terms, which means one less standalone vendor to document. Worth checking before you commit to a separate tool.

How to verify a SOC 2 report

Vendors will produce a SOC 2 report, a SOC 2 summary letter, or a badge graphic. These are not equivalent. Here is what to check:

1. Confirm the type. The report should state "SOC 2 Type II" and include a defined audit period (e.g., "For the Period from October 1, 2024 through March 31, 2025"). A Type I report will state a single audit date, not a range.
2. Check the auditor. A SOC 2 report must be issued by an AICPA-licensed CPA firm. A self-assessment labeled "SOC 2 compliant" or a summary prepared by the vendor itself is not an audited report.
3. Check which Trust Service Criteria are covered. Most SOC 2 audits cover Security and Availability. Coverage of Confidentiality and Privacy is more directly relevant to NPI handling. A report that covers only Security is not a full picture.
4. Check the report date. A Type II report more than 12 months old may not reflect current infrastructure, especially for cloud-native tools that change frequently. Ask whether a new audit cycle is underway.
5. Keep a copy. Your Reg S-P vendor oversight file should include the most recent SOC 2 Type II report for every tool that processes client NPI. SEC examiners assessing your Emerging Financial Technology controls may ask for vendor documentation.

What belongs in the DPA

Under amended Reg S-P, service providers that receive or maintain customer records and information must be covered by written agreements containing the required safeguards. For an AI note-taker, a defensible DPA addresses:

• NPI scope: explicit acknowledgment that meeting recordings, transcripts, and AI-generated summaries constitute customer NPI subject to Reg S-P
• Purpose limitation: vendor uses data only to deliver the contracted service; no training, product improvement, or aggregated benchmarking rights on your client data
• Retention and deletion: specific window for audio, transcript, and summary retention, with contractual deletion timelines (not just policy page language)
• Breach notification: notification to the RIA within 72 hours of discovering a breach (matching the Reg S-P standard for smaller advisers)
• Subprocessors: list of third-party subprocessors with rights to receive notice when new ones are added
• Return and destruction on termination: what happens to your data when you cancel

If you are not sure which tools to evaluate first, or whether your meeting workflow is the highest-priority automation for your firm, the AI Bottleneck Scorecard maps where advisor time is going before you commit to a tool.

Recordkeeping: what the note-taker's output must preserve

Under Rule 204-2, an AI-generated meeting summary or transcript qualifies as a book or record if it relates to your business as an investment adviser. You must retain both the AI output (the summary) and the underlying source material (the transcript, if not the audio itself) for five years, with the first two years readily accessible.

The vendor's own retention is not your retention. If the note-taker stores transcripts for 90 days and then deletes them, and your compliance archiver never pulled the export, you have a Rule 204-2 gap. Ensure your workflow includes an archiving step: export to Smarsh, Global Relay, or your existing compliance archiving solution before the vendor's retention window closes. A meeting summary that lives only inside the note-taker's dashboard is not an archived record.

The deletion of audio after transcription is a feature, not a risk. A transcript is sufficient for Rule 204-2. Retaining audio beyond what is necessary to produce the transcript extends the NPI exposure window without adding recordkeeping value.

Frequently Asked Questions

Why do SOC 2 certification and audio retention matter for RIAs?

SOC 2 tells you the vendor's security controls have been independently audited. Audio retention tells you how long client NPI, including names, financial context, and advice discussed in a meeting, lives on a third-party server. A tool can carry a valid SOC 2 report and still retain audio indefinitely. Under amended Reg S-P and Rule 204-2, you are responsible for what your vendors hold, how long they hold it, and what happens in a breach. The SOC 2 badge does not answer those questions.

Which AI note-takers delete audio after transcription, or avoid capturing it entirely?

Zocks never captures audio or video. Text-only capture is the architecture, not a configurable setting, so no audio ever reaches a third-party server. For tools that do capture audio, deletion timelines vary and are often not published. Before deploying any tool, get the specific retention window in writing, confirm it is guaranteed in the DPA rather than just stated in a help article, and keep that documentation in your vendor oversight file.

What is a "no-bot, no-recording" mode, and which tools offer it?

Some AI note-takers can work without a visible recording bot and without sending audio to their own servers. Zoom AI Companion can generate summaries from Zoom's native transcript feed rather than a separate audio recording. Zocks operates without a bot and without audio capture. Some clients object to visible recording bots; some state laws (including Illinois BIPA) impose consent requirements specifically around biometric data captured from audio. A tool that reads the meeting platform's own transcript sidesteps both issues.

What data-residency options do AI note-takers offer?

FinMate offers explicit data residency as a stated feature. Zoom AI Companion inherits Zoom's enterprise data residency options, configurable by tenant. Most other standalone advisor note-takers do not publish US-specific residency options. If your firm operates under state-level data laws or client agreements that restrict cross-border data transfers, ask the vendor directly and put the answer in the DPA as a contractual term, not a sales call promise.

How do I verify that a vendor's SOC 2 report is current and legitimate?

Request the full SOC 2 Type II report, not a badge or a vendor-prepared summary. Confirm it covers at least a six-month audit period, was issued within the past 12 months, was completed by an AICPA-licensed CPA firm, and covers the Security Trust Service Criterion at minimum. Keep a copy in your Reg S-P vendor oversight file. If the vendor cannot produce a Type II report or sends one older than 12 months, ask whether a new audit cycle is in progress and when it will complete. A SOC 2 summary written by the vendor, without the auditor's report behind it, cannot be independently verified.

Which AI note-taker vendors will sign a data processing agreement with an RIA?

FinMate, Zocks, and Fathom have a track record of providing DPAs for enterprise and advisor-tier customers. Otter.ai provides a DPA on its enterprise tier. For Jump and Fireflies.ai, request a DPA directly; availability may depend on subscription tier and the vendor's current enterprise sales process. For any tool handling client meeting recordings, a signed DPA that explicitly covers financial NPI, states the breach notification timeline, and lists subprocessors is non-negotiable under amended Reg S-P. A vendor that refuses to sign, or that sends only a generic terms addendum, is a vendor to reconsider.

What are your obligations if a note-taker vendor experiences a breach?

Under amended Reg S-P, you must notify affected customers of a covered security incident without unreasonable delay. Whether you can meet that obligation depends on your vendor notifying you first, which is why breach notification timelines belong in the DPA — not just on a vendor security page. If a vendor breach exposed client meeting recordings or transcripts, the notification trigger is determined by what data was disclosed, not which tool held it. Document your vendor's breach notification commitment before deployment, test the contact path annually, and know which clients have data held by each tool so you can scope a notification quickly. A vendor that breaches and takes 30 days to notify you cannot be remedied after the fact by reading the DPA you should have negotiated up front.