# Regions and data residency

> Choose where your visitors' data lives. Each organization belongs to one region, and identification data never leaves it.

Last updated: 2026-09-17

Fingerly runs a separate data plane in each region. Your organization belongs to one region, chosen once, and the data about your visitors is collected, processed and stored there.

## Available regions

| Region | API | Key region | Status |
| --- | --- | --- | --- |
| United States | `https://us.api.fingerly.io` | `us` | Available |
| European Union | `https://eu.api.fingerly.io` | `eu` | Coming soon |

## Choosing a region

The owner chooses the region when setting up a new organization. The choice is permanent: an organization cannot move between regions. To use two regions, create an organization in each.

## What stays in the region

| In your region | In the United States |
| --- | --- |
| Identification events and archived submissions | Accounts and sign-in |
| Visitor identifiers | Organizations, members and invitations |
| SDK keys and proxy keys | Billing and payments |
| Risk weights and thresholds |  |
| Webhook endpoints, secrets and deliveries |  |
| Analytics, queues and backups |  |

When you view visitor data in the dashboard, your browser reads it directly from your region's API. It does not pass through the United States.

## Routing

- Every key carries its region, and the SDKs send requests to that region's API automatically.
- A key presented to another region's API is refused.
- A [proxy](https://docs.fingerly.io/docs/proxy-integrations) forwards only to the region in its proxy key.

> **Note:** Where a CDN or your own proxy processes requests before they reach Fingerly is governed by that provider's settings, not by Fingerly.