--- title: "AI Voice Assistants in Germany: GDPR, AI Act, and Rollout Checks (2026)" description: "AI voice assistants are usable in Germany if GDPR, call recording, AI Act transparency, and human handoff controls are built in." image: "https://compound.law/assets/images/og-image-en.webp" source: "https://compound.law/en-DE/compliance/ai-voice-assistants/" language: "en" --- ![AI voice assistants Germany compliance guide](https://compound.law/assets/images/compliance/compliance_1.webp) compliance # AI Voice Assistants in Germany: GDPR, AI Act, and Rollout Checks (2026) 3 April 2026 Short answer AI voice assistants can be deployed lawfully in Germany, but only if companies define the use case, give clear AI disclosure, choose a valid GDPR setup for call data, review vendor terms and transfers, and route sensitive cases to a human before the system shapes important outcomes. - Start with routing, FAQs, summaries, and agent assist before moving into complaints, refunds, or rights-impacting decisions. - Check legal basis, call recording notice, retention, DPA, subprocessors, hosting, and training settings before launch. - Add human handoff, works council review where employees are affected, and governance for sensitive conversations. **AI voice assistants can be used in Germany, but only with a structured compliance setup.** For most businesses, the workable position is yes: voice agents, call-routing assistants, transcript tools, and agent-assist systems can be deployed if the company gives clear AI disclosure, limits the data scope, chooses a defensible GDPR basis, controls recording and retention, and ensures that complaints, contested outcomes, and sensitive calls move to a human. The practical risk is usually not the label “voice AI” itself. The real legal questions are what the assistant does in the call flow, what personal data enters the system, whether calls are recorded or reused, and whether the tool starts shaping decisions that matter for customers or employees. Before rollout, legal, privacy, procurement, and operations teams should usually confirm: - what live call data, transcripts, metadata, and CRM fields enter the workflow, - whether the use case is only routing and assistance or also complaint handling and outcome shaping, - which GDPR legal basis and call notice cover the processing, - whether recording, retention, and training use are technically and contractually controlled, - whether the vendor offers a workable **DPA** under Article 28 GDPR, - and when a human must take over the interaction. ## Can companies use AI voice assistants in Germany lawfully? In many cases, yes. But the lawful answer depends on the **deployment model**, not the tool name. Common use cases include: 1. voice bots for first-line customer support, 2. AI call routing and intent detection, 3. call transcription and summary generation, 4. agent-assist prompts during live calls, 5. internal voice assistants for employees, 6. quality review of conversations at scale. Those use cases often sit inside a combined legal framework: - **Articles 5 and 6 GDPR** for purpose limitation, minimisation, and legal basis, - **Articles 13 and 14 GDPR** for transparency toward callers and customers, - **Article 28 GDPR** for processor terms and instructions, - **Chapter V GDPR** where third-country transfers are involved, - **Article 22 GDPR** if the system starts driving decisions with legal or similarly significant effects, - **Article 50 AI Act** for disclosure when a person interacts with AI and that is not obvious, - and, in employee-facing deployments, **section 87(1) no. 6 BetrVG** if technical systems can monitor behaviour or performance. If you are evaluating a concrete voice vendor, see our detailed [ElevenLabs DPA review](https://compound.law/en-DE/tools/elevenlabs/). It covers DPA availability, EU data residency, Zero Retention Mode, and how German buyers should assess customer calls, voice cloning, and employee recordings before rollout. The current timeline matters. The European Commission states that the AI Act entered into force on **August 1, 2024**, AI literacy obligations began applying on **February 2, 2025**, and the **Article 50 transparency rules apply from August 2, 2026**. Companies deploying voice agents should therefore build disclosure and governance now, not treat them as a later UI fix. If you are comparing adjacent customer-facing workflows, our pages on [AI customer service](https://compound.law/en-DE/compliance/ai-customer-service/), [AI chatbots](https://compound.law/en-DE/compliance/ai-chatbots/), and [ElevenLabs](https://compound.law/en-DE/tools/elevenlabs/) help frame the surrounding data-protection and operational questions. ## Voice agents, call routing, transcripts, and summaries: what changes legally? The risk profile changes with the **role the voice assistant plays in the call**. A tool that announces itself, routes a caller to the correct team, and creates a transcript for a human reviewer is usually easier to justify than a system that: - handles complaints end to end, - influences refunds or service restrictions, - analyses emotion or stress in the voice, - identifies people through voice biometrics, - or evaluates employees based on call behaviour. That difference matters under both GDPR and the AI Act. Limited-risk interaction tools may mainly raise transparency and privacy questions. Systems that move toward profiling, biometric use, or consequential decisions require a much deeper assessment. ### GDPR legal basis for live calls and voice data There is no single legal basis that covers every voice AI deployment. In practice, companies usually assess: - whether the workflow is necessary for a service process and can rely on **Article 6(1)(b) GDPR**, - whether parts of the workflow are supported by **Article 6(1)(f) GDPR** legitimate interests, - whether recording or analytics require a separate and clearer justification, - and whether the call may contain special-category data that raises the threshold further. Voice content, transcripts, caller identifiers, timestamps, and routing metadata are personal data. If the system uses voice for authentication or identification, biometric rules may also become relevant. The legal analysis should therefore cover the full pipeline, not only the speech-to-text model. ### Call recording, retention, and model training One of the biggest compliance mistakes in voice AI projects is treating **recording**, **transcription**, **summarisation**, and **training reuse** as if they were one question. They are not. Companies should separate at least four issues: 1. whether the call is recorded at all, 2. whether it is transcribed or analysed, 3. how long raw audio and transcripts are stored, 4. whether the vendor may use the material to train or improve models. The call notice, privacy information, retention logic, and vendor terms should line up with those distinctions. A team may have a defensible setup for live routing and summaries but not for open-ended reuse of customer calls for product improvement. Training use should be treated as a **current contractual and technical setting to verify**, not as a marketing promise to assume. If your voice workflow overlaps with broader support automation, the legal review should align with the controls described in our [AI customer service guide](https://compound.law/en-DE/compliance/ai-customer-service/). ## Human handoff and AI Act transparency for voice assistants For voice agents in Germany, the safest design principle is simple: **callers should know when they are speaking with AI, and they should be able to reach a person when the conversation turns sensitive or outcome-relevant**. That means disclosure should usually be clear and early, for example at the first point of interaction rather than buried in the privacy policy or post-call email. The disclosure design should match the call flow, including transfers between AI and human agents. Human handoff is equally important. Companies should define escalation triggers in advance, especially for: - complaints and contested outcomes, - cancellations, refunds, and restrictions, - callers mentioning health, children, or other sensitive topics, - unclear answers or hallucinations, - requests for human review, - and any step where the system begins shaping a significant customer outcome. This is where AI Act and GDPR governance meet. Even if the use case is not formally high-risk under the AI Act, a weak handoff model can create practical fairness, accountability, and customer-trust problems very quickly. ## Vendor due diligence for voice AI providers Many voice assistant projects fail legally at procurement, not at deployment. Before launch, teams should review the vendor on at least these points: - whether a usable **DPA** is available, - where audio, transcripts, and logs are hosted, - which subprocessors are involved, - what transfer mechanism is used outside the EEA, - whether model training or service-improvement reuse is enabled, - how deletion and retention can be configured, - what security controls apply to recordings and transcripts, - and whether the workflow supports human takeover and auditability. This matters not only for specialist voice vendors but also for broader platforms that bring voice into service operations. Related deployment questions often appear in tools such as [Intercom AI](https://compound.law/en-DE/tools/intercom/), [Zendesk AI](https://compound.law/en-DE/tools/zendesk/), or [HubSpot AI](https://compound.law/en-DE/tools/hubspot/), where call data may interact with ticket history and CRM records. ### Shortlist criteria for voice-API and communication-API vendors Many procurement projects start with the umbrella term “communication APIs.” Depending on the stack, that can mean voice APIs for inbound and outbound calls, CPaaS platforms for phone numbers, routing, and carrier connectivity, speech layers for transcription and summaries, or complete voice-agent platforms. For the procurement file, the category label matters less than the actual stack: break it into its layers and review each layer against the same criteria. No vendor is automatically GDPR compliant because of EU hosting or a public DPA alone. Put a provider on the shortlist only once these five criteria are documented in writing: | Criterion | What legal should demand in writing | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **DPA/AVV availability** | An Article 28 GDPR data-processing agreement covering the exact product purchased — including product scope, subprocessors, audit support, and deletion assistance | | **Data residency & transfer model** | Storage and processing locations for audio, transcripts, metadata, and support logs; the transfer mechanism (e.g., SCCs) for any remaining third-country access | | **Retention & deletion** | Separate periods for raw audio, transcripts, metadata, analytics, and backups; deletion at termination; zero-retention and no-training promises only where they cover the concrete product path | | **Sub-processors** | A complete, current list across telephony, speech, model, analytics, and support partners, with change notification | | **German support & escalation** | A named contact — German-language support where possible — with response times for deletion requests, security incidents, and regulator questions | Data residency is not the same as data sovereignty: residency answers where data is stored or processed, while sovereignty also asks who can access it — remote support and parent-company access can create third-country exposure even with an EU data center. A vendor that cannot answer these questions cleanly is usually not ready for a fast German procurement cycle. The shortlist never replaces individual review: before signature, the vendor’s DPA text, product controls, and sub-processor chain must be confirmed in vendor-specific review. The legal framework for that review is set out in our [GDPR AI procurement guide](https://compound.law/en-DE/compliance/gdpr-ai-procurement/). ## When voice AI creates employment-law or works council risk Voice assistants are not only customer-service tools. They are often also **employee-facing systems**. That is where German employment law enters the picture. If a voice AI rollout affects how employees are monitored, scored, instructed, scheduled, or evaluated, co-determination under **section 87 BetrVG** can become relevant. The practical warning signs are: - QA systems that rank agents, - dashboards that expose call-by-call performance, - automated coaching or script compliance scores, - tools that listen to live calls and influence supervisor review, - or internal voice assistants that log extensive employee behaviour. In those cases, the works council question should not be left until after procurement. It needs to be built into the rollout plan early, together with privacy and governance review. ## Practical rollout checklist for AI voice assistants in Germany Before scaling an AI voice assistant, companies should usually work through this checklist: 1. Define the exact use cases and exclude rights-impacting or highly sensitive scenarios from the first rollout. 2. Map what audio, transcript, metadata, and CRM data enter the system. 3. Confirm the GDPR legal basis for live processing, recording, analytics, and retention separately. 4. Design a clear AI disclosure for the first caller interaction and any later AI handoff points. 5. Review the DPA, subprocessors, hosting, transfers, deletion, and training settings. 6. Limit permissions and data exposure to what the workflow actually needs. 7. Create mandatory human handoff rules for complaints, disputes, sensitive topics, and unclear outputs. 8. Assess whether employee monitoring or performance visibility triggers works council involvement. 9. Test quality, hallucination risk, and unfair or misleading call outcomes before broad launch. 10. Document the deployment in the company’s AI governance, privacy, and vendor-management process. ## Compound Law’s refresh brief for implementation For search intent, the page should be positioned around **AI voice assistants in Germany**, **voice agents**, **call recordings**, **GDPR**, **human handoff**, and **vendor due diligence**, not only around AI Act disclosure. Recommended on-page structure: - H1: AI Voice Assistants in Germany: GDPR, AI Act, and Rollout Checks - H2: Can companies use AI voice assistants in Germany lawfully? - H2: Voice agents, call routing, transcripts, and summaries: what changes legally? - H2: Human handoff and AI Act transparency for voice assistants - H2: Vendor due diligence for voice AI providers - H2: When voice AI creates employment-law or works council risk - H2: Practical rollout checklist for AI voice assistants in Germany ## How Compound Law helps Compound Law advises businesses in Germany and the DACH region on AI deployment across privacy, commercial contracts, employment, and regulatory compliance. Typical support for voice AI projects includes: - GDPR and call-data assessments, - DPA and vendor-term review, - retention and training-use governance, - AI Act disclosure design, - works council strategy for employee-facing systems, - and rollout guidance for legal, privacy, procurement, and operations teams. Specific deployments still require individual legal advice. A guide like this helps structure the review, but it cannot replace a fact-specific assessment of the actual tool, contract, data flows, and use case. ## FAQ ### Can we use an AI voice assistant for customer calls in Germany? Often yes, if the assistant is transparent, the use case is limited, the GDPR setup is defensible, and sensitive matters move to a human before the system shapes important outcomes. ### Do we need to tell callers that they are speaking with AI? In many cases, yes. Under Article 50 AI Act, people interacting directly with AI must be informed when that is not obvious, and those transparency rules apply from August 2, 2026. ### Is call recording for AI summaries automatically allowed? No. Recording, transcription, summaries, retention, and model training should be assessed separately. The lawful setup depends on the exact call flow, notice, legal basis, and vendor configuration. ### When does a voice assistant become a works council issue? Usually when the system affects employee monitoring, performance evaluation, quality scoring, or other workflows that make behaviour visible through technical means. ### What is the safest first rollout for voice AI? Usually a narrow deployment focused on routing, FAQs, summaries, and agent assist, with clear disclosure and mandatory human handoff for complaints, sensitive issues, and contested outcomes. ## Related Compliance Guides [![EU AI Act training obligation and Article 4 AI literacy in Germany](https://compound.law/assets/images/compliance/compliance_2.webp)](https://compound.law/en-DE/compliance/ai-act-schulungspflicht/) [compliance](https://compound.law/en-DE/compliance/ai-act-schulungspflicht/) ### [EU AI Act Training Obligation: What Article 4 Requires](https://compound.law/en-DE/compliance/ai-act-schulungspflicht/) [EU AI Act training obligation under Article 4: who it covers in Germany, what AI literacy measures to implement, and how to document compliance.](https://compound.law/en-DE/compliance/ai-act-schulungspflicht/) [![AI legal counsel in Germany for company AI procurement](https://compound.law/assets/images/compliance/compliance_3.webp)](https://compound.law/en-DE/compliance/ai-legal-counsel-germany/) [Guides](https://compound.law/en-DE/compliance/ai-legal-counsel-germany/) ### [AI Legal Counsel in Germany for Companies](https://compound.law/en-DE/compliance/ai-legal-counsel-germany/) [AI legal counsel in Germany helps companies handle EU AI Act, GDPR, DPA, procurement, and rollout risk before signing or launching AI tools.](https://compound.law/en-DE/compliance/ai-legal-counsel-germany/) [![EU AI Act procurement before 2027 for German buyers](https://compound.law/assets/images/compliance/compliance_3.webp)](https://compound.law/en-DE/compliance/eu-ai-act-procurement-before-2027/) [compliance](https://compound.law/en-DE/compliance/eu-ai-act-procurement-before-2027/) ### [EU AI Act Procurement Before 2027 in Germany](https://compound.law/en-DE/compliance/eu-ai-act-procurement-before-2027/) [EU AI Act procurement before 2027 matters now for German buyers because contracts, evidence flows, and deployer support should be fixed before rollout.](https://compound.law/en-DE/compliance/eu-ai-act-procurement-before-2027/) ## Frequently asked questions Often yes, if the deployment is transparent, limited to defensible use cases, and supported by a valid GDPR, vendor, and governance setup. Yes, where people interact directly with an AI system and that fact is not obvious. Article 50 AI Act transparency rules start applying on August 2, 2026. That requires separate analysis. Companies should review legal basis, call notices, retention, vendor terms, and whether training use is disabled or contractually restricted. Usually when the system affects employee performance visibility, call monitoring, scheduling, or quality scoring. That can trigger works council co-determination under section 87 BetrVG. Review the DPA, subprocessors, transfer mechanics, deletion, security, training rights, voice data reuse, and whether the tool can be configured for human escalation. ## Structured data ```json [ { "@context": "https://schema.org", "@type": [ "Organization", "LegalService" ], "@id": "https://compound.law/#organization", "name": "Compound Law", "alternateName": "Compound Law — AI Law Firm", "url": "https://compound.law/", "logo": { "@type": "ImageObject", "url": "https://compound.law/press/logos/PNG/Compound_Law_Icon.png", "width": 1024, "height": 1024 }, "image": "https://compound.law/assets/images/og-image.webp", "description": "The AI-native law firm in Berlin for start-ups, mid-sized companies and corporates: commercial and contract law, data protection, the EU AI Act, trademarks, corporate law, and restructuring and insolvency. A lawyer reviews every result, billed at a flat fee.", "foundingDate": "2026", "founder": [ { "@type": "Person", "name": "Marko Bradic", "jobTitle": "CEO", "url": "https://compound.law/en-DE/tech-team/marko-bradic/", "sameAs": [ "https://www.linkedin.com/in/markobradic/" ], "knowsAbout": [ "Product strategy and development", "Scaling technology companies", "FinTech and financial services", "AI-powered product innovation", "Business operations and growth", "Digital transformation" ] }, { "@type": "Person", "name": "Mohit Tilwani", "jobTitle": "CTO", "url": "https://compound.law/en-DE/tech-team/mohit-tilwani/", "sameAs": [ "https://www.linkedin.com/in/mohit-tilwani/" ], "knowsAbout": [ "Engineering leadership and architecture", "Scaling high-traffic systems", "AI and machine learning infrastructure", "FinTech platform development", "Cloud infrastructure and DevOps", "Product engineering" ] }, { "@type": "Person", "name": "Julian Jantze", "jobTitle": "Rechtsanwalt", "url": "https://compound.law/en-DE/lawyers/julian-jantze/", "sameAs": [ "https://www.linkedin.com/in/julian-jantze-957b95158/" ], "knowsAbout": [ "Corporate law and corporate governance for technology companies", "Employment law and HR compliance", "EU AI Act compliance and AI governance", "Employee participation models (VSOP/ESOP)", "Regulatory compliance for tech companies", "Legal operations and Legal Tech implementation" ] } ], "employee": [ { "@type": "Person", "name": "Marko Bradic", "jobTitle": "CEO", "url": "https://compound.law/en-DE/tech-team/marko-bradic/", "sameAs": [ "https://www.linkedin.com/in/markobradic/" ], "knowsAbout": [ "Product strategy and development", "Scaling technology companies", "FinTech and financial services", "AI-powered product innovation", "Business operations and growth", "Digital transformation" ] }, { "@type": "Person", "name": "Mohit Tilwani", "jobTitle": "CTO", "url": "https://compound.law/en-DE/tech-team/mohit-tilwani/", "sameAs": [ "https://www.linkedin.com/in/mohit-tilwani/" ], "knowsAbout": [ "Engineering leadership and architecture", "Scaling high-traffic systems", "AI and machine learning infrastructure", "FinTech platform development", "Cloud infrastructure and DevOps", "Product engineering" ] }, { "@type": "Person", "name": "Julian Jantze", "jobTitle": "Rechtsanwalt", "url": "https://compound.law/en-DE/lawyers/julian-jantze/", "sameAs": [ "https://www.linkedin.com/in/julian-jantze-957b95158/" ], "knowsAbout": [ "Corporate law and corporate governance for technology companies", "Employment law and HR compliance", "EU AI Act compliance and AI governance", "Employee participation models (VSOP/ESOP)", "Regulatory compliance for tech companies", "Legal operations and Legal Tech implementation" ] }, { "@type": "Person", "name": "Marc Schuba", "jobTitle": "Founding Partner, Rechtsanwalt (German attorney)", "url": "https://compound.law/en-DE/lawyers/marc-schuba/", "sameAs": [ "https://www.linkedin.com/in/marcschuba/" ], "knowsAbout": [ "IP and IT law", "SaaS and IT contracts, IT outsourcing", "Software and open-source licensing", "Data protection law (GDPR)", "AI law and the EU AI Act" ] }, { "@type": "Person", "name": "Dr. Markus Dreißigacker", "jobTitle": "Rechtsanwalt", "url": "https://compound.law/en-DE/lawyers/markus-dreissigacker/", "sameAs": [ "https://www.linkedin.com/in/markusdreissigacker" ], "knowsAbout": [ "M&A (Due diligence, post-merger integration, IPO readiness)", "Corporate Law (Governance, board work, restructuring)", "Commercial Law (Customer contracts, supplier agreements, NDAs)", "IP (Trademark management, IP transfer agreements)", "Compliance & ESG (Global compliance programs, human rights, sustainability)", "Data Protection (GDPR strategy, DPO experience, privacy programs)" ] }, { "@type": "Person", "name": "Philipp Brandt", "jobTitle": "Partner, Rechtsanwalt (German attorney), Specialist Lawyer for Intellectual Property Law", "url": "https://compound.law/en-DE/lawyers/philipp-brandt/", "sameAs": [ "https://www.linkedin.com/in/philipp-brandt-81b446a/" ], "knowsAbout": [ "Restructuring and insolvency law (crisis advice for management, protective shield and insolvency plan proceedings, insolvency administration)", "Intellectual property (trademarks, unfair competition, copyright, trade secrets, licence agreements)", "Data protection law (data breaches, regulatory fine proceedings, access and damages claims)", "Distribution and commercial law (distribution agreements, acquisition and sale of industrial plants)" ] } ], "address": { "@type": "PostalAddress", "addressLocality": "Berlin", "addressCountry": "DE" }, "areaServed": [ "Germany", "Austria", "Switzerland", "European Union", "United Kingdom", "United States", "Singapore" ], "availableLanguage": [ "de", "en" ], "serviceType": [ "AI law firm", "AI-native legal services", "legal counsel for start-ups and growth companies", "legal counsel for mid-sized companies and corporates", "Commercial Law", "Corporate Law", "Employment Law", "Regulatory & Compliance", "Intellectual Property", "Insolvency & Restructuring" ], "hasOfferCatalog": { "@type": "OfferCatalog", "name": "Compound Law services", "itemListElement": [ { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Commercial Contracts", "description": "Battle-tested contracts for your sales process", "serviceType": [ "enterprise contracts", "MSA", "DPA", "sales contracts" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "International Employment", "description": "Compliant hiring across borders", "serviceType": [ "international employment", "hiring abroad", "employment contracts" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "VSOP/ESOP Setup", "description": "Employee participation that actually works", "serviceType": [ "VSOP", "ESOP", "employee stock options", "equity incentives" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Funding Round Support", "description": "Clean legal for your next raise", "serviceType": [ "funding round", "term sheet", "SHA", "due diligence", "cap table" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Corporate Housekeeping", "description": "Get your legal house in order", "serviceType": [ "corporate governance", "board resolutions", "shareholder register" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Data Protection & Privacy", "description": "GDPR compliance that doesn't slow you down", "serviceType": [ "GDPR", "data protection", "privacy", "DPA", "cookies", "data breach response", "GDPR fines", "Art. 82 GDPR" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "AI Act Compliance", "description": "Navigate EU AI regulation", "serviceType": [ "AI Act", "AI compliance", "AI governance", "EU AI regulation" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "IP & Competition", "description": "Protect and enforce what you've built", "serviceType": [ "IP protection", "intellectual property", "trademarks", "trademark enforcement", "warning letters", "preliminary injunctions", "unfair competition", "software licensing", "open source compliance" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Fractional General Counsel", "description": "In-house legal without the full-time cost", "serviceType": [ "fractional GC", "fractional general counsel", "outsourced legal", "legal retainer" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "FinTech Compliance", "description": "Navigate financial regulation", "serviceType": [ "fintech compliance", "BaFin", "banking regulation", "AML", "KYC" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Legal Retainer", "description": "Predictable legal support when you need it", "serviceType": [ "legal retainer", "legal subscription", "ongoing legal support" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "M&A Preparation", "description": "Get ready for acquisition interest", "serviceType": [ "M&A preparation", "acquisition", "due diligence", "exit" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } }, { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Restructuring & Insolvency", "description": "From the first liquidity check to the restructuring itself", "serviceType": [ "restructuring", "insolvency", "StaRUG", "self-administration", "insolvency plan", "director liability" ], "areaServed": [ "Germany", "European Union", "United Kingdom", "United States", "Singapore" ] } } ] }, "contactPoint": { "@type": "ContactPoint", "contactType": "sales", "email": "contact@compound.law", "availableLanguage": [ "English", "German" ], "areaServed": [ "DE", "AT", "CH", "EU", "GB", "US", "SG" ] }, "email": "contact@compound.law", "sameAs": [ "https://www.linkedin.com/company/compoundlawfirm", "https://x.com/CompoundLawFirm" ], "knowsAbout": [ "Commercial Contracts", "enterprise contracts", "MSA", "DPA", "sales contracts", "International Employment", "international employment", "hiring abroad", "employment contracts", "VSOP/ESOP Setup", "VSOP", "ESOP", "employee stock options", "equity incentives", "Funding Round Support", "funding round", "term sheet", "SHA", "due diligence", "cap table", "Corporate Housekeeping", "corporate governance", "board resolutions", "shareholder register", "Data Protection & Privacy", "GDPR", "data protection", "privacy", "cookies", "data breach response", "GDPR fines", "Art. 82 GDPR", "AI Act Compliance", "AI Act", "AI compliance", "AI governance", "EU AI regulation", "IP & Competition", "IP protection", "intellectual property", "trademarks", "trademark enforcement", "warning letters", "preliminary injunctions", "unfair competition", "software licensing", "open source compliance", "Fractional General Counsel", "fractional GC", "fractional general counsel", "outsourced legal", "legal retainer", "FinTech Compliance", "fintech compliance", "BaFin", "banking regulation", "AML", "KYC", "Legal Retainer", "legal subscription", "ongoing legal support", "M&A Preparation", "M&A preparation", "acquisition", "exit", "Restructuring & Insolvency", "restructuring", "insolvency", "StaRUG", "self-administration", "insolvency plan", "director liability" ] }, { "@context": "https://schema.org", "@type": "Article", "headline": "AI Voice Assistants in Germany: GDPR, AI Act, and Rollout Checks (2026)", "description": "AI voice assistants are usable in Germany if GDPR, call recording, AI Act transparency, and human handoff controls are built in.", "image": "https://compound.law/assets/images/compliance/compliance_1.webp", "datePublished": "2026-04-03T00:00:00.000Z", "dateModified": "2026-04-03T00:00:00.000Z", "author": { "@type": "Person", "name": "Julian Jantze", "image": "https://compound.law/assets/images/team/julianjantze.webp" }, "publisher": { "@type": "Organization", "@id": "https://compound.law/#organization", "name": "Compound Law" }, "mainEntityOfPage": { "@type": "WebPage", "@id": "https://compound.law/en-DE/compliance/ai-voice-assistants/" } }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://compound.law/en-DE/" }, { "@type": "ListItem", "position": 2, "name": "Compliance Guides", "item": "https://compound.law/en-DE/compliance/" }, { "@type": "ListItem", "position": 3, "name": "AI Voice Assistants in Germany: GDPR, AI Act, and Rollout Checks", "item": "https://compound.law/en-DE/compliance/ai-voice-assistants/" } ] }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Can German companies use AI voice assistants lawfully?", "acceptedAnswer": { "@type": "Answer", "text": "Often yes, if the deployment is transparent, limited to defensible use cases, and supported by a valid GDPR, vendor, and governance setup." } }, { "@type": "Question", "name": "Do AI voice assistants need disclosure under the AI Act?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, where people interact directly with an AI system and that fact is not obvious. Article 50 AI Act transparency rules start applying on August 2, 2026." } }, { "@type": "Question", "name": "Can customer calls be recorded for AI summaries or training?", "acceptedAnswer": { "@type": "Answer", "text": "That requires separate analysis. Companies should review legal basis, call notices, retention, vendor terms, and whether training use is disabled or contractually restricted." } }, { "@type": "Question", "name": "When does a voice assistant create employment-law risk in Germany?", "acceptedAnswer": { "@type": "Answer", "text": "Usually when the system affects employee performance visibility, call monitoring, scheduling, or quality scoring. That can trigger works council co-determination under section 87 BetrVG." } }, { "@type": "Question", "name": "What should be checked in the vendor contract?", "acceptedAnswer": { "@type": "Answer", "text": "Review the DPA, subprocessors, transfer mechanics, deletion, security, training rights, voice data reuse, and whether the tool can be configured for human escalation." } } ] } ] ```