Security and privacy, by design

Client data, unpublished findings and exploit research belong in a private environment. Every instance runs on a dedicated GPU in the EU, stores no prompts or outputs, and is never reached through our control plane.

What we are building for

Nine design principles, in three areas.

Infrastructure

Where your instance runs and who operates it.

  • Dedicated infrastructure

    Each instance hosts one model on its own GPU. GPUs are not shared between customers.

  • EU GPU providers only

    Instances run only with EU-based GPU providers that are certified to ISO/IEC 27001. You do not operate or configure the provider.

  • ISO/IEC 27001 certified company

    The company behind the service runs an ISO/IEC 27001 certified information security management system. Extending the certification scope to this service is planned.

Your data

What happens to prompts, outputs and instance content.

  • No training on your data

    Prompts and outputs are not used to train models.

  • No prompt or output storage

    Prompts and outputs are never stored. Request logging is off, and nothing is written to logs or disks.

  • Complete deletion

    Stopping an instance deletes it. Instance content is not kept afterwards.

Access and contracts

Who can reach your instance and what is agreed.

  • Limited control plane

    Our control plane can start, stop and delete your instance. You call the instance directly over TLS, and inference traffic never passes through the control plane.

  • API key access control

    Each instance has its own API key, checked on the instance. Only a hash of the key is stored by us.

  • Data processing agreement

    An AVV / DPA is part of onboarding, together with a documented list of subprocessors.

What our control plane can and cannot do

The control plane manages the lifecycle of your instance. It is never part of the data path.

It can

  • Start, stop and delete your instance
  • Redeploy it after a failed health check
  • Store a hash of your API key

It cannot

  • Receive your prompts or outputs
  • Log in to or read a running instance
  • Sit in the path of inference traffic
  • Keep instance content after deletion

The life of your data

From the request to the deletion of the instance.

  1. You send a requestFrom your tools or agents, over TLS, straight to the endpoint of your instance
  2. Your instance answersThe model runs on your dedicated GPU. The control plane is not involved
  3. Nothing is keptPrompts and outputs are not stored and not used for training
  4. You stop the instanceIt is deleted, and its content is not kept afterwards

Certifications and contracts

What is held today and what you receive when you onboard.

Held today

ISO/IEC 27001

Our company ISMS is certified. Extending the scope to this service is planned.

Providers

Certified EU providers

All EU GPU providers are certified to ISO/IEC 27001. Further certifications such as SOC 2 are listed per provider in the data processing agreement.

At onboarding

Data processing agreement

An AVV / DPA and a documented list of subprocessors are part of onboarding.

Authorised security work only

The models are built for authorised security work. Some Red Team models need verification before you can deploy them, and every use remains subject to the terms and applicable law.

Security questions

Where are my prompts processed?

On your own instance: one model on a dedicated GPU, with an EU-based GPU provider. Requests go straight to the endpoint of your instance.

Can your team read my prompts?

No. Inference traffic does not pass through our control plane, prompts and outputs are never stored, and we have no technical access to running instances. The data processing agreement is the binding reference.

Do you train on my data?

No. Prompts and outputs are not used to train models.

What happens to my data when I stop an instance?

Stopping an instance deletes it. Instance content is not kept afterwards.

Is EU hosting enough for GDPR?

It supports GDPR-oriented processing, but compliance also depends on contracts and on how you use the service. That is why a data processing agreement is part of onboarding.

Which statements are binding?

The data processing agreement and the terms of service are binding. This page describes how the service works.

Request early access

Tell us about your team and the models you want to run. We will contact you as soon as your tier is available.