# Security and data

Product: AI Universe
Source: https://docs.fortytwo.io/ai-universe/governance/security-and-data/

AI Universe is built so that the questions you would ask in a security review have short answers.

## Where your data lives

Everything runs in **your own Azure subscription and Entra tenant**: the apps, their databases, the models, the logs and the platform itself. You choose the Azure region at install.

Fortytwo has no access to your deployment. The only connections to Fortytwo are the releases you pull when you upgrade, and the licence check.

## How it is reached

| Path | Protection |
|-|-|
| Browsers, to the control panel and apps | One Application Gateway with a web application firewall in prevention mode. Nothing else is reachable from the internet. |
| Sign-in | Your own Entra ID, with your Conditional Access policies. Each app has its own registration and only lets in the people given access to it. |
| AI and API calls | Through Azure API Management only. The platform's internal services accept calls from nothing else. |
| Optionally, by network | Install with restricted access to allow only your own IP ranges. |

## How every AI call is governed

- **One gateway.** Every model call from every app goes through the AI gateway. Apps hold no model keys, so they cannot bypass it.
- **Safety rules** on every question and reply. See [AI and models](https://docs.fortytwo.io/ai-universe/control-panel/ai/#safety-rules).
- **Allowed tools only.** An agent can only use the tools switched on for it. See [Agents](https://docs.fortytwo.io/ai-universe/apps/agents/).
- **One switch to stop it all.** See [Pause all AI](https://docs.fortytwo.io/ai-universe/control-panel/ai/#pause-all-ai).
- **A record.** Usage is recorded for cost, and a fingerprint of every AI response is kept for compliance. See [Compliance](https://docs.fortytwo.io/ai-universe/governance/compliance/).

## Secrets

Secrets are kept in Azure Key Vault and referenced from there. They are never stored in code, in the database or in build pipelines. Deployments from GitHub sign in to Azure without stored secrets.

## Least privilege

Each part of the platform runs with its own managed identity and only the permissions it needs. The identity that runs approved repairs, for example, can only read and start the platform's jobs.