Yes — when the architecture is right. Here's how Milemarker Navigator makes Claude safe for regulated financial services firms.

The number one objection to AI adoption in wealth management is data security. Advisors, compliance officers, and firm leadership all ask the same question: "If I use Claude with client data, where does that data go?" It's the right question. The answer depends entirely on architecture. Consumer AI tools send your data to the model provider's servers where it may be used for training. Milemarker Navigator is built differently. Your data stays in your Snowflake instance. Claude accesses it through secure, permissioned, read-only MCP connections. Nothing is sent for training. Nothing leaves your control.

Why Financial Services Firms Are Cautious

Financial services data is among the most regulated in any industry. SEC, FINRA, GLBA, and a growing body of state regulations govern how client information is collected, stored, transmitted, and used. Client data includes personally identifiable information, account numbers, financial positions, and transaction history — all subject to strict handling requirements with meaningful legal consequences for mishandling.

Fiduciary duty means protecting client information is not optional — it is a legal obligation that runs from the firm to every individual client. A data breach or misuse of client information exposes a firm to regulatory action, civil liability, and reputational damage that can take years to recover from.

Consumer AI tools — free-tier ChatGPT and similar products — have terms of service that may allow data entered into the system to be used for model training. Compliance teams that flagged these tools were correct to do so. The risk was real and the caution was appropriate.

But here is the distinction that changes the analysis: most firms that have banned AI did so because they evaluated consumer-grade tools, not enterprise infrastructure. The answer to "is AI safe for our firm?" is not "no." It is "it depends on the architecture." Consumer tools are not designed for financial services data. Enterprise infrastructure — built with residency, permissioning, and auditability as first-order requirements — is a different category entirely.

The Milemarker Navigator Security Architecture

Milemarker Navigator connects Claude to your firm's data through a structured, permissioned architecture that addresses each security concern compliance teams raise. The following table describes each security layer and how it works in practice.

Data Residency

• How It Works: Your data lives in your Snowflake instance. Your account. Your cloud region. Your retention policies. Milemarker does not host a copy of your data outside Snowflake.

Model Training

• How It Works: Your data is never used to train Claude or any AI model. Anthropic's enterprise terms explicitly prohibit training on customer data. Milemarker enforces this at the infrastructure level.

Access Control

• How It Works: Role-based permissions determine what each user can access through Navigator. An advisor sees their clients. A COO sees the firm. A compliance officer sees audit data. Your firm configures the permissions.

Read-Only Default

• How It Works: Navigator provides read-only access to your data by default. Claude can query your warehouse but cannot modify, delete, or write records unless write-back is explicitly configured for specific use cases.

Encryption

• How It Works: Data in transit encrypted with TLS 1.2+. Data at rest encrypted with AES-256 in Snowflake. API connections between Navigator and Snowflake are encrypted end-to-end.

Audit Logging

• How It Works: Every Navigator query is logged: user identity, timestamp, question asked, data accessed, and results returned. Logs are available for compliance review and regulatory examination.

SOC 2 Type II

• How It Works: Milemarker maintains SOC 2 Type II certification. Security controls are audited annually by an independent third party.

MCP Standard

• How It Works: Model Context Protocol is an open standard created by Anthropic. It defines how AI models connect to external data sources with explicit permissions. It is not a proprietary or opaque integration.

Consumer AI vs. Enterprise AI Architecture

The distinction between consumer AI tools and enterprise AI infrastructure is not a matter of degree — it is a matter of design intent. Consumer tools are built for convenience and broad accessibility. Enterprise infrastructure is built for security, compliance, and auditability. They are different products that happen to use similar underlying models.

Consumer AI (ChatGPT, free-tier tools)

Data sent to provider's servers

May be used for model training

No role-based access control

No audit logging

Shared infrastructure

No compliance certification

Data residency unclear

Enterprise AI (Claude + Milemarker Navigator)

Data stays in your Snowflake instance

Never used for model training

Role-based permissions you configure

