Guide

Before an AI tool touches client data: a vendor checklist for advisory firms

13 min read

By . Published . Last updated . Reviewed by Mavrin Labs on . How this guide was researched and checked.

A card reading "Before an AI tool touches client data: a vendor checklist for advisory firms" beside the Mavrin Labs logo
The card that shows when this guide is shared or linked.

An advisory firm can use an AI tool with client information only after it knows what the tool does with that information. Check whether the data trains a model, how long it is kept, who is told about a breach, where the records go and what the tool may do alone.

The guide is written for the principal or compliance officer of a registered investment adviser, a firm registered with the SEC or a state to give investment advice, or of an independent insurance agency.

It explains what a few public rules and reports say, and it ends with twelve questions to put to any AI vendor. It is not legal or compliance advice and recommends no vendor: your compliance officer or counsel decides how each rule applies to your firm.

The rules below describe duties your firm already has. An AI tool does not change them, but it can make them harder to meet.

What is an AI vendor, for an advisory firm?

An AI vendor is any company whose tool reads, stores or writes client information with AI for the firm, such as a meeting recorder, so the firm must oversee it. For an adviser registered with the SEC, that oversight is written and covers breach notice, as set out below (SEC compliance guide, checked Wednesday, November 18, 2026).

The vendor may make a standalone AI tool, or it may be a provider whose existing software has added AI features, from a meeting recorder to an assistant built into the client records system. Both count, because the question is what happens to client information, not what the product is called.

A meeting recorder is a common first case, and the guide to AI meeting notes for financial advisors in Florida covers the consent and records questions it raises.

Why it matters: client data draws fraud, and notice windows are short

Client information is worth stealing. The FBI's 2024 internet crime report logged 859,532 complaints and $16.6 billion in reported losses, a 33% rise on 2023, with business email compromise alone reported at about $2.77 billion across 21,442 complaints (the FBI's 2024 internet crime report, checked Monday, November 16, 2026).

