C
Centsible Consulting
← All articles
Core

Data Privacy and Core: Your Data Never Leaves Your Environment

For firms handling sensitive client data, the architecture of your AI is not a preference. It is a compliance requirement. Here is how Core handles it.

B
Brent Gephart
March 6, 20265 min read

The Compliance Reality

Law firms operate under attorney-client privilege. Medical practices operate under HIPAA. Accounting firms have client confidentiality obligations. Financial advisors have fiduciary duties. All of these regulatory frameworks have one thing in common: they were not designed with shared AI infrastructure in mind.

When a lawyer pastes case details into a shared AI platform, is attorney-client privilege maintained? The answer depends on the platform''s terms of service, data handling policies, and infrastructure architecture — none of which were designed to preserve legal privilege. The prudent answer is: probably not, and the risk is not worth testing.

Core''s Architecture

Core runs in your dedicated environment. This is not a privacy setting on a shared platform. It is a physical separation of infrastructure. Your data — every document, every conversation, every workflow, every piece of knowledge Core captures — resides in resources allocated exclusively to your organization.

There is no shared database. There is no multi-tenant model layer. There is no situation in which your data could be accessible to another organization because your data is not in a system that other organizations access.

What This Means for Specific Regulations

Attorney-client privilege: Communications between your team and Assist about client matters remain within your environment. Core''s learning from those communications does not leave your environment. The analysis: privilege is maintained because the infrastructure is equivalent to an internal system.

HIPAA: Protected health information processed through Assist or Flows is handled within a HIPAA-eligible environment. We execute a Business Associate Agreement. PHI is encrypted at rest and in transit within your dedicated infrastructure. Audit logging tracks all access.

Financial regulations: Client financial data processed through the platform is subject to the same controls as data in your other internal systems. Access controls, audit trails, and retention policies are configurable to meet your specific regulatory requirements.

Data Ownership

Your data is your data. This is not a marketing statement — it is a contractual commitment. Everything Core learns from your organization belongs to your organization. If you leave the platform, your data leaves with you. Core''s learned intelligence about your business does not become Centsible''s asset.

This is the opposite of how most AI platforms work. Most platforms learn from their users'' data to improve their models for all users. Core learns from your data to improve the model for you alone.

The Security Posture

Beyond data isolation, the platform implements standard enterprise security controls: encryption at rest and in transit, role-based access controls, multi-factor authentication, audit logging, regular security assessments, and incident response procedures.

These are not differentiators — they are baseline requirements. The differentiator is the architecture: single-tenant infrastructure that makes data isolation a physical property of the system rather than a policy promise.

Coredata privacyHIPAAattorney-client privilegecomplianceCentsibleAIsecurity
B

Brent Gephart

25+ years across payment infrastructure, fintech M&A, and AI platform design. Founder of Centsible Consulting.

Monthly briefing on payment infrastructure.

One email per month. No marketing. Written for operators and investors who need to understand how this stuff actually works.