Complete audit trail

Your dedicated infrastructure

SOC 2 Type II certified

Data residency in your cloud account

Addressing Your Compliance Team's Questions

If you are the person responsible for getting AI approved at your firm, the following questions are the ones your compliance committee is most likely to raise. Here are precise, accurate answers you can bring to that conversation.

"Where does client data go when we use Claude?"

Nowhere. Claude accesses your data through Navigator's MCP connection to your Snowflake warehouse. The data stays in Snowflake. Claude reads it, generates a response, and the data is not retained by Anthropic or used for any purpose beyond answering your question.

"Can Anthropic see our client data?"

No. Anthropic's enterprise terms prohibit access to customer data for training or any purpose beyond processing your request. Milemarker's architecture ensures data is transmitted only through secure API connections within the query-response cycle. Anthropic processes the query and returns a response — it does not store or access your underlying client records.

"What happens if an advisor asks Claude about a client they shouldn't have access to?"

Navigator's permission system prevents this. Each user's access is scoped by role. If an advisor attempts to query a client outside their book, Navigator returns no data. The attempt is logged — including the user identity, the question asked, and the timestamp — so your compliance team has a complete record.

"How do we satisfy our compliance committee?"

Milemarker can provide: SOC 2 Type II report, architecture diagrams, data flow documentation, security questionnaire responses, and a reference call with an existing client's compliance team. Most compliance committees approve Navigator after reviewing these materials. The typical review cycle is two to three weeks.

"What about state privacy regulations?"

Your data resides in your Snowflake instance in a cloud region you choose. Milemarker does not transfer data across jurisdictions. Navigator's access controls and audit logging — including Snowflake Cortex-compatible governance — support compliance with state privacy requirements. Your legal team can review the architecture documentation and data flow diagrams as part of their assessment.

Frequently Asked Questions

Is my client data used to train Claude?

No. Anthropic's enterprise terms explicitly prohibit using customer data for model training. Your data is accessed through Navigator only to answer your specific query and is not retained for training purposes.

Where is my data stored?

In your Snowflake instance — an account your firm owns and controls. Milemarker manages the data pipelines but does not host a separate copy of your data outside of your Snowflake environment.

Can I get a SOC 2 report?

Yes. Milemarker maintains SOC 2 Type II certification. The report is available for review by your compliance team, auditors, or legal counsel upon request.

What is MCP and why does it matter for security?

Model Context Protocol is an open standard created by Anthropic that defines how AI models connect to external data sources. It provides explicit permission controls, scoped access, and structured data exchange — replacing ad-hoc API integrations with a standardized security model.

Can we restrict what data Claude can access?

Yes. Navigator's permission system allows your firm to configure exactly what data each role can query. You can restrict by data type, client assignment, time range, or any other dimension.

Is there an audit trail?

Yes. Every query through Navigator is logged with user identity, timestamp, question, data accessed, and results. Logs are retained according to your firm's policies and are available for compliance review.

What happens during a data breach?

Milemarker's incident response plan follows SOC 2 requirements. In the event of a security incident, affected clients are notified per contractual and regulatory requirements. Because your data resides in your Snowflake instance, you maintain independent access and control regardless of any Milemarker operational issue.

Can our legal team review the architecture before we proceed?

Yes. Milemarker provides architecture documentation, data flow diagrams, security questionnaires, and the SOC 2 report for legal and compliance review. Most firms complete their security review within 2-3 weeks.

Related guides

Part of the AI for Wealth series:

• Snowflake for Financial Services & Wealth Management

• Snowflake Cortex for Financial Services. AI Where Your Data Already Lives.

• Claude for Financial Advisors: AI That Knows Your Clients, Portfolio, and Practice

• Claude for Financial Services: How Wealth Management Firms Use AI With Real Client Data

• Claude for Compliance: AI-Powered Compliance Queries for Wealth Management Firms

• Model Context Protocol (MCP) for Wealth Management: How AI Agents Access Firm Data