Google Gemini and the EU AI Act: full analysis
Google's GPAI obligations (already in effect)
Google, as the provider of Gemini as a General Purpose AI model, has had EU AI Act compliance obligations since August 2025. This includes publishing model documentation, implementing copyright compliance policies, and conducting systemic risk assessments for Gemini Ultra-class models. Google has committed to the GPAI Code of Practice. These are Google's obligations as a provider — they do not substitute for your deployer obligations.
Gemini in Google Workspace: internal use
Gemini features built into Google Docs (Help me write), Gmail (Smart Compose, Summarise), and Meet (meeting summaries) are used by employees for internal productivity. This is minimal EU AI Act risk: employees know they are using AI, there is no deceptive interaction, and no consequential decisions about individuals' rights are made. Your obligations are limited to AI literacy training (Article 4) and GDPR compliance for any personal data processed by Gemini within Workspace documents.
Gemini as a customer-facing chatbot
Businesses can deploy Gemini via the API or through Google's Agentspace and Vertex AI products to build customer-facing chatbots. When you do this, you become the deployer of an AI system that directly interacts with natural persons — Article 50(1) applies. You must add the disclosure. Google supplying the model does not remove your obligation to disclose to your own users.
Gemini-generated content: Article 50(2)
Using Gemini to generate content published to customers — help documentation, product descriptions, marketing emails, blog posts — may trigger Article 50(2) labelling when content is published at scale without meaningful human review. The same threshold analysis as other generative AI tools applies: human-reviewed and edited content does not require a label; auto-generated content published without human review does.