The Settings → Compliance page surfaces the data-processing transparency information specific to your organization’s region. It is the place to confirm where your data lives and which third parties may touch it.
Data residency
Section titled “Data residency”Every organization is pinned to a region at creation. The active organization’s region is shown at the top of the compliance page. Tenant data (applicants, verifications, workflow templates, audit history) stays inside that region for the life of the organization and is never replicated across regions.
If you need a different region for a different population of applicants, create a separate organization in that region. See Create an organization and Data residency.
Sub-processors
Section titled “Sub-processors”The page lists every third-party service that may process personal data on behalf of the platform for your region. Each entry shows:
- Name: the legal entity acting as a sub-processor.
- Category: the function it provides (infrastructure, identity verification, email delivery, and so on).
- Description: what the sub-processor does in the platform.
The list is the union of platform-wide sub-processors and the ones specific to your region, rendered together. The page also shows the list’s effective date: the date the list last changed.
Amazon Web Services: biometric verification and network relay
Section titled “Amazon Web Services: biometric verification and network relay”Amazon Web Services appears on the list for your region in two roles.
The liveness check. When a workflow template’s identity-document check uses an active-liveness biometric mode, Amazon Web Services handles the liveness check for your region. Biometric data is special-category personal data (GDPR Article 9), so it is handled under a separate residency commitment: an EU organization’s liveness check is pinned to the EU region (Ireland) and the resulting data is written to EU storage and never transits another region. No name, date of birth, address, email, or phone is sent for the liveness check. The raw video is not retained; only the reference image needed to match the face against the document is stored, and it follows the same encryption and erasure rules as the other identity-document images. See Biometric data for the full residency and retention detail.
The network relay. Some connected systems accept requests only from an allowlisted network address. Amazon Web Services hosts the fixed-address network relay for integrations with such a connected system. Only those integrations send traffic through the relay. The relay runs in your organization’s region (US East for the US region, Ireland for the EU region). It adds no network hop outside that region. The relay carries traffic to and from the connected system, wherever that system is hosted. So the relay does not keep that data in your region. The relay forwards encrypted traffic only and cannot read it. Nothing is stored on the relay.
Retention windows
Section titled “Retention windows”Retention controls are not configurable per-organization. Platform defaults apply and are described in the Data residency FAQ.
Legal agreements
Section titled “Legal agreements”The active legal agreements for the platform (Terms, DPA, and any region-specific addenda) are linked from the marketing site and are not customized per organization in this surface.
Audit access
Section titled “Audit access”Every privileged action on the organization (role changes, branding updates, invites, billing changes) emits an audit event. Review the trail in the Audit log.