Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions neuraltrust/data-privacy/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,7 @@ NeuralTrust ensures complete data privacy and regulatory compliance for AI monit

### Data Sovereignty Model

NeuralTrust's data sovereignty model ensures that your most sensitive information never leaves your cloud environment. All data processing occurs within your own infrastructure, giving you complete control over your data while still benefiting from advanced AI monitoring capabilities.

Our architecture separates sensitive data processing from control plane management. Your personal data, proprietary information, and confidential AI models remain in your environment, while only privacy-safe metadata is shared with our Control Plane for system management and compliance analytics.
Where your data is processed and stored depends on how you deploy. On **Hybrid**, the data plane runs in your own infrastructure: raw payloads stay there and only privacy-safe metadata is shared with our Control Plane. On **SaaS**, NeuralTrust processes and stores raw payloads, including the request bodies behind TrustGuard findings, in the region your workspace is provisioned in.

Where data lives depends on how you deploy. NeuralTrust offers **SaaS** and **Hybrid** — see [Deployment overview](/neuraltrust/deployment/overview).

Expand Down Expand Up @@ -89,13 +87,13 @@ Federated learning approaches enable decentralized AI model training that keeps

### Data Protection Controls

Comprehensive encryption protects data throughout its lifecycle, from initial collection through processing, storage, and eventual deletion. Our zero-knowledge architecture ensures that NeuralTrust personnel cannot access your raw data, even for support purposes.
Comprehensive encryption protects data throughout its lifecycle, from initial collection through processing, storage, and eventual deletion. Encryption is not the same as zero knowledge: on SaaS, raw payloads are stored by NeuralTrust, so access to them is governed by our access controls rather than made impossible. If NeuralTrust must not hold your raw payloads, deploy Hybrid.

Advanced anonymization techniques remove identifying information while preserving the statistical properties needed for AI monitoring. When testing and development require realistic data, synthetic data generation creates artificial datasets that maintain analytical utility without privacy risks.

Protection controls include:
- **End-to-End Encryption**: AES-256 encryption for all data at rest and in transit
- **Zero-Knowledge Architecture**: NeuralTrust cannot access your raw data
- **Hybrid deployment**: Keeps raw payloads in your own infrastructure, out of NeuralTrust's reach
- **Anonymization**: Advanced techniques to remove identifying information
- **Synthetic Data**: Generate artificial datasets for testing and development

Expand Down Expand Up @@ -129,13 +127,13 @@ Monitoring capabilities include:

### Audit & Certification

Independent validation of privacy controls provides assurance to stakeholders and demonstrates commitment to privacy excellence. Annual SOC 2 Type II audits validate security and privacy controls, while ISO 27001 certification demonstrates comprehensive information security management.
Independent validation of privacy controls provides assurance to stakeholders and demonstrates commitment to privacy excellence. ISO 27001 certification demonstrates comprehensive information security management. A SOC 2 Type II audit is in progress; NeuralTrust does not yet hold a SOC 2 report.

Privacy certifications provide industry-standard validation of privacy compliance, and regular penetration testing ensures that privacy controls remain effective against evolving threats.

Audit programs include:
- **SOC 2 Type II**: Annual independent security and privacy audits
- **ISO 27001**: Information security management certification
- **SOC 2 Type II**: Audit in progress — no report issued yet
- **Privacy Certifications**: Industry-standard privacy compliance validation
- **Penetration Testing**: Regular security testing of privacy controls

Expand Down
8 changes: 4 additions & 4 deletions neuraltrust/security/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Security-minded customers sometimes voice a concern that NeuralTrust itself migh
**Data security and encryption features:**
- **Customer-Managed Keys**: Full control over encryption keys through cloud KMS
- **End-to-End Encryption**: AES-256 encryption for data at rest and TLS 1.3 for data in transit
- **Zero-Knowledge Architecture**: NeuralTrust cannot access your raw data
- **Deployment-dependent data location**: On SaaS, raw payloads (including TrustGuard request bodies) are stored by NeuralTrust in your workspace's region. On Hybrid, they stay in your own infrastructure and only metadata reaches NeuralTrust — see [Data handling](/trustguard/data-handling)
- **Data Classification**: Automatic identification and protection of sensitive data
- **Secure Deletion**: Cryptographic erasure with verification
- **Backup Encryption**: Separate encryption keys with automatic rotation
Expand Down Expand Up @@ -95,13 +95,13 @@ NeuralTrust maintains a comprehensive vulnerability management program that incl

## Security certifications and compliance

NeuralTrust maintains industry-leading security certifications and compliance attestations to ensure our platform meets the highest security standards.

**Current certifications and compliance:**
- **SOC 2 Type II**: Annual independent security and availability audits
- **ISO 27001**: Information security management system certification
- **GDPR**: European Union data protection regulation compliance

**In progress:**
- **SOC 2 Type II**: Audit in progress. NeuralTrust does not yet hold a SOC 2 report; contact your NeuralTrust representative for the current status.

---

> **🔒 Security Commitment**: NeuralTrust provides enterprise-grade security with comprehensive threat detection, automated compliance, and zero-trust architecture that protects your AI monitoring environment while maintaining operational excellence.
7 changes: 4 additions & 3 deletions platform/compliance/eu-ai-act.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,10 @@ can cite against specific articles.
| [SIEM forwarding](/platform/alert-integrations) | Alert findings delivered as OCSF Detection Findings |

Retention is split by design. Audit events are kept 365 days. TrustGuard records
follow a per-team entitlement — 365 days by default — and expire on a fixed date set
when they are written, so changing entitlements later neither extends nor shortens
what is already stored.
follow a per-team entitlement set by your plan — 365 days on Enterprise — and expire on a
fixed date set when they are written, so changing entitlements later neither extends nor
shortens what is already stored. See [Data handling](/trustguard/data-handling#retention)
for every plan's window and the defaults that apply when none is recorded.

## Article 14 — Human oversight

Expand Down
2 changes: 1 addition & 1 deletion platform/compliance/iso-42001.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ provisioning. See [Data handling](/trustguard/data-handling).
- **Control configuration** — the policy set in force, its mode and its scope.
- **Operating evidence** — findings, and the request bodies behind them, credential-redacted and capped at 1 MiB.
- **Administrative trail** — [audit logs](/platform/audit-logs) retained 365 days, exportable as CSV or JSON.
- **Retention statement** — every record carries its retention plan and an absolute expiry stamped when written.
- **Retention statement** — records from a guard with a retention window carry its plan and an absolute expiry stamped when written; see [Data handling](/trustguard/data-handling#retention) for the defaults otherwise.

## Where NeuralTrust stops

Expand Down
26 changes: 18 additions & 8 deletions trustguard/data-handling.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -97,14 +97,24 @@ Details: [Attachments and SSRF](/trustguard/api/evaluate#attachments-and-ssrf).

## Retention

Retention is a **per-team entitlement**, not a single global default. Every stored record
is kept for the retention period in force when it was written and then deleted, so a
record written today expires on a fixed date — changing entitlements later does not
retroactively extend or shorten records already stored.
Retention is a **per-team entitlement** that comes from your plan, not a single global
default. When a guard has a retention window, every record it writes is stamped with an
absolute expiry — request time plus the window — and deleted after it. A record written
today expires on a fixed date, so changing entitlements later does not retroactively
extend or shorten records already stored.

For teams entitled to TrustGuard the default window is **365 days**. A shorter window can
be provisioned on request, so confirm your team's window with your NeuralTrust contact
rather than assuming the default.
| Plan | Retention window |
|---|---|
| **Free** | 7 days |
| **Standard** | 30 days |
| **Enterprise** | 365 days |

A stamped window applies equally to the finding and to its request body.

**If a guard has no retention window recorded**, its records are not stamped and the
storage defaults apply instead: findings are kept **90 days** from the event, and request
bodies **30 days** from ingestion. Confirm your team's window with your NeuralTrust
contact rather than assuming either value.

If you need a specific window contractually, or shorter than your current one, raise it
with your NeuralTrust contact — it is an entitlement change, not a policy setting, so you
Expand All @@ -123,4 +133,4 @@ If your threat model calls for storing less:
matched requests, so no detector runs on them and no record is produced. See
[Policies](/trustguard/concepts/policies).
- **Shorten retention.** Ask your NeuralTrust contact to provision a window shorter than
the 365-day default.
your plan's.
Loading