Skip to main content

Data, security, compliance

Where the models run​

  • Self-hosted models (openhippo/… and the hippo-… aliases such as hippo-coding) run on our own hardware in the LEW Green Data Center in Augsburg, Germany.
  • Partner models run at the respective partner in the EU. Partner and location are listed per model in the model list.

The LEW Green Data Center is certified to ISO/IEC 27001 and DIN EN 50600 (TÜV SÜD); its power comes, on balance, from hydro and photovoltaics. The certificates belong to the data centre, not to Open Hippo.

Vision aliases​

  • hippo-chat-vision is another name for openhippo/Qwen3.8-27B (like hippo-coding and hippo-chat). The model understands images itself; there is no separate describe step. It runs in Augsburg.
  • There are also aliases ending in -vision for models without image understanding of their own. They are not in the model list. There a vision model first describes the image, then the actual model answers; both steps run at the same provider, and the describe step is billed in addition.

Training​

  • Self-hosted models: customer data is not used for training.
  • Partner models: the respective partner's terms apply, see sub-processors.

Retention​

  • We do not store prompts or responses.
  • Metadata (e.g. model, token counts, cost, key, timestamp) is kept for as long as legally required to evidence the service provided and for billing.

The DPA and the terms and conditions are binding. Under the terms (§ 4 (3)), data transmitted by the customer is not stored separately and retained.

Abuse review​

The terms (§ 3 (8)) say, verbatim:

The Provider reserves the right to review prompts and generated output using abuse prevention or content filtering methods, and to block processing where there is reasonable suspicion of misuse.

The provider is Open Hippo. The terms do not regulate further details.

Questions: support@openhippo.io.

§ 203 StGB​

For professional secrecy holders such as law firms, tax advisers and medical practices (§ 203 of the German Criminal Code):

  • Every self-hosted model is suitable for § 203 StGB.
  • Partner models are not intended for it.
  • A confidentiality undertaking under § 203 StGB is available on request.
Before you send client or patient data

Request the confidentiality undertaking and clarify open questions with us: support@openhippo.io or book a call.

To make sure a team only uses suitable models, restrict the model approvals to self-hosted models.

Compliance flags​

The flags in the model list match those in the console:

FlagMeaning as defined in the console
§ 203suitable for professional secrecy holders under § 203 StGB
GDPRprocessed in line with the EU General Data Protection Regulation
sovereignoutside US CLOUD Act reach; data stays under EU jurisdiction

The "sovereign" flag follows the console's definition (outside the reach of the US CLOUD Act). The Mistral models do not carry it in our catalog.

DPA and sub-processors​