Privacy Policy
This policy explains what information Hybermedia Co., Limited, of Room A08, 2/F, Lee Ka Industrial Building, 8 Ng Fong Street, San Po Kong, Kowloon, Hong Kong, which runs the Service under the name Hyperouter (“Hyperouter”, “we”, “us”), collects when you use hyperouter.app, the Hyperouter API, Hyperouter Chat and Hyperouter Studio (the “Service”), how we use it, and the choices you have. We are responsible for this information. Card payments, where offered, are handled by Stripe, which receives your card details directly under its own privacy policy.
1. Summary
- We keep the inputs and outputs of every request encrypted for 180 days to meet our legal obligations. We disclose them only to authorities that present a valid legal request. They are never used to train models, never shown in the dashboard and never sold.
- We do not sell personal information, and we do not use your content to train models.
- Your prompts are sent to the model provider that serves each request. You control which providers are eligible.
- We keep request metadata (model, provider, token counts, cost, time) so we can bill you and keep the Service running.
2. Information we collect
Information you give us
- Account and contact details: name, email, company, and anything you include when you request access or email us.
- Payment information: we run no payment processor and hold no card or wallet details. When you pay for a top-up, you tell us the payment reference in a support ticket; staff check the payment and credit your balance, and the reference, amount and fee are noted in your account's credit ledger. Any screenshot of the payment you attach to the ticket is stored with the ticket.
Information collected automatically
- Request metadata: timestamp, API key ID, model, provider, token counts, cost, latency, status code and the optional
userfield you send. - Technical data: IP address, user agent and request headers, used for security, abuse prevention and rate limiting.
3. Prompts and outputs
Prompts, files and model outputs pass through our systems to be routed and returned. To meet our legal obligations, we keep a copy of the inputs and outputs of every request for 180 days, and then it is deleted automatically. The inputs are the request you send, with its prompts, the files you upload, and the files we fetch from links you give to serve it. The outputs are the reply, streamed or not, and the images and videos generated for you.
This copy is encrypted before it is stored. We disclose it only to authorities that present a valid legal request, and only the engineers who answer such a request can read it. It is never used to train models, never shown in the dashboard or returned by the API, and never sold.
To fulfil a request we send its content to the model provider selected for that request. Providers process it under their own terms; some may retain data for a limited time for abuse monitoring.
4. How we use information
- to provide, route and bill requests, and to show you usage and spend;
- to issue API keys and respond to your emails;
- to detect and prevent fraud, abuse and security incidents;
- to measure provider performance and improve routing, using metadata only;
- to send service notices, such as changes to these policies or to pricing;
- to meet legal, tax and accounting obligations.
Where the GDPR applies, we rely on performance of our contract with you, our legitimate interests in running a secure service, and compliance with legal obligations.
5. Who we share information with
- Model providers, which receive request content needed to serve your request.
- Service providers that host our infrastructure or send email for us, under contracts that limit their use of the data.
- Authorities, when required by law or to protect the rights, safety or property of our users or others. The copy of your inputs and outputs (section 3) is disclosed only in answer to a valid legal request.
- A successor, if Hyperouter is involved in a merger, acquisition or sale of assets, subject to this policy.
6. Retention
| Data | Kept for |
|---|---|
| Prompts, files and outputs | 180 days, encrypted, to meet legal obligations (section 3) |
A rewritten prompt (prompt_expand), readable through the API | 30 days |
| Request metadata | As long as the credit ledger: each request is the billing record of its charge |
| Credit ledger and payment references | As long as tax and accounting law requires, typically 7 years |
| Sign-in and session logs (IP, user agent) | 90 days |
| Audit log of changes to your account, keys and credits, with the IP they came from | Not deleted: it is the permanent record of who changed what |
| Support tickets and their attachments | Not deleted, also after the account is closed: they are the record of what was asked, paid and refunded |
| Access request emails | Until the request is closed, plus 12 months |
Closing your account
You can close your account yourself on the Account page of the dashboard. Closure takes effect at once and cannot be undone.
- At once: every API key, dashboard access token and session stops working, and your webhook endpoints are switched off. Requests already running finish and are charged as usual. Nobody can sign in to the account again.
- Deleted when nothing is owed either way: your linked Google and GitHub sign-ins, passkeys, authenticator app, recovery codes, sign-in log and sessions are deleted, and the name, email address and profile picture on the account are replaced with placeholders. If no credit is left and no request is still running, this happens at closure.
- If credit is left, we refund it less the top-up fee, as the Terms set out, and write to your account email to arrange the refund. The deletion above follows once the refund is made; until then your email address is kept so we can reach you.
- Kept: the credit ledger, request metadata, support tickets and the audit log stay for the periods in the table above, tied to the account's ID rather than to your name or email. The encrypted copy of inputs and outputs is deleted 180 days after each request (section 3), whether or not the account is closed.
7. Security
Traffic to the Service is encrypted in transit with TLS. API keys are stored hashed. The copy of your inputs and outputs is encrypted with AES-256 before it is stored. Access to production systems is limited to staff who need it. No system is perfectly secure; if we learn of a breach that affects your personal information, we will notify you as required by law.
8. Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal information, to object to or restrict certain processing, and to withdraw consent. California residents may request to know what we collect and ask us to delete it; we do not sell or share personal information for cross-context behavioral advertising.
To make a request, email [email protected] from the address on your account. We will respond within 30 days. You may also complain to your local data protection authority.
9. International transfers
We and our providers may process information in countries other than yours. Where required, we use appropriate safeguards such as Standard Contractual Clauses for these transfers.
10. Cookies
hyperouter.app does not use advertising or analytics cookies. The site loads fonts from Google Fonts, which receives your IP address when you visit. Signed-in areas may use strictly necessary cookies to keep you logged in.
11. Children
The Service is not directed to children under 18, and we do not knowingly collect their information. If you believe a child has given us information, contact us and we will delete it.
12. Changes
We may update this policy. We will post the new version here with a new effective date and, for material changes, notify account holders by email before they take effect.
13. Contact
Privacy questions or requests: [email protected].