When a breach does happen, amended Regulation S-P gives a covered firm no more than thirty days after it becomes aware of unauthorized access to notify affected clients, and asks it to act as soon as practicable (the SEC's announcement of the amendments, checked Monday, November 16, 2026). A vendor that answers slowly uses up that window.

A vendor learns of a breachIn a system it keeps for the firmWithin seventy-two hoursThe vendor tells the firmAmended Regulation S-P, forSEC-registered advisersWithin ten daysThe vendor tells the firmFlorida's breach law, for athird-party agentWithin thirty daysThe firm tells affectedclientsUnder both rules, as soon as itpracticably can
The notice windows this guide cites, and who tells whom. Each clock runs from when that party learns of the breach; the firm's own notice to clients is filled.

Does the AI plan you use train on client data?

The answer depends on the plan, so read the provider's own terms for the exact plan each person uses. Many providers treat individual plans and business plans differently. An individual plan may let chats train the provider's models, while a business plan under commercial terms may keep them out. Check every account that could see client data.

Terms can change from one month to the next, so check them on the day you decide, for the exact plan each person uses. Ask each vendor for the page that covers your plan, and keep a dated copy in your vendor file.

What does the SEC now ask of advisers about service providers?

The SEC now asks the advisers registered with it to oversee, in writing, the service providers that handle customer information. Regulation S-P, the SEC's privacy rule for customer information, as amended in 2024, requires a written incident response program, a plan to find, answer and recover from unauthorized access to that information.

That program must include written policies and procedures for overseeing service providers, and each provider must report a breach to the firm quickly.

Each provider must take steps to protect customer information. It must also tell the firm as soon as possible, and no later than seventy-two hours after it learns of a breach of a customer information system it maintains.

The firm may agree in writing that the provider notifies affected customers, but the firm keeps the responsibility for that notice. Larger firms had to comply by Wednesday, December 3, 2025, and smaller firms by Wednesday, June 3, 2026, according to the SEC's small entity compliance guide to Regulation S-P, checked on the date given with the guide above.

Whether an AI tool is a service provider depends on what it handles. If client information goes in, ask how the vendor meets the notice window.

Is AI output a record the firm has to keep?

AI output can be a record the firm has to keep, because the books and records rule turns on what a communication is, not on who drafted it. An adviser registered with the SEC keeps the written communications it sends and receives about its advice. An AI-drafted email an adviser approves and sends to a client may be one.

The rule covers written communications about any recommendation or advice, about receipts and deliveries of funds or securities, and about placing orders. Most of those records are kept for at least five years from the end of the fiscal year of the last entry, the first two years in an appropriate office.

Records kept electronically need procedures that guard them from loss, change or destruction and that limit who can reach them (the SEC's books and records rule, Rule 204-2, checked Friday, October 16, 2026).

Two questions follow for any AI vendor. Where does an approved draft land, and can the firm's archive reach it? If the tool keeps the only copy, the firm may struggle to produce it when asked.

What does Florida's breach law ask of a vendor that holds client data?

Florida's breach law puts duties on the vendor as well as on the firm. A business that acquires, keeps or uses personal information is a covered entity under the law. A vendor it contracts to keep, store or process that information is a third-party agent, and both must take reasonable steps to protect the data.

When a breach hits a system the vendor maintains, the vendor must tell the firm as soon as it practicably can, and no later than ten days after it determines that a breach occurred or has reason to believe one did. It must also give the firm everything the firm needs for its own notices.

The firm must then notify affected people in Florida, generally no later than thirty days after that point. A vendor may send those notices for the firm, but a failed notice counts against the firm (Florida's law on the security of confidential personal information, section 501.171, checked Friday, October 16, 2026).

For the vendor conversation, the point is simple: ask for its notice window in writing, and check that it fits both the state and the federal timeline.

What should you ask about logs, review and allowed actions?

Ask what the tool logs, who reviews its work and which actions it may take without a person. FINRA's 2026 report on its oversight priorities gives a useful list. FINRA oversees broker-dealers rather than advisers registered only with the SEC or insurance agencies, but its questions suit any firm that is weighing up an AI tool.

FINRA's 2026 report section on generative AI, checked Wednesday, November 18, 2026, names these practices:

  • storing prompt and output logs;
  • tracking which model version was used and when;
  • testing a model to learn its limits;
  • human review of model outputs, including regular checks for errors or bias.

On AI agents, the same section warns that an agent may:

  • act without a person's approval;
  • act beyond the scope it was given;
  • leave steps that are hard to trace;
  • mishandle sensitive data.

Turn each of those into a question for the vendor. A clear answer names the log, the reviewer and the list of allowed actions.

How should the firm describe its own use of AI?

Describe your firm's use of AI exactly as it works, and no more. When a firm tells clients that AI shapes its advice, that statement has to be true. The SEC has already charged advisers over AI claims they could not support, so any line about AI in your marketing deserves the same review as any other.

On Monday, March 18, 2024, the SEC charged two investment advisers with false and misleading statements about their use of AI. One said it used client data to make its AI smarter, and the other called itself an AI financial adviser.

The SEC found that neither claim held up. Without admitting or denying the findings, both firms agreed to settle and pay civil penalties, as the SEC's announcement of the two cases records, checked Wednesday, November 18, 2026.

The same care applies to what a vendor says about itself. If a vendor's claims end up in your client materials, you answer for them.

Which twelve questions make up an AI vendor due diligence checklist?

Put these twelve questions to any AI vendor before client information reaches its tool, and ask for every answer in writing. Each question turns one duty the rules and reports above place on a firm, its vendors or its records into something a vendor can answer, in the order of this guide.

  • Questions on training, storage and breach notice

    The first seven questions cover training, storage and breach notice, the answers a firm needs before any client data reaches the tool. The notice answer carries a deadline: Regulation S-P, as amended in 2024, gives a covered firm no more than thirty days to notify affected clients (the SEC's announcement of the amendments, checked Monday, November 16, 2026).

    Questions on training, storage and breach notice
    Question to ask What a clear answer includes
    Which plan or contract covers our use? The plan's name and the terms that govern it, with a link we can keep
    Is our data used to train or improve any model? A written yes or no, and where the setting lives if one exists
    How long are prompts, files and outputs kept? A stated period, and how we ask for deletion
    Where is our data stored, and who else handles it? The regions used, and a list of other companies that touch the data, shared on request
    How soon will you tell us about a breach of our data? A written notice window we can check against our own procedures
    Will you help us notify clients after a breach? Who drafts the notice, who sends it, and who decides
    Who at your firm can see our data? Named roles, multi-factor sign-in, and access removed when the work ends
  • Questions on logs, actions, records and the exit

    Questions on logs, actions, records and the exit
    Question to ask What a clear answer includes
    What does the tool log? Prompts, outputs, actions and model version, in a form we can read and export
    What may the tool do without a person? A written list of allowed actions, with approval before anything reaches a client
    How do approved outputs reach our archive? A path into the system that already keeps our records
    How was the tool tested, and how will we hear of model changes? Test results we can read, and notice before the model changes
    What happens to our data when the contract ends? Return or deletion in a stated period, confirmed in writing

    Keep the answers in your vendor file beside the plan's terms, and read them with a simple key:

    • Clear and in writing: the answer goes to the compliance officer as it is, with the plan's terms beside it.
    • First seven: missing or vague answers there mean client data waits until the vendor answers in writing, because those answers decide whether the data may go in at all.
    • Last five: a missing or vague answer goes to the compliance officer with the gap marked, and the tool waits on that decision.

How does Mavrin Labs answer these questions?

Mavrin Labs puts its answers to the questions that cover its own work in writing, in the services agreement and the design plan each client approves before a build. The page on how Mavrin Labs handles client data is one worked answer, covering training, breach notice, access, allowed actions and what happens when the work ends.

It is not a claim of compliance or certification.

Sources behind this guide

Each source in this guide was last checked on the date given beside it or with its first citation, and the guide is reviewed quarterly. The table below pairs each outside fact with its publisher.

Sources behind this guide
Fact Source
Advisers must oversee service providers in writing, and providers must report breaches fast SEC small entity compliance guide to Regulation S-P
Written communications about advice are records an adviser keeps SEC books and records rule
Florida puts breach duties on vendors that hold personal information Florida's law on the security of personal information
Logs, testing and human review are practices examiners look for FINRA report section on generative AI
Claims about AI in an adviser's marketing must be true SEC announcement of two AI cases
Reported internet crime losses and business email compromise in 2024 FBI 2024 internet crime report
Clients must hear of a breach quickly under amended Regulation S-P SEC announcement of the Regulation S-P amendments

Corrections and changes to this guide, newest last:

  • Monday, November 16, 2026: the definition of an AI vendor and the breach and fraud figures were added, each with its source.
  • Tuesday, November 17, 2026: the opening and closing sources lines were corrected to name every date a source was checked, the service provider citation was added to the definition, and a paragraph pointing to a demonstration no longer published was removed.
  • Wednesday, November 18, 2026: the SEC compliance guide, the FINRA section and the SEC announcement of the two AI cases were opened again and now carry that date. The notice-window diagram, the method behind the twelve questions and the key for reading the answers were added, and two repeats were cut. The sources line now points to the date beside each source instead of listing every date.

Key takeaways

  • Check the plan, not the product: individual and business terms can differ.
  • Treat an AI vendor that sees client data as a provider you oversee in writing.
  • Make sure approved AI output reaches the archive that keeps your records.
  • Ask for logs, a reviewer and a written list of allowed actions.
  • Hold client data back until the first seven answers are in writing.

The page for advisory and insurance firms shows the workflows Mavrin Labs looks at first. The service page for custom AI agents explains how an assistant drafts within set limits, and workflow automation covers where a person approves each step. To talk through a tool your firm is weighing up, start a conversation.

Frequently asked questions

Can our advisers paste client details into a personal AI account?

Whether advisers may paste client details into a personal AI account is a policy question for the firm. First find out which plan each account is on, what its terms say about training and how long it keeps chats. A personal account sits outside the firm's control, so the firm cannot set or check those settings.

Does a business AI plan settle the question?

A business plan does not settle the question on its own. Business terms often keep data out of training, but the firm still has to oversee the vendor, keep the records its rules require and supervise how staff use the tool. Read the plan's own terms, and treat them as one answer among the twelve in the checklist.

Do these rules apply to an insurance agency?

The SEC rules in this guide apply to advisers registered with the SEC, so most of them do not reach an insurance agency directly. An agency follows its own state's insurance privacy and data security rules instead. Florida's breach law does apply to many businesses that hold personal information, whatever their regulator.

Is this guide legal or compliance advice?

Nothing in this guide is legal or compliance advice, and Mavrin Labs gives neither. The guide explains in plain words what a few public rules and reports say, and it links each one so you can read the source yourself. Your compliance officer or counsel decides how any of it applies to your own firm.

The Mavrin Labs mark

Who writes these guides

Client work at Mavrin Labs is delivered by a team in mixed roles, led by our founder. AI tools help with research and drafting, and a person at Mavrin Labs checks each fact against its named source before a guide is published.

Enquiry form

Start with one workflow

Tell Mavrin Labs what is stuck and which systems it touches. A person at the firm reads every enquiry and replies by email.

Start a conversation

Fields marked with an asterisk are the ones a reply needs.

So a reply can address you properly.

The address the reply goes to.

Optional. Give one only if you would rather talk than write; the reply goes by email either way.

Optional, and useful when it says what the work has to fit around.

The result you want, and when you would want it working. Two or three sentences are plenty.

The task as it actually happens, roughly how often it runs, and which systems it touches. Two links at most, please.

Optional.

What you send goes to the Mavrin Labs inbox and is used to answer you, and a phone number, if you give one, is used for the same thing and nothing else.

A person reads it and replies by email.

If the form does not send, write to info@mavrinlabs.com instead; it reaches the same inbox.

Which hours would you take back first?

Name the one workflow that eats the most of your week. Mavrin Labs reads it, and the reply comes from the people who would build the fix.

Start a conversation