Security and trust

Your prosecution history is your competitive advantage. It stays yours.

NOA's whole value depends on being trusted with privileged, unpublished, client-confidential material. We designed the data boundary before we designed the product.

Encryption

Data is protected in transit and at rest.

Tenant isolation

Customer environments remain logically separated.

Access control

Permissions follow organization, role, and matter.

Traceability

Relevant system activity remains reviewable.

Data boundaries

Customer information stays within defined controls

Data boundary diagram showing authorized users, controlled access, the NOA customer environment, tenant boundary, authorized outputs, approved export, and external model training not used.

Security by design

Controls across the full workflow

Encryption at rest

Stored matter content remains protected.

Encryption in transit

Connections use protected transport.

Role-based permissions

Access is limited by assigned responsibility.

Tenant separation

Organizations remain logically isolated.

Controlled retention

Data lifecycle follows configured policy.

Reviewable activity

Relevant actions can be traced.

Secure development

Changes follow disciplined review practices.

Incident response

Defined procedures guide investigation and notice.

FAQ

Is our client-confidential material used to train your models?

No. Your data trains a style profile that is available only to your organisation. It never contributes to any model or capability offered to another customer.

How is access to matters controlled?

Access is governed through role-based authorization, tenant-level separation, and customer-specific entitlements. Users can access only the matters, workspaces, and environments approved for their organization and role.

Can customers define retention requirements?

Yes. Retention policies can be aligned to customer requirements, including configured data lifecycle controls, backup retention, and environment-specific governance needs.

How is data protected during processing?

Data is protected through encrypted transport, controlled access paths, and isolated processing environments. Access to customer content is limited by approved permissions and governed throughout the workflow.

What activity can be reviewed or audited?

Relevant administrative, access, configuration, and application activity can be reviewed to support oversight, security reviews, and customer reporting. Audit scope can be expanded as customer governance needs mature.

Does NOA support security reviews?

Yes. NOA can support customer security reviews with documentation covering architecture, access controls, data protection, operational safeguards, and the boundaries that govern customer information.

Security questionnaires

Requests for security documentation and completed vendor questionnaires may be directed to us. We respond to all such requests in writing.

Contact security