> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.lakera.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.lakera.ai/_mcp/server.

# Data Regions

Check Point AI Guardrails allows you to control where your API requests are **processed** and where your logs are **stored**. These are two independent settings, giving you flexibility to optimize for both latency and compliance.

## Processing Regions

The processing region determines where AI Guardrails runs its detectors on your screening requests. You control this by choosing which API endpoint to send requests to.

### Available Endpoints

| Endpoint                               | Processed in         | `allowed_processing_regions` value |
| -------------------------------------- | -------------------- | ---------------------------------- |
| `https://eu.api.lakera.ai`             | EU                   | `eu-south-2`                       |
| `https://us.api.lakera.ai`             | USA                  | `us-east-1`                        |
| `https://ap-southeast-1.api.lakera.ai` | Singapore, Asia      | `ap-southeast-1`                   |
| `https://api.lakera.ai`                | Closest of the above | any of the above                   |

> **Warning**
>
> It is your responsibility to use the correct endpoint for your desired processing region. Check Point does not automatically route requests to a specific region - requests are processed wherever they are sent.

## Storage Region

The storage region determines where your AI Guardrails logs are persisted. You can configure this in the AI Guardrails Dashboard under **Settings > Data regions** using the `storage_region` setting.

The default storage region is **EU**.

> **Warning**
>
> The storage region is set when the organization is created and cannot be changed afterwards. If you need logs stored in multiple regions, use separate organizations. Contact [Check Point support](mailto:support@lakera.ai) for help with initial setup.

## Allowed Processing Regions

The `allowed_processing_regions` setting lets you restrict which regions are permitted to process your requests. This is an enforcement mechanism, not a routing control.

If a request is sent to an endpoint in a region that is **not** in the allowed list, the gateway rejects it with a `4xx` error.

You can configure this in **Settings > Data regions** in the AI Guardrails Dashboard. If not set, all regions are allowed by default.

## Platform Logs

The `region` field shown in the platform logs refers to the **processing region**, which can differ from the storage region. If you see unexpected region values in your logs, verify that your application is using the correct API endpoint.

## Examples

### Process and store everything in the EU

To guarantee that all requests are processed and stored in the EU:

1. Set `allowed_processing_regions` to `["eu-south-2"]`
2. Keep the default `storage_region` (EU)
3. Point your application to `https://eu.api.lakera.ai`

With this configuration, any requests sent to other regions (e.g. `us.api.lakera.ai`) will be rejected with a `4xx` error.

### Global processing with US storage

To allow processing in any region (for lower latency) while storing all logs in the US:

1. Leave `allowed_processing_regions` unset (defaults to all regions)
2. Set `storage_region` to **US**
3. Use whichever regional endpoint provides the lowest latency for your application