Security

Your data. Your clients' data.
Protected by architecture.

You're evaluating whether to give an external system access to your CRM and your client information. That's the right question to ask carefully. Here's exactly how the security architecture works — in plain language, not fine print.
Principles
Four commitments. Non-negotiable.
These aren't policy preferences. They are architectural constraints built into how Aether operates. They cannot be overridden, waived, or excepted.
Complete Data Isolation
Every partner firm's data exists in its own isolated environment. No partner can access, view, or be influenced by another partner's data. Every client within a partner's portfolio has its own isolated data room. Hard walls, not access controls.
No Cross-Partner Sharing
Your firm's data — financials, client information, strategic plans, deliverables — is never visible to any other partner firm. No "anonymized benchmarks." No "similar firm" recommendations derived from your specifics. Your data stays yours.
No Model Training
Partner and client data is never used to train, fine-tune, or improve AI models. Your engagement data serves your engagement. Period. This is a contractual commitment, not a policy preference.
Client Invisibility
Your clients never interact with CYPHR systems. They never see Aether. They never know the operating architecture exists. Every touchpoint is through your team, under your brand, within your client relationship.
Architecture
How data isolation works.
Aether's data architecture operates at two levels — partner isolation and client isolation within each partner. Both are structurally enforced.
Partner Level
Firm-to-firm isolation
Each partner firm operates in a completely separate environment. Your firm's data, configurations, client information, deliverables, and intelligence outputs are invisible to every other partner. There is no shared data layer across partner firms. The architecture treats each partner engagement as if it were the only one.
Client Level
Client-to-client isolation within your firm
Within your firm's environment, every client engagement operates in its own data room with strict access controls. Client A's financials, contracts, and strategic information are not accessible when working on Client B's deliverables. Isolation is maintained at the data room level — not through permissions, but through architectural separation.
Intelligence Layer
Pattern recognition without data exposure
Aether builds your firm's institutional knowledge by recognizing patterns across your engagements — but the intelligence layer operates on abstracted insights, not raw client data. Your firm benefits from accumulated wisdom. Individual client confidentiality is never compromised to produce it.
Data Ownership
Everything remains partner property
All data generated during your engagement — deliverables, analysis, intelligence briefings, knowledge base content — remains your firm's property. If the engagement ends, your data is exported in a standard format and purged from CYPHR systems within 30 days of termination.
CRM Security
Salesforce API security.
Aether connects to your Salesforce instance through secure, scoped API integration. Here's exactly what that means and what it doesn't mean.
OAuth 2.0 Authentication
All Salesforce connections use OAuth 2.0 with refresh token rotation. No stored passwords. No service account credentials saved in plaintext. Authentication tokens are encrypted at rest and expire on a defined schedule.
Scoped Permissions
Aether requests only the specific Salesforce permissions required for the selected engagement level. At the Aether level: read-only access to client context fields. At the Business Development level: read-write access to pipeline objects. Nothing more is requested or granted.
Encrypted Connections
All data in transit between Aether and your Salesforce instance travels over TLS 1.3 encrypted connections. No data passes through intermediary systems. The connection is direct — Aether to your Salesforce API endpoint.
Audit Trail
Every API call Aether makes to your Salesforce instance is logged — what was accessed, when, and by which Aether process. These logs are available to your firm on request. Full transparency into what the integration does and doesn't touch.
You control the connection. Your Salesforce administrator grants and can revoke Aether's access at any time through standard Salesforce connected app management. If you want to disconnect, you disconnect. There's no lock-in at the CRM integration level.
Infrastructure
Where Aether runs.
Cloud-primary architecture with local failover. Designed for continuous availability with no single point of failure.
Primary Compute
Cloud Infrastructure
Aether runs on enterprise cloud infrastructure with multi-region redundancy. Production workloads are distributed across availability zones. Automated failover ensures continuity if any single region experiences an outage.
Local Failover
On-Premises Node
A dedicated local server provides data sovereignty and emergency failover capability. If cloud infrastructure becomes unavailable, the local node maintains operational continuity. Staging and testing workloads run locally by default.
Monitoring
Three-Layer Alerting
Aether self-monitoring runs continuous health checks. External uptime monitoring provides independent verification. Escalation alerts reach the operations team via phone for critical incidents. No issue goes undetected.
99.9%
Uptime SLA
24/7
Availability
Multi-Region
Redundancy
Confidentiality
Contractual protections.
Beyond the architectural security, every CYPHR RED engagement includes formal contractual protections.
Mutual NDA
Every partner engagement begins with a mutual non-disclosure agreement. Your firm's information is protected. CYPHR's proprietary architecture is protected. Neither party can disclose confidential information without written consent.
Data Handling Protocols
Strict data handling protocols govern how partner and client information is stored, accessed, processed, and — when the engagement ends — exported and purged. These protocols are defined in the engagement agreement, not a separate policy document you have to find.
Access Controls
Within CYPHR, access to partner data is restricted to the Aether processes and principals directly involved in the engagement. There is no internal "browse" capability across partner environments. Access is scoped, logged, and auditable.
Termination Rights
If you end the engagement, your data is exported to you in a standard format and fully purged from CYPHR systems within 30 days. No residual data. No retained copies. No "we might need this later" exceptions.
Governance
Security terms at a glance.
Data isolation Per-partner + per-client architectural separation
Cross-partner sharing Never
Model training on partner data Never — contractual commitment
Salesforce authentication OAuth 2.0 with token rotation
Data in transit TLS 1.3 encrypted
API audit trail Full logging, available on request
Uptime commitment 99.9% availability SLA
Confidentiality Mutual NDA on every engagement
Data ownership All data remains partner property
Post-termination purge Full export + deletion within 30 days
Client visibility to CYPHR None — architecturally enforced
Questions about security?
We expect you to diligence this thoroughly. Your clients trust you with their information. You need to trust whoever you give access to. Let's have that conversation directly.
Start a Conversation Explore the Architecture
red@cyphrgroup.com · red.cyphrgroup.com

CYPHR RED is a division of CYPHR, an AI-native advisory and operating firm. CYPHR provides document preparation and advisory services. CYPHR is not a law firm, accounting firm, or licensed professional services provider. Deliverables are produced as business documents and do not constitute legal advice, tax advice, or professional opinions requiring licensure. Partner firms are responsible for all client-facing representations and licensed professional obligations. Security commitments described on this page are enforced through engagement agreements.

CYPHR RED | The Key
The Advisory Engine for Advisory Firms · March 2026