Industry
Standards & Terms

01 Client-Side Execution & Hardware Gating

Enclave Nexus is a browser-native software console that runs SQLite (WASM) and DuckDB calculations locally on the user's workstation.

Consequently, computational speeds, memory limitations, and processing limits are strictly governed by the user's hardware specifications (GPU capacity, VRAM, and browser capabilities). Sierra Holdings Inc. is not responsible for query failures, memory exhaustions, or visual lags resulting from hardware constraints.

02 Zero-Trust Credentials & BYOK (Bring Your Own Key)

To facilitate advanced reasoning models, Enclave Nexus incorporates a BYOK architecture where users enter their own API keys (e.g., OpenAI API, Anthropic Claude API, or other third-party cloud reasoning API keys) directly into their workstation configuration settings.

These credentials are encrypted client-side using industry-standard cryptography (AES-GCM 256-bit) and stored inside your browser's private state database. You are entirely responsible for protecting your credentials. Under no circumstances will Sierra Holdings Inc. have access to, or assume liability for the exposure, theft, or billing charges of API keys uploaded by the user.

03 Third-Party Connections & External Integrations

Users may optionally authorize Enclave Nexus to establish out-of-band integrations to external databases, enterprise data warehouses, or third-party cloud spreadsheet and file storage tools.

The application acts strictly as a local routing bridge. Any API tokens received via authentication remain stored locally in your browser cache. You are responsible for ensuring that your integrations adhere to your organization's security directives and the respective third-party terms of service.

04 Security Standards Compliance

Enclave Nexus is developed in adherence to federal and international security standards:

• NIST SP 800-63B Alignment: We utilize state-of-the-art authentication protocols (such as SAML/OIDC identity brokerage via Auth0) to ensure secure logins.
• FIPS 140-2 Compliance: Local dataset state packages exported from the app utilize AES-256-GCM authenticated encryption.
• Tamper-Evident HEC Telemetry: System events are hashed using SHA-256 HMAC keys before routing to user-configured Splunk SIEM endpoints.

05 Limitation of Liability

Sierra Holdings Inc. provides Enclave Nexus "as is" and "as available". We do not warrant that the application will run without interruption, remain error-free, or be completely secure from local system hacks. We disclaim all liability for any direct, indirect, incidental, or consequential damages resulting from data loss, local hardware failures, or network disruptions.