Data Residency

Overview

Every verification profile stores its data in one region: the United States or the EU. US is the default. You choose the region when you create a verification profile. US and EU profiles can sit side by side in the same organization, so you can serve both regions without a second account.

What it affects

Area	US profile	EU profile
Verification data storage	Stored in the US	Stored in the EU and stays there at rest
API endpoint	`api.trinsic.id`	`api.eu.trinsic.id`
Hosted verification endpoint	`verify.trinsic.id`	`verify.eu.trinsic.id`
Calls to identity providers	Made from the US	Made from the EU
Custom domains	US domains only	EU domains only

Verification data covers identity attributes, document images, provider responses and encrypted data.

Endpoints: Sessions for an EU profile must be created and completed on the EU endpoints. A call to the US endpoints for an EU profile fails with an error saying the profile is set to EU residency.
Custom domains: A custom domain belongs to one region. If you already use a custom domain such as verify.example.com for US profiles, your EU profiles need a separate hostname, such as verify.eu.example.com. Trinsic handles TLS for custom domains, so the only choice you make is the region.
Provider registrations: Some providers require redirect or callback URLs to be registered on their side. For EU profiles, those URLs are on verify.eu.trinsic.id or your EU custom domain. Trinsic handles this for the registrations it manages. If you use your own provider credentials, you may need to add the EU URL in that provider's portal.

What stays the same

Dashboard: You manage all profiles from the same dashboard, whichever region they use.
Relying parties: Branding and provider registrations on a relying party can be reused across US and EU profiles.
Integration: Apart from pointing EU sessions at the EU endpoints, your integration doesn't change.
Data retention: Retention is set per verification profile, so you control it separately for each region.

Setting up an EU profile

Create a new verification profile and choose EU as its data residency.
Select or create the relying party it will use.
If you use a custom domain, request an EU domain in the Domains tab. The DNS records appear in the dashboard once you submit the request.
Enable your providers as usual.
Point your integration at api.eu.trinsic.id and verify.eu.trinsic.id for sessions on this profile.

A profile's region is locked once it records its first session. To change regions after that, create a new profile.

FAQ

Can I change an existing profile's region?
Trinsic can change this for you, only before it records its first session. After that, create a new profile in the region you need.

How do I tell which region a profile is in through the API?
The List Verification Profiles endpoint returns each profile's region and lets you filter by it.

Are all providers available in both regions?
Contact your Customer Success Manager to confirm availability for the providers you need in the EU.

Does EU residency change what my end users see?
No. The verification flow looks the same. Only the hostname changes, unless you use a custom domain.