Model catalogue · Google
Google Text-Embedding
The established previous generation of Google embeddings turns text into vectors and includes an expressly multilingual tier. It is the right choice where an existing search index is not to be recomputed or where foreign-language documents are decisive. Via Google Vertex AI the chain is closed: the platform operator's signed confidentiality agreement under section 203 of the German Criminal Code is service-bound and covers the embeddings as well as the language models, callable through the EU endpoint and through individual EU regions. Two points belong in the setup: an embedding run sends the entire indexed corpus through the service, and the London processing location listed for two tiers lies outside the EU endpoint.
The confidentiality agreement under section 203 of the German Criminal Code is signed. We set the route up without storage at the provider (zero retention) once the provider has committed to it - at Microsoft through the exception from abuse monitoring, which usually takes months. Until then, storage and review by the provider are not ruled out.
What it is good for
- Established embedding line with a multilingual tier for foreign-language documents
- Callable through the EU endpoint and through individual EU regions, processing committed to the EU
- Covered by the same service-bound section 203 agreement as the platform's language models
Where it stops
- London is listed as the processing location for two tiers; the United Kingdom is excluded from the EU endpoint - this call path has to be blocked
- An embedding run sends the entire indexed corpus through the service - the scope and redaction of the index have to be settled beforehand
- Previous generation: for new indexes the current embedding tier is usually the better choice
- CLOUD Act exposure remains - the third-country module is mandatory
Status through us
The same model, procured differently, is a different legal position. The status above refers to procurement through us; processing takes place in a third country.
Which route carries it, with which instrument and under which condition, we set out in full to the firm before it commissions us - section 203(4) requires that the chain can be checked, not that it is published. The full matrix, with the sources behind every route, can be requested in the German catalogue after confirming your e-mail address, and we go through it in the conversation.
Is Google Text-Embedding the right fit?
We go through your tasks and the route that carries them - and say plainly where it does not.
Arrange a conversation