Security review should not require a second sales call.

Monitoring signals are reviewed regularly, and critical alerts are handled through the incident response workflow.

Duvo follows a documented incident response plan aligned with NIST computer security incident response guidance.

Encryption at rest and in transit is enforced across the service and its supporting platform architecture.

Encryption keys are managed through managed services rather than ad hoc operator processes.

Company endpoints are required to maintain encryption as part of the baseline security posture.

Availability monitoring is in place to maintain service continuity against service-level expectations.

Availability alerts are reviewed and addressed according to engineering operating procedures.

The service is deployed on redundant cloud architecture designed to reduce single points of failure.

Access controls include role-based permissions, network protections, and other controls to limit unauthorized access.

Access to critical systems and delivery resources is reviewed for appropriateness on a recurring schedule.

All user entities authenticate through unique credentials before they can access the service.

Human access can run through your identity provider with single sign-on.

Write access runs on scoped credentials you control: revoking them, or pausing the automation, stops the agent from acting in your systems.

Run history records each approval and every write-back to your systems. Export it to your security monitoring (SIEM) tools, with retention agreed in the contract.

Critical systems and resources require MFA as part of the internal access-control baseline.

Service architecture and data-flow diagrams are maintained and can be shared with customer reviewers.

Platform and external systems are scanned for vulnerabilities, with findings handled through a defined remediation policy.

Duvo does not train its own or third-party models on customer data. The trust portal lists an Anthropic zero-data-retention certificate, available for review on request. Retention depends on the selected provider, endpoint and configuration; agree those terms for your deployment. Model-provider retention is separate from the process records and audit logs Duvo retains.

Customer-managed and dedicated model endpoints can be scoped for supported processes. Review model compatibility, any external model-dependent steps, failure behaviour and operating responsibilities before treating a process as fully private. Changing a model requires evaluation and approval.

Duvo can arrange EU-only, single-tenant GPU capacity for model inference, or dedicated capacity in another agreed geography. The deployment agreement also specifies the locations of orchestration, browser and desktop execution, files and logs, plus support access and any exceptions. Model location alone does not establish residency for the whole service.

Access follows the scope of the user or role that starts the task. Tenant isolation is enforced across the application and data layers, and sensitive actions can require human approval.

Customer-specific context helps execute and review your work; it is separate from model training. Agree what context, files and audit records are retained, who can access them, retention periods and the exit handoff. Duvo minimizes retained data to what is needed for auditability and troubleshooting. Logs focus on actions and outcomes, data at rest is encrypted, traffic uses TLS, and run history stays auditable.