Security
Security and Privacy
Nexus models your company across products. The privacy posture below describes how that data stays yours.
Cross-Product Data Boundaries
Nexus reads from your CLM contracts, CFO spend, HR workforce data, and any integrations you connect. All data stays inside your tenant boundary. The operational graph is per-tenant; node and edge tables enforce tenant scope at every query.
Never Aggregated Per-Tenant
When Nexus surfaces benchmarks (SaaS overlap rate, negotiation outcome percentiles, organizational complexity scores), the aggregate is computed across opted-in customers and only published when the count clears the k-anonymity threshold (k = 5). Customer identity is never written into the benchmark tables.
Explainability On Every Autonomous Action
Every Nexus playbook run records why it triggered, the confidence score, the impact analysis, the affected systems, and the rollback path. Nothing executes without an audit trail.
BYOK and Dedicated Tenants
Enterprise Secure customers can supply their own AI provider key (BYOK) so model calls bill to their account and never share inference state with other tenants. Dedicated isolated tenants are available for customers with strict data-residency requirements.
Encryption and Access
Tenant isolation is enforced via row-level data isolation in the database. Sessions use httpOnly, Secure, SameSite cookies plus a CSRF double-submit token. Files are stored with AES-256 server-side encryption. Encryption keys are stored using industry-standard symmetric encryption at rest. Internal service calls require a shared-secret header validated at each hop.