# Google Gemini API

## Kurzbeschreibung
**Google **offers a family of models with the Gemini API for text generation, reasoning, coding, agent workflows, tool use, multimodal prompts, and document-centric processing. 


For current API LLMs, Gemini 3.1 Pro Preview, Gemini 3 Flash Preview, Gemini 3.1 Flash-Lite Preview, Gemini 2.5 Pro, Gemini 2.5 Flash, and Gemini 2.5 Flash-Lite are particularly relevant. Older Gemini 2.0 Flash variants are still available, but are already marked as deprecated.

## Claim
LLM “AI for every developer”

## Geeignet für
- API Integration
- Automation / Workflows
- Data Analysis
- Data Extraction / Document Analysis
- Customer Service & Chatbots
- Programming / Software Development
- Research
- Texts / Content
- Translations
- Knowledge Management / Internal Search

## Kernfunktionen
- Image Generation
- Embeddings
- Function Calling
- AI Agents
- LLM API
- Multimodal AI
- Programming
- Reasoning Model
- Language Model
- Text Generation

## Preismodell
- **free:** Free or unpaid use with limits; content may be used for product improvement and should not contain sensitive or confidential data.
- **other:** **Gemini API Paid Tier** For production applications with higher limits, context caching, Batch API, access to advanced models, and without using content for product improvement.


**Batch / Context Caching / Priority / Flex** Additional billing and operational options for controlling cost, latency, and throughput.


**Vertex AI / Google Cloud** Enterprise-oriented operation with Cloud DPA, IAM, regional endpoints, data residency, monitoring, and zero-data-retention configurations.


**Grounding / Tuning / Embeddings / Live API** Advanced features for search, context enrichment, model customization, vector search, real-time audio, and multimodal applications.

## DSGVO und Datenschutz
**Gesamteinschätzung:** Conditional

**On-prem / local hosting: indirect / not available**

The website does not specify any on-premises or self-hosting options for the Gemini API itself. The API is described as a hosted service.

**Private Cloud / Data Center: Partially**

The website refers to use via cloud projects and to “Google Cloud hosted solutions,” but does not specify a dedicated private cloud, an isolated EU data center, or an explicitly segregated customer environment for the Gemini API on ai.google.dev.

**EU SaaS / Managed: Partially**

Google operates a SaaS/API service. However, the website does not specify an explicit EU data residency or an EU/EEA data center for the Gemini API; rather, according to the additional terms, certain data may be stored in any country where Google or its agents operate facilities.

**Hybrid: Indirect / Not Available**

An explicit hybrid operating model for the Gemini API is not described on the website. The documentation only shows the hosted API; local or internal partial processing for the same solution is not specified there.

**T&C / DPA: Covered**

For “Paid Services,” the Additional Terms explicitly state that prompts and responses are processed in accordance with the “Data Processing Addendum for Products Where Google is a Data Processor.”

**No training: partially**

For “Paid Services,” the website explicitly states that prompts and responses are not used to improve the products. At the same time, they are logged for a limited period for security and compliance purposes; for “Unpaid Services,” content is generally used for improvement, though EEA users are referred to the “Paid Services” rule. Additionally, more extensive ZDR controls exist only under certain conditions.

**Open Source / Transparency: Partially**

To promote greater transparency and user autonomy, the website refers to open Gemma models and notes that Gemma can also run on-device. However, for the Gemini API itself, neither open core components nor the option to self-host the service are specified.

**Data Processing**

The website describes the Gemini API as a service operated by Google. For “Paid Services,” according to the additional terms, prompts and responses are not used for training or product improvement, but are logged for a limited time to detect and prevent violations, as well as for required legal or regulatory disclosures. According to the website, this data may be stored transiently or in cache in any country where Google or its agents operate facilities. The ZDR documentation describes additional restrictions and configurations: certain stateful or storage-intensive functions must be disabled or avoided, and for certain grounding functions, the storage mentioned there cannot be disabled.

**Conclusion**

From an EU/EEA perspective, the Gemini API is not documented on the provider’s website as a service that is clearly EU-resident. A viable data protection pathway is apparent if the service is used as a “Paid Service,” the DPA applies, and storage functions are configured restrictively. However, because no explicit EU data residency is specified and, according to the website, log data can be temporarily stored worldwide, the service’s overall compliance with the GDPR is only *partially* substantiated.

