Disclosure: I co-founded Mitosis Labs, which runs Private SuperIntelligence. This is an adaptation of the original guide written for SEC-registered advisers and multi-family offices. General information, not legal advice.
If you build or run tooling for an advisory firm, amended Regulation S-P turns every AI integration into a vendor review question. The test is a data-path test. The rule defines a service provider as "any person or entity that receives, maintains, processes, or otherwise is permitted access to customer information through its provision of services directly to a covered institution."
Trace the path, not the product name
Draw each AI feature as a pipe and ask who sits on it:
- Meeting notetaker. Audio in, summary out. It receives and processes customer information.
- Enterprise AI seat (ChatGPT Business or Enterprise, Microsoft Copilot, Claude for Work). It receives customer information the moment an adviser pastes a client email into it.
- AI feature inside the CRM or portfolio system. It processes customer information through that vendor, and possibly through the model provider behind it. That second hop is easy to miss in an architecture diagram.
- Private AI deployment run by an outside company. Still a service provider, if that company can access customer information.
The definition turns on access, so "we only send summaries" or "it's just a pilot" doesn't take a vendor out of scope. And the scope of what counts as customer information widened: any record containing nonpublic personal information about a customer that the firm holds or that is handled on its behalf, including information received from another financial institution.
The obligations, as requirements
- Oversight. The incident response program must include written policies and procedures "reasonably designed to require oversight of service providers," run "through due diligence and monitoring." Check before data flows, keep checking after.
- Vendor notice. The provider must notify the firm "as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system maintained by the service provider."
- Client notice. The firm notifies affected clients no later than 30 days after becoming aware. A vendor can send it under a written agreement, but "the ultimate responsibility for such notice rests with the covered institution."
- Records. The adopting release points advisers to Rule 204-2(e): kept in an easily accessible place for at least five years, the first two in an appropriate office of the adviser.
Larger advisers ($1.5 billion or more in assets under management) have had to comply since December 3, 2025, and smaller advisers since June 3, 2026.
Vendor questions that map to system properties
| Question | Property you are checking |
|---|---|
| Where is our clients' information received or stored? | Systems, regions, subprocessors, including the model provider |
| Do you or your model provider train on our data? | Contractual no-train, plus how feedback buttons are handled |
| How long do you keep prompts, outputs, transcripts and files? | Retention per data type, confirmed deletion |
| Who can see our data? | Named roles, access conditions, access logging |
| Will you notify us within 72 hours of a breach? | Contract term with a named contact |
| What security attestations do you hold? | A current SOC 2 Type II report or equivalent |
| Can we export or archive outputs? | A route into the books-and-records archive |
| What happens when we leave? | Return and deletion terms with a deadline |
Store each answer with the date and reviewer. That file is the due diligence record.
Private SuperIntelligence from Mitosis Labs works across a firm's own email, documents and data and acts within permissions the firm sets. Each deployment is built for one client, from the hardware to the model provider to where the data is stored, and a client deployment captures none of the client's data and sends no telemetry back to Mitosis Labs.
Speak with the founders
Private SuperIntelligence takes a limited number of families at a time so every one gets the same standard of service. Book a private call (ref RSP1-DEV) to talk through your office with Alex Morris.
Prakshal Jain (PJ), Co-founder and CTO, Private SuperIntelligence (by Mitosis Labs)
Alexander Morris, Co-founder and CEO, Private SuperIntelligence (by Mitosis Labs)
Originally published at privatesuperintelligence.si.
Sources: SEC, Fact Sheet: Final Rules, Enhancements to Regulation S-P, May 2024, https://www.sec.gov/files/34-100155-fact-sheet.pdf ; SEC, Final Rule: Regulation S-P, Release No. 34-100155, 2024-05-16, https://www.sec.gov/files/rules/final/2024/34-100155.pdf ; SEC, Enhancements to Regulation S-P: A Small Entity Compliance Guide, https://www.sec.gov/files/rules/final/2024/regulation-s-p-small-entity-compliance-guide.pdf ; SEC press release 2024-58, 2024-05-16, https://www.sec.gov/newsroom/press-releases/2024-58 ; SEC Division of Examinations, Examination Priorities, Fiscal Year 2026, 2025-11-17, https://www.sec.gov/files/2026-exam-priorities.pdf ; SEC, Family Offices: A Small Entity Compliance Guide, rule adopted 2011-06-22, https://www.sec.gov/files/rules/final/2011/ia-3220-secg.htm ; 17 CFR 275.204-2 (Legal Information Institute), https://www.law.cornell.edu/cfr/text/17/275.204-2
Top comments (0)