Subprocessor register status — draft

Controlled-preview status: an approved public subprocessor register is not currently available.

DRAFT — NOT APPROVED AS A PUBLIC REGISTER. This page does not state that a provider is engaged, approved, contractually bound, located in a particular region, or configured with a particular retention or model-training setting.

Draft source reviewed: July 12, 2026

Effective date: Not established

Machine-readable public register: Unavailable

Candidate provider classes

Depending on the actual deployment, due diligence may be required for cloud infrastructure, identity, billing, email, model inference, error and performance monitoring, observability, DNS/CDN, support, and customer-communication providers.

This is a due-diligence denominator, not an approved vendor list. Customer-selected connectors and customer-held model keys also require a documented role analysis; they are not automatically excluded from review.

What an approved entry requires

For each actually engaged provider, Shielda must verify the legal entity and service, purpose and data categories, role, live configuration, processing and support locations, transfer mechanism, contract and security-review status, retention and deletion settings, model-training treatment, incident terms, downstream providers, and change-notification decision.

Publication gate

An accountable legal/privacy owner must reconcile the live provider inventory, approve each applicable entry, and confirm that the public register matches the preview or released deployment. Until then, provider logos, source imports, environment variables, and old lists must not be read as public commitments.

For an evaluation, contact Shielda for the provider and data-flow schedule applicable to that exact setup.