Trust & residency

Know where identity data goes.

Covenant plans to offer hosting in Canada and the European Union. Every service that handles identity data must use a non-US provider, including the services behind sign-in and recovery.

Regional design

Each region earns approval

  • CanadaFirst invite-only pilot candidate
  • European UnionSeparate deployment and review

Each region has its own planned issuer, database and backups.

Processor review

Follow the identity data

  1. Sign-in trafficEdge access and encryption termination
  2. StorageIdentity database, backups and audit logs
  3. SupportRecovery and operations access

The non-US provider requirement applies at every step.

Review the trust details

Which services handle identity data?

For each service, Covenant must verify who operates it, where it processes data, and who can access it. The review includes downstream providers.

Traffic and hosting

The policy covers infrastructure and edge services handling sign-in traffic, including services that terminate encrypted connections.

Storage and recovery

The review includes identity databases, backups, audit logs, and services that send recovery emails or handle recovery requests.

Operations and support

Before launch, Covenant must verify where support and incident response teams can access identity data, including through monitoring tools.

What we verified locally

These checks used synthetic accounts in the local build. Each region needs its own production verification.

Sign-in and tokens

Browser tests exercised passkey enrolment, passkey verification, and OpenID Connect with PKCE S256. Keycloak rejected refresh-token reuse in the tested setup.

Customer access

Company domain verification uses an expiring DNS challenge. Issuing invitations and modifying reseller grants require recent identity verification.

Access changes

Workspace audit logs record who changed access and when. The local flow was tested for reseller revocation and cancellation of pending invitations issued through that grant.

What must pass before launch?

Verify the regional processor chain

Confirm service operators, downstream processors, and the locations of hosting, backups, and support access for each region.

Prove isolation and recovery

Test sign-in, session revocation, and access isolation across two unrelated customer projects. Time a backup restore and rehearse rollback using synthetic identities.

Complete independent security review

Verify the pilot’s controls, retest fixes, and confirm who owns incident response, patches, and access revocation before approving a region for real customer identities.