# NEXQ Documentation — Legal-Safe Version

This documentation surface provides technical and policy context for research, security, and deployment planning. It does not replace legal counsel, regulatory assessment, security certification, customer governance, or licensed medical judgment.

## Program statement

NEXQ is developing a research-stage, security-reviewed PACS-oriented web/mobile workflow concept for imaging-review and segmentation research. NEXQ does not publicly represent the system as world-first, fully quantum-encrypted, FDA-authorized, clinically validated, or production-ready for diagnosis or treatment planning unless those claims are separately substantiated and approved.

## Deployment requirements

- Intended-use memo and FDA/CDS/SaMD classification before any clinical, patient-facing, hospital, PACS, diagnostic, or treatment-planning workflow.
- BAA, DPA, security schedule, subprocessor approval, retention schedule, and role map before NEXQ receives, creates, maintains, transmits, or accesses regulated production data.
- TLS 1.3 where feasible; TLS 1.2 minimum only where risk-accepted and configured with approved cipher suites; HSTS, certificate lifecycle management, and origin controls required.
- MFA/RBAC where appropriate, audit logging, session controls, vulnerability management, incident response, and backup/restore testing before production.
- AI model cards, data provenance, evaluation records, bias/safety testing, drift monitoring, human review, and rollback plans before release.
- Product-specific Apple, Google, Samsung, and other app-platform data disclosures must match actual SDKs, permissions, backend data collection, and WebViews.

## Third-party names

Third-party product, platform, university, hospital, cloud, or technology names do not imply endorsement, affiliation, sponsorship, or partnership unless expressly authorized in writing.