A readable processing chain
Your application calls llmhub.ch with an LLMHub key. LLMHub authenticates the key, applies account permissions, reserves the required credits and sends the request to RouterLab.
RouterLab then runs or routes the request to the selected route. Depending on that route, processing may take place in Switzerland or Germany, or with a third-party model provider identified by RouterLab.
- Client: your application, agent or automation.
- LLMHub: account, API key, permissions, balance and credit ledger.
- RouterLab: technical gateway and selected model route.
- Model: processing at the destination associated with the selected route.
What LLMHub keeps
LLMHub keeps account data, events required for security, payment references, called models, token volumes and credit entries required to operate the service.
LLMHub does not log or permanently archive prompt and response content. A very short-lived technical cache may be used only when required to route or deliver a response.
Payments and communications
Stripe processes payments and related fraud checks. LLMHub does not receive the complete payment card number.
Emails sent by LLMHub use Eyelo SA's internal services. LLMHub uses no advertising or audience analytics tools.
Limits stated clearly
This page describes how LLMHub operates. It is neither a certification nor a retention promise that binds third-party providers.
A proprietary route also depends on RouterLab and the corresponding provider. The Terms and Privacy Policy remain the governing documents.