Back

Terms of Use

Effective Date: 2026-08-15

1. Nature of the Service

Hyperion is not a security product or security-focused AI platform. It is a local-first client interface for interacting with third-party AI services.

By using Hyperion, you acknowledge that you are using a tool to interact with external APIs, specifically OpenRouter, and that Hyperion itself does not provide the AI intelligence, host the models, or secure the transit beyond standard HTTPS.

2. User Responsibility

You are solely responsible for:

  • Maintaining the security of your OpenRouter API key.
  • The content of the prompts and data you submit through the interface.
  • Selecting the appropriate model and provider for your use case.
  • Any API costs incurred on your OpenRouter account through the use of this interface.
  • Complying with all applicable laws, regulations, and OpenRouter's terms of service.

3. OpenRouter Integration

Hyperion operates as an independent client for the OpenRouter API. We are not affiliated with, endorsed by, or operated by OpenRouter. Your use of OpenRouter's services through Hyperion is governed by OpenRouter's own Terms of Service.

4. No Guarantees

Hyperion is provided "AS IS" without warranties of any kind. We do not guarantee:

  • The accuracy, reliability, or safety of the model outputs.
  • The continuous availability or uptime of the interface or external services.
  • The retention or non-retention policies of third-party model providers.
  • Uninterrupted service or error-free operation.

5. Assumption of Risk

Your use of external AI services, submission of sensitive information, and usage of API keys within this browser environment is entirely at your own risk. Hyperion and its creators shall not be held liable for any damages, data leaks, API overages, or consequences arising from the use of this interface.

Security & Isolation RecommendationIn the hosted version, your browser holds credentials in memory during the session. We strongly recommend cloning the open-source repository and running Hyperion locally. The local version includes an option to use a `.env` file (`OPENROUTER_API_KEY`) which securely proxies requests so the key never touches your browser memory.