Security & Sovereignty

Data Retention Controls

In production deployments on your infrastructure, data retention is governed by your configuration. You can run in a zero-retention mode and enable local activity journaling only when needed. MX4 does not use customer production data to train base models unless you explicitly opt in.

Encryption

• In Transit: Data is protected with TLS. mTLS is available for private cloud and air-gapped deployments.
• At Rest: Encryption at rest is supported for models and activity journals. Keys can be managed by your own HSM or KMS.

Infrastructure Activity Journal

API requests, model inferences, and configuration changes can be logged locally and optionally signed. Retention and export are controlled by your infrastructure policy.

Data Residency Controls

Data residency is enforced by deployment topology and network isolation.

• Compute Residency: Inference runs on servers in your approved region.
• Storage Residency: Models, embeddings, and training data stay within your infrastructure boundary.
• Backup Residency: Backups can be kept within the same approved region or facility based on your backup policy.
• Zero Transit: No external routing by default; external providers require explicit configuration.

Incident Response

Incident response is owned by your security team. MX4 provides guidance and escalation support for Enterprise deployments.