# SPQR Trust & Assurance | ISO and SOC Information

Canonical page: https://spqrtech.ai/trust/

Content edition: 2026-10-10

This Markdown edition is generated from the public page content.

---

SPQR / trust & assurance

# Inspect the assurance. *Confirm the scope.*

Security and governance information for teams evaluating SPQR, Praxis and Aegis.

Certification and assurance

## Request the evidence *that applies to your scope.*

### SOC 2 Type II

Controls independently examined. Request the applicable report, covered system and reporting period.

### ISO/IEC 27001

Certified information security management. Request the certificate, covered entity, scope and current validity.

### ISO/IEC 42001

Certified AI management system. Request the certificate, covered entity, scope and current validity.

Confirm the applicable legal entity, services, deployment and current documentation before relying on a statement for procurement. Certification and assurance do not guarantee that any specific AI action is safe or legally compliant.

[Request the assurance pack](https://spqrtech.ai/contact/#assurance)

The engineering conversation

## What must be explicit *before deployment.*

### Authority and custody

Name the policy approver, bundle signer, runtime activator and key custodian. Record how authority changes and revocations are verified.

### Enforcement coverage

Identify every governed operation and tool path, the credential holder and routes that could bypass the gate. Test fail-closed behaviour and recovery.

### Data and retention

Agree which action context, logs and decision evidence are processed, where they are hosted and the retention and deletion requirements.

### Contract and accountability

Confirm the contracting SPQR entity, deployment region, support arrangement, applicable assurance scope and service responsibilities.

Technical and security contact

## Start without *sensitive material.*

Contact Adam Mazzocchetti at [adam@spqrtech.ai](mailto:adam@spqrtech.ai) to request a security or assurance conversation. Start with a high-level description. Agree a secure route before sharing credentials, customer data, detailed vulnerabilities or restricted reports.

This page is not authorisation to test or attack SPQR systems. Controlled evaluations require agreed scope and permission.

One clear next step

## One request. *The relevant evidence.*

Tell us the product, deployment and assurance questions your team needs to evaluate.

[Request security and assurance information](https://spqrtech.ai/contact/#assurance)[Review controlled-test terms](https://spqrtech.ai/challenge/)

One workflow. Defined scope. A decision about fit.