**Sources**

- [https://ai.google.dev/gemini-api/terms](https://ai.google.dev/gemini-api/terms)
- [https://ai.google.dev/gemini-api/docs/zdr?hl=es-419](https://ai.google.dev/gemini-api/docs/zdr?hl=es-419)
- [https://ai.google.dev/gemini-api/docs/logs-datasets](https://ai.google.dev/gemini-api/docs/logs-datasets)
- [https://ai.google.dev/gemma/docs](https://ai.google.dev/gemma/docs)
- [https://ai.google.dev/gdc?hl=en](https://ai.google.dev/gdc?hl=en)

For the EU/EEA region, a more privacy-friendly use of the Gemini API based on the provider’s documentation appears to be possible only under certain conditions. On the positive side, according to the additional terms, a DPA applies to “Paid Services,” and prompts and responses are not used for product improvement. On the negative side, Google nevertheless logs prompts and responses for Paid Services for a limited time for security and compliance purposes and may store this data temporarily or in cache “in any country” where Google or its agents operate facilities. The website does not specify an explicit EU data residency or an EU/EEA server location for the Gemini API.

**Positive**

The website lists three key points for “Paid Services”: processing in accordance with a DPA, no training on prompts or responses for product improvement, and specific notes for EEA users. Additionally, the “Zero Data Retention” page explains that, for certain projects and upon approval, user-identifying content and metadata can be removed before logging, and that individual storage options can be disabled for stateful features.

**Negative**

The website does not specify a guaranteed EU data residency for the Gemini API or a specific EU/EEA data center location. Rather, the additional terms state that log data for Paid Services may be stored transiently or in cache in any country where Google or its agents operate facilities. Furthermore, data-minimizing configurations such as “Zero Data Retention” and the disabling of certain storage functions require additional prerequisites; according to the website, it is not possible to disable the storage described there for specific functions such as “Grounding with Google Search” or “Grounding with Google Maps.”

**Server Location**

Not specifically listed on the website as an EU/EEA location. For paid services, it states that log data may be stored temporarily or in cache in any country where Google or its agents operate facilities.

## Hosting und Daten
- **On-Prem / lokales Hosting:** unknown
- **Private Cloud / Rechenzentrum:** teilweise / indirekt
- **EU SaaS / Managed:** teilweise / indirekt
- **Hybrid:** unknown
- **AVV / DPA:** abgedeckt
- **Kein Training auf Kundendaten:** teilweise / indirekt
- **Open-Source / Transparenz-Pfad:** teilweise / indirekt

## Standort
**Land:** USA

**Taxonomie:** USA

Global parent company: Google LLC, 1600 Amphitheatre Parkway, Mountain View, California 94043, United States.
For EMEA Gemini API Paid Services: Google Cloud EMEA Limited, 70 Sir John Rogerson’s Quay, Dublin 2, Ireland.

## Vorteile
- Very broad range from high-end reasoning to very low-cost high-volume processing.
- Strong combination of multimodality, coding, agents, grounding, tooling, and long context windows.
- Clear production pricing logic with Standard, Batch, Flex, and in some cases Priority.
- For Paid Services, prompts/responses are not used for product improvement according to the Terms.
- For enterprise environments via Vertex AI, there are stronger security/compliance options and regional processing models.

## Nachteile
- The portfolio is currently somewhat confusing because stable 2.5 models, 3.x previews, and deprecated 2.0 models coexist in parallel.
- For the direct Gemini API, data localization is documented less clearly than for Vertex AI; according to the Terms, for Paid Services logs may be stored transiently or cached in countries where Google or its agents operate facilities.
- The cheaper models are strong for volume and standard tasks, but not ideal for the most difficult analysis and precision use cases.
- Preview models may still change before GA and have more restrictive limits.

## Quellen
- Offizielle Website: https://ai.google.dev/gemini-api/docs/pricing?hl=de

## Letzter Datenstand
2026-04-17

## Originalseite
https://kifox.ai/en/ki-tools/google-gemini-api-en/