scoco.ai
Law & data protection

How to tell if a "German" AI phone assistant is a US wrapper

Whether a "German" AI phone assistant runs its own conversation logic or is a US platform with a German website can be checked: read the privacy notice and the sub-processor list, count the sub-processors, and ask for each station about the endpoint, the company and the transfer basis. "Servers in Germany" alone answers none of these questions.

This article is orientation, not legal advice. For your specific situation the topic belongs with your data protection adviser.

What "US wrapper" means — and why the question is fair

By "wrapper" we mean a provider that, at its core, resells someone else's platform: the website and the legal notice are German, but the telephony connection, speech recognition, the language model and the conversation logic run at a platform provider, for example one with its head office or its data paths in the US. This is not a scam, and it is not prohibited either. But it changes who actually processes your callers' data, how many parties are involved, and how far statements like "data protection made in Germany" carry. As the controller under the GDPR you have to know this, not guess at it: you may only use processors that provide sufficient guarantees (Article 28(1) GDPR), and you have to inform your callers about recipients and transfers to third countries (Article 13(1)(e) and (f) GDPR).

Step 1: read the privacy notice and the sub-processor list

The first test takes a few minutes: open the provider's privacy notice and, if published, its sub-processor list, and find the information on recipients or processors. Three findings are possible:

  • Specific names with registered office and role — a good sign. Here you can trace who processes what.
  • Only collective categories ("IT service providers", "cloud providers") — ask. In a privacy notice, categories are permitted (Article 13(1)(e) GDPR: "the recipients or categories of recipients"). For your own assessment you still need the names, in the data processing agreement at the latest: the European Data Protection Board (EDPB) expects controllers to have the identity of all sub-processors readily available at all times (Opinion 22/2024).
  • No information at all — ask explicitly for the list before you sign. Without it you cannot give an informed authorisation for the use of sub-processors (Article 28(2) GDPR).

Bear in mind: the privacy notice mainly describes what the provider processes itself as a controller — its website, customer accounts, its own demo lines. Which service providers process the calls to your business is set out bindingly in the sub-processor list that belongs to the data processing agreement. If a single voice AI platform shows up there as the central processor, that is a pointer to the architecture; ask which stations run through it.

Step 2: count and classify the sub-processors

Ask for the complete sub-processor list, as an annex to the data processing agreement or published. Then count and classify: how many parties are involved, where are they based, and who delivers the core service? What matters is the structure: does the provider run its own conversation logic and buy in individual components — or does it hand the entire call through to a platform that brings further sub-processors of its own? In the second case you are effectively not vetting one provider, but a chain whose links you did not choose yourself.

Step 3: ask about the endpoints

Even with European data paths, the precise question is worth asking: "which endpoints do speech recognition, the language model and speech output run on — EU or US? Which company operates them, and what does a transfer to the US rest on?" Some US providers of speech AI offer EU endpoints; a provider that uses them can name this for each station, with region and transfer basis. If the answer does not come, or is evasive, that is a finding. Keep asking until you know it for every station.

Honestly: US sub-contractors are not a knock-out criterion

US technology in the stack is not a blemish in itself — scoco.ai, too, uses services from US companies or a US group for speech recognition, the language model and speech output (details below). Legally, the GDPR does not prohibit transfers to the US: Chapter V permits them under conditions (Article 44), for example under the adequacy decision on the EU-US Data Privacy Framework for companies certified under it (Article 45) or with standard contractual clauses (Article 46(2)(c)). Whether that decision will hold is open: the General Court of the EU dismissed an action against it on 3 September 2025 (T-553/23), and the appeal before the Court of Justice is pending (C-703/25 P, as of 15 November 2026).

An EU endpoint keeps the data on servers in the EU. The company behind it, though, can be subject to US law that obliges it, when ordered by the authorities, to disclose data it holds or controls outside the United States as well (18 U.S.C. § 2713, introduced by the CLOUD Act). How far that reaches is not settled; how you weigh it is something to settle with your data protection adviser.

What you can check yourself is transparency: a provider that discloses every party involved, with its registered office and its transfer basis — including the awkward ones — can be checked. An origin claim like "data protection made in Germany" without a list of the parties involved cannot. What deserves scrutiny is not the US component in itself, but a gap between the advertising and the documentation.

The point behind "servers in Germany"

"Servers in Germany" can be limited to the hosting of the application, not the processing of the call. Despite a German server, your caller's audio can flow to other places for speech recognition and for the language model. Which is why it is the combination that counts: where it is hosted, where it is processed, who is involved.

scoco.ai answers that as follows: servers, database and backups in Germany (Hetzner, Falkenstein); speech recognition and the language model in the EU, at providers that are US companies or belong to a US group; speech output can run through a US provider that receives only the assistant's reply texts, no caller audio. Everyone involved is listed with task, registered office or processing region and transfer basis in the public sub-processor list, and the privacy notice names the service providers for demo calls with name and role. So anyone who applies the steps above to scoco.ai will find several US companies — named openly.

Frequently asked questions

Is a US wrapper automatically in breach of the GDPR?

No, not automatically. The GDPR permits transfers to the US under conditions — for example under the adequacy decision on the EU-US Data Privacy Framework or with standard contractual clauses (Article 45, Article 46(2)(c) GDPR), together with a data processing agreement with the provider (Article 28). Whether a specific arrangement is permissible is a case-by-case question. A problem arises at the latest when the parties involved are concealed: then you can neither give an informed authorisation for the sub-processors (Article 28(2) GDPR) nor inform your callers about transfers to third countries (Article 13(1)(f) GDPR).

What is the quickest way to identify the core platform?

The sub-processor list: if a single voice AI provider is named there and the call itself visibly runs through it, that is a strong pointer to the architecture. Then ask which stations run through it and whether the provider runs its own conversation logic or buys it in.

Am I allowed to simply ask for the sub-processor list?

Yes. Without it you cannot give an informed authorisation for the use of sub-processors (Article 28(2) GDPR), and the European Data Protection Board expects the processor to supply the identity of all sub-processors to you proactively and keep it up to date (Opinion 22/2024). Before signing, the question is simply part of your provider due diligence.

Does the provider's registered office count for anything?

It is one factor — a contracting party in Germany can make communication and enforcement easier. But what is meaningful for data protection is the processing chain behind it, not the address in the legal notice.

Further reading

From now on, someone
always picks up.

Call our demo business and hear for yourself what your reception sounds like.

We only use your address for your access. Privacy

4-week free trial. Or call the demo right now: +49 621 490799-22