scoco.ai
Law & data protection

ISO 27001 and AI phone assistants: what it proves — and doesn't

ISO 27001 certifies an information security management system — how security is organised, not whether a processing operation is lawful. The GDPR does not require a certificate; Article 42 makes data protection certification expressly voluntary. Five check questions say more than a seal: processing agreement, technical and organisational measures, sub-processor list, deletion policy, recording practice.

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

What ISO 27001 actually certifies

ISO/IEC 27001 (current edition from 2022) is a standard for information security management systems (ISMS). In an audit, a certification body checks whether an organisation runs its security systematically: analyses risks, assigns responsibilities, documents measures, handles incidents and improves the whole thing regularly. That has value. It shows that security there is organised as an audited process.

Two limitations come with it. First: only what the certificate names in its scope is certified. A certificate for the data centre says nothing about the application running inside it. Second: when a provider advertises "ISO 27001", it is worth looking at the certificate itself. It names the certificate holder, the certification body, the scope, the sites and the validity. Only then do you know whether the certified management system covers the service you are buying, or perhaps only the data centre it runs in.

What the certificate does not prove

An ISO 27001 certificate attests that a management system meets the requirements of the standard. It does not attest that a processing operation is lawful under the GDPR. The certificate does not answer whether a data processing agreement exists, which sub-processors are involved, whether data flows to third countries, how long transcripts are stored, or whether callers are properly informed. A provider can run a faultlessly audited management system and still keep call data longer than necessary, or leave its processor list vague.

In short: the seal measures how organised a provider is about security, not whether its processing is lawful. Treat the two as the same thing and you buy the wrong certainty.

The GDPR does not require a certificate

Article 32(1) GDPR requires controllers and processors to implement "appropriate technical and organisational measures" that ensure a level of security appropriate to the risk. The Regulation does not prescribe a certificate for this. What the controller must be able to demonstrate is that its processing complies with the Regulation (Article 24(1)). An approved certification mechanism under Article 42 may be used as an element in demonstrating that (Articles 24(3), 28(5) and 32(3)), nothing more. Article 42 itself makes clear that certification is voluntary (paragraph 3) and does not reduce responsibility (paragraph 4). ISO/IEC 27001 is not such a mechanism: it does not appear in the register the European Data Protection Board keeps under Article 42(8).

For you as a decision-maker that means: under the GDPR, a missing certificate is no ground for exclusion, and an existing one is no free pass. The supervisory authority can request the record of processing activities (Article 30(4)) and any information it needs for its tasks (Article 58(1)(a)), for example the contract with the processor and the description of the measures.

Five check questions that show more than a seal

When you are assessing a provider, with or without a certificate, these five questions get to the substance faster:

  1. Can you read the full data processing agreement before you sign, with every annex it refers to?
  2. Do the technical and organisational measures exist as a document of their own (encryption, access controls, backups, tenant separation)?
  3. Is there a sub-processor list naming each service provider's location, role and transfer mechanism?
  4. Is there a deletion policy with defined retention periods per data type?
  5. Are calls recorded as audio — yes or no?

A logo answers none of these questions. A provider that has done its homework can answer all five in writing.

Honestly: when a certificate really does help

There are situations in which ISO 27001 has real value. Where a client expressly requires the certificate, for instance in a public tender or in an enterprise's procurement rules, it is the formal entry ticket and can replace long security questionnaires there. And it shows that a provider has invested considerable effort in its security organisation; that is not an empty signal. If you need such a certificate from the provider itself: scoco.ai does not have one.

Where nobody requires the seal, something else decides: whether the processing agreement, the technical and organisational measures and the sub-processor list answer the questions of your IT service provider or data protection officer.

How scoco.ai answers the check questions

scoco.ai itself is not certified, neither to ISO 27001 nor under an Article 42 GDPR mechanism nor to any other standard. The servers are in Germany, at Hetzner Online GmbH in Falkenstein. Hetzner's information security management system for hosting services and data centres is certified to ISO/IEC 27001:2022, the Falkenstein data centre included (certificate holder: Hetzner Online GmbH; certification body: SOCOTEC Certification Deutschland GmbH; valid until 26 September 2028). That certificate covers Hetzner's hosting services and data centres, not the scoco.ai service.

Speech recognition and the language model run in the EU; speech output can run through a US provider that receives only the assistant's reply texts (no caller audio). The answers to the five questions:

  1. The data processing agreement is publicly available, and so is the sub-processor list (Annex 3); the technical and organisational measures (Annex 2) come on request, see 2.
  2. The technical and organisational measures are a versioned document of their own (Annex 2 to the agreement); we send it by e-mail on request.
  3. The sub-processor list is public, with each service provider's location, processing region and transfer mechanism.
  4. scoco deletes transcripts and call data after retention periods you choose yourself (data retention in the help centre).
  5. No call recordings are produced, only transcripts and summaries.

AI disclosure in the greeting is active by default and cannot be removed.

Frequently asked questions

Is an ISO 27001 certified provider automatically GDPR compliant?

No. The certificate confirms that a security management system meets the requirements of the standard, not that a processing operation is lawful. You have to check the processing agreement, the technical and organisational measures, the sub-processor list and the deletion policy independently of it.

Is there a "real" GDPR certification?

Yes. Article 42 GDPR provides for voluntary data protection certification, and the European Data Protection Board keeps a register of approved mechanisms (Article 42(8)). As of 15 November 2026 it lists, among others, the European Data Protection Seal Europrivacy and criteria approved by German supervisory authorities, such as AUDITOR for cloud services acting as processors, and EuroPriSe. Such a certification is issued for at most three years (Article 42(7)). scoco.ai has none.

What does "data centres ISO 27001 certified" mean when a provider says it?

That the data centre operator is certified, not necessarily the provider itself. Who holds the certificate and what it covers is stated in the certificate: holder, scope, sites, validity. For scoco.ai it is the certificate of Hetzner Online GmbH for its hosting services and data centres; scoco.ai itself is not certified.

Does my provider have to be certified for Article 32 GDPR?

No. Article 32 requires appropriate technical and organisational measures, not a certificate. An approved Article 42 mechanism may be used as an element in demonstrating compliance (Article 32(3)), but it is not a precondition. The measures are described, for example, in a technical and organisational measures document annexed to the processing agreement.

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