> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getvirtualbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Security and Compliance

> Certifications, data handling, encryption, and access controls

Your client data stays yours. VirtualBrain meets the security standards that enterprise buyers and their clients expect.

## Certifications and Compliance

| Certification     | Status    | Description                                                |
| ----------------- | --------- | ---------------------------------------------------------- |
| **ISO 27001**     | Certified | International standard for information security management |
| **SOC 2 Type II** | Compliant | Controls for security, availability, and confidentiality   |
| **GDPR**          | Compliant | European data protection regulation                        |

<Info>
  Our ISO 27001 certificate and SOC 2 Type II report are available from the [Trust Center](https://trust.getvirtualbrain.com), alongside the active control list and our declared subprocessors. For anything it doesn't cover, contact your account manager or email our DPO, [terence@getvirtualbrain.com](mailto:terence@getvirtualbrain.com).
</Info>

## Data Handling

### A Dedicated, Secure Environment

VirtualBrain runs in a dedicated secure environment for your organization, designed for the confidentiality standards enterprise clients expect:

* **EU-hosted infrastructure**: Your documents and data are processed and stored in the European Union, on a hybrid AWS and Azure architecture running primarily in Paris with nodes in Frankfurt
* **Enterprise AI models**: Answers are generated by frontier models served through AWS Bedrock and Azure AI Foundry, hosted in the EU with no transfer outside EU borders, under a zero-retention, zero-training policy
* **Permission mirroring**: Synced cloud sources keep their original access rules; nothing is widened by connecting them
* **You control deletion**: Remove documents at any time; deleting a Brain removes its documents and their stored extracts, including deliverables. Brain data is securely deleted within 30 days of deletion or disconnection, and an administrator can request full deletion of all company data

### Your Data Never Trains Models

VirtualBrain does not use your documents or queries to train AI models. Your data is used exclusively to provide you with answers.

| Data Type                         | Used for Training? | Retained?                                                           |
| --------------------------------- | ------------------ | ------------------------------------------------------------------- |
| Documents from a connected source | No                 | No original stored; only extracted text and key visuals are indexed |
| Manually uploaded documents       | No                 | Yes, as an encrypted copy in your Brain                             |
| Chat queries                      | No                 | Yes, in your history                                                |
| App outputs                       | No                 | Yes, for your reference                                             |

### Data Encryption

* **In transit:** TLS 1.2 / 1.3 encryption for all data transfers
* **At rest:** AES-256 encryption for stored documents, with column-level encryption on extracted text and encryption keys held in AWS KMS and Azure Key Vault

### Data Residency

All customer data is hosted on European Union servers by default:

* **European Union**: Default for all customers, with data centers in Paris and Frankfurt. No data flows outside the EU
* **Custom regions**: Contact your account manager

## Access Controls

### Authentication

VirtualBrain supports two ways to sign in:

* **Email and password** sign-in, with multi-factor authentication.
* **Single sign-on (SSO)** with Google and Microsoft work accounts over OpenID Connect, including Microsoft Entra ID (formerly Azure AD) tenant configuration. When SSO is enabled, you sign in with the work account you already use, with no separate VirtualBrain password to create or rotate, and access follows your firm's existing identity controls for joiners and leavers.

SSO is configured with the VirtualBrain team during your organization's deployment; there is no customer-side setup to perform. If sign-in with your work account isn't available yet, contact your VirtualBrain administrator or your account manager.

### Permissions Model

Access in VirtualBrain is controlled at two levels:

| Level                        | How it works                                                                                                                                                                             |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Workspace administration** | Administrators manage users, teams, integration policy, usage, and company templates through the [Admin Dashboard](/features/admin-dashboard/overview). Admin access is role-restricted. |
| **Per-resource sharing**     | **Brains and Apps are private to their owner by default** and shared explicitly: a named individual at full access or read-only.                                                         |

### Brain-Level Permissions

Each Brain has its own access controls:

* **Private**: Only you can access (the default)
* **Specific users**: Grant a named colleague Full access or read-only
* **Teams**: Share with a whole team at once.

Cloud-storage integrations also [mirror source permissions](/features/brains/connectors): a colleague who can't open a folder in the source system can't see its contents through VirtualBrain either.

## Infrastructure Security

### Cloud Infrastructure

VirtualBrain runs on enterprise-grade cloud infrastructure:

* Hybrid AWS and Azure architecture, in SOC 2 certified EU data centers
* Multi-AZ architecture with at least 99.95% availability, resilient to the loss of a data center
* Daily backups stored in a separate region
* AWS WAF and AWS Shield for DDoS protection, with a single entry point (one load balancer, TCP/443 only) into a segmented VPC

### Application Security

* Annual penetration test by Bastion Technologies
* Quarterly vulnerability scans (Qualys)
* Peer code review on every change
* Secure development lifecycle (SDL)
* Bug bounty program

## Audit and Monitoring

### Activity Logs

Enterprise plans include comprehensive audit logs, exportable on demand:

* User login/logout events
* Document uploads and deletions
* Brain access and modifications
* App runs and query history

### Retention

* **Standard plans:** 90-day activity log retention
* **Enterprise:** Customizable retention periods

## Incident Response

VirtualBrain maintains a documented incident response plan:

1. **Detection**: Automated monitoring and alerting
2. **Containment**: Immediate isolation of affected systems
3. **Notification**: Customer notification within 24 hours
4. **Recovery**: Full restoration and root cause analysis

## Vendor Security

We vet all third-party vendors for security:

* Cloud and AI infrastructure, AWS (Bedrock) and Microsoft Azure (AI Foundry). The enterprise agreements are with AWS and Microsoft, not with the providers whose models run on their platforms
* No data sharing with sub-processors without consent
* Regular vendor security assessments

## Security Contact

For security questions, concerns, or to report vulnerabilities:

* **Email:** [terence@getvirtualbrain.com](mailto:terence@getvirtualbrain.com), our DPO
* **Response time:** Within 24 hours

<CardGroup cols={2}>
  <Card title="Trust Center" icon="file-certificate" href="https://trust.getvirtualbrain.com">
    ISO 27001 certificate, SOC 2 Type II report, active controls, and declared subprocessors
  </Card>

  <Card title="Enterprise Security" icon="shield" href="mailto:kata@getvirtualbrain.com?subject=Enterprise%20Security%20Requirements">
    Discuss custom security requirements
  </Card>
</CardGroup>
