Security stated precisely.
Architecture
Security architecture may include encryption in transit, encrypted storage, authenticated access, and hardened operating policies. The scope of encryption, including transit, storage, key management, and any end-to-end guarantee, is specified separately for each deployment.
Each MEOS environment is deployed as a client-branded instance with its own identities, records, and operating policies. The infrastructure it runs on, and the degree to which it is dedicated or segmented, is chosen with the client and recorded in the deployment specification. See the platform overview for what the environment contains.
Access and approval
Each enabled channel has a defined authentication method and action scope, validated before release. Channel identity alone is not sufficient authority for a business transaction. What a person can see and do is scoped to their role and the organization’s approval policies, not to the channel they arrive on.
MERCURY retrieves information and prepares documents over remote channels. Transaction execution over telephone or shared channels is enabled only with channel-specific authorization, action scopes, confirmation, approval, and testing. Material business actions require appropriate permission and, when configured, human approval. Multi-step actions run with validation and leave an audit record of what changed.
Governance
Operational logging and audit trails record who accessed what, what was changed, and what was approved, so the operational record stays transparent to the organization that owns it. Backup, restore, and continuity procedures are defined and tested as part of the deployment, and sensitive data can be segregated from day-to-day working data where the organization requires it.
Key management, retention, and access review follow the contracted configuration. Where a client’s requirements call for it, the security architecture is reviewed and tested independently before the environment is placed into operation.
Sovereign configurations
Choose dedicated infrastructure, specified data location and segmented environments where your requirements call for them. Isolation, residency, access control and independent review are specified and verified for the actual deployment; they are not implied by a package name.
AI boundaries and data separation
MERCURY retrieves information and executes supported authorized actions. CASSANDRA supplies forecasts and advice. A recommendation does not itself authorize an action. Knowledge permissions, data source access, execution roles and human approvals are configured separately and tested.
Customer data boundaries, retention, tenant isolation, model access and provider dependencies are defined in the architecture. Data from one customer is not made available to another through a shared assistant. The configured controls must be verified before operational use.
Updates, monitoring and response
Monthly MEOS licensing includes technical support, software updates, security updates and security monitoring for the agreed environment. Purchase customers can add these through an ongoing care agreement.
Included services apply to the agreed scope and coverage. Unlimited development, continuous staffed monitoring, guaranteed incident resolution and third-party fees are not implied. Monitoring and patching responsibilities depend on hosting, access and the service agreement.
The service agreement identifies monitored systems, monitoring hours, alert handling, escalation, patch approval and rollout, customer responsibilities and response targets. Customer-hosted environments require agreed access and responsibility boundaries.
Review purchase and licensing →