Title: Policies %E2%80%94 LLM EU
Canonical: https://llmeu.com/en/docs/policies/
Markdown mirror: https://llmeu.com/en/docs/policies.md
Machine-readable: https://llmeu.com/llms.txt (index) - https://llmeu.com/llms-full.txt (full catalogue) - https://llmeu.com/llms-catalogue.json

Get started

- [Quickstart](/en/docs/quickstart/)
- [Console](/en/docs/console/)
- [Migration](/en/docs/migration/)
- [API reference](/en/docs/api/)

Reference

- [Authentication](/en/docs/authentication/)
- [Endpoints](/en/docs/endpoints/)
- [Errors](/en/docs/errors/)
- [Rate limits](/en/docs/rate-limits/)
- [Streaming](/en/docs/streaming/)
- [Policies](/en/docs/policies/)
- [Routing and policy](/en/docs/routing/)
- [Residency and regions](/en/docs/residency/)
- [Evidence and verification](/en/docs/evidence/)
- [OpenAI compatibility](/en/docs/openai-compat/)

Operate

- [Self-hosting](/en/docs/self-hosting/)

# Policies

The policy object that decides what an organization may call, where it may run and what it may spend, field by field.

A policy is stored per organization and read on every inference request. The defaults are the safe ones: EU-owned or EU-region hosting, zero retention, public and internal data only, a trace required.

## Fields

## Which policy applies

A request may name one with llmeu.policy_id. Without it, the organization's default policy applies. A policy_id that belongs to another organization is refused with policy_not_found, because the lookup is always scoped to the organization the key belongs to.

```
"llmeu": { "policy_id": "the-uuid-from-the-console" }
```

Because the default policy applies to every key, an organization's residency promise is not something a caller can opt out of by omitting a field.

## The order the rules run in

Endpoint kind first %E2%80%94 a catalogue-only entry is rejected before anything else %E2%80%94 then status, then the residency class and region, then the provider and model lists, then the partner rule, vision, context size and price. The full sequence, with the failure code each step produces, is on the routing page.

## Editing

In the console, or with PUT /platform/v1/policies/{id} using a key that carries platform_write. A change applies to the next request; a request already in flight keeps the policy it started under.