Professional Secrecy Agreement

Restricted routing for information protected by German § 203 StGB

If you are subject to professional secrecy under § 203 StGB, information entrusted to you in your professional capacity may require additional confidentiality safeguards.

Cortecs supports these workloads through a Professional Secrecy Addendum and routing restricted to a defined set of providers. Both measures are required for the setup described on this page.

Default routing is not suitable for § 203 workloads. By default, Cortecs may route requests across its broader provider pool. Do not submit information protected by § 203 StGB until the Professional Secrecy Addendum is in effect and restricted routing has been configured.

Set up restricted § 203 routing

1

1. Conclude the Professional Secrecy Addendum

Sign the Professional Secrecy Addendum with Cortecs GmbH. Contact [e-mail] to request it.

The addendum establishes the additional confidentiality obligations for the approved provider chain. It does not replace your Data Processing Agreement or other applicable data-protection terms, and it does not replace your own assessment of professional-law requirements or whether a particular disclosure is permitted and necessary.

2

2. Restrict routing to approved providers

Use only providers approved by Cortecs for restricted § 203 routing. You can apply the restriction at project level OR per API request:

• In the dashboard, go to Settings → Inference and select only providers from the approved list below.

• In an API request, pass the exact identifiers from the approved list in allowed_providers.

The addendum alone does not restrict routing and does not make default routing suitable for § 203 workloads.

UI example

In the dashboard, go to Settings → Inference and select only providers from the list of approved providers. Make sure your selection exactly matches the approved providers.

An example of a specific provider selection. Make sure it matches approved providers.

API example

curl 'https://api.cortecs.ai/v1/chat/completions' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <API_KEY>' \
  -d '{
    "model": "<MODEL_NAME>",
    "messages": [
      { "role": "user", "content": "<YOUR_MESSAGE>" }
    ],
    "allowed_providers": [
      "amazon_ireland",
      "amazon_paris",
      "ionos",
      "ovh",
      "aki",
      "infercom",
      "google",
      "berget"
    ]
  }'

When allowed_providers is set, Cortecs will not route or fall back to a provider outside that allowlist. If none of the listed providers can serve the request, the request fails. See Routing Concept for more information about routing parameters.

Approved Providers

Use the API identifiers exactly as shown or select them by name in the UI.

Name	Provider IDs	Legal entity
Amazon	amazon_ireland, amazon_paris	Amazon Web Services EMEA SARL
Ionos	ionos	IONOS SE
OVH	ovh	OVH SA
AKI	aki	AKI.IO GmbH
Google	google	Google Cloud EMEA Limited
Infercom	infercom	Infercom SCS
Berget	berget	Berget AI AB

Additional providers may be added to this list on a continuous basis. Customers should review this page regularly to stay informed of the current approved providers.