Security
Your data. Your environment. Your control.
Security details should be concrete before your team connects a source. This page describes the launch model; each pilot receives deployment-specific documentation.
Last updated October 20, 2026
Deployment model
Notrix is designed for customer-controlled cloud deployment. The exact architecture, cloud account, region, network boundaries, and operational responsibilities are documented before a pilot begins.
Data storage and processing
Connected company knowledge remains in the storage locations agreed for the deployment. Notrix processes only the information needed to retrieve sources and produce an answer. Customer data is not used to train shared models.
Identity and permissions
Workspace access is tied to approved identities. Source permissions and deployment policy determine which material a user may retrieve. Administrators control connected sources and user access.
Notrix access
Notrix personnel do not receive routine access to customer knowledge. Any temporary support access must be authorized, limited to the required purpose, and removed when the work is complete.
External providers
Cloud, model, monitoring, and support providers vary by deployment. Providers that may process customer information are identified during security review and documented in the applicable agreement.
Retention and deletion
Retention follows the agreed deployment configuration. At the end of a pilot or service term, customer-controlled resources can be disconnected and Notrix-held service data is deleted according to the written agreement, subject to legal obligations and documented backups.