v1.27.0Tera Router v1.27.0 is out: open source, GPL-3.0 licensed, self-hosted. Release notes

Legal

Privacy Policy

What the Tera Router AI service collects to operate — account, billing, and metering data, but not your prompts — and how the website itself handles data.

Last updated November 15, 2026

01

Overview

This policy covers the Tera Router website, the documentation at docs.terarouter.xyz, and the Tera Router AI service — the developer portal and its AI gateway API. Short version: the service needs account, billing, and metering data to run, and it does not store your prompts. The marketing site itself counts anonymous page visits and collects nothing else.

02

Account data

An account holds your name, email address, and optional profile image, with email-and-password sign-in. Verification and account emails are delivered through an email provider (Resend). Login sessions record the IP address and user agent of each device, and you can view and revoke every session in the portal's settings.

03

Billing and usage data

Prepaid credits and top ups are recorded so your balance is right. Every request through the gateway is metered: provider, model, token counts, cost, latency, errors, the client name, and the client IP are logged per request. This is what bills you correctly, powers your usage dashboard, and lets us stop abuse. Token counts and costs are metadata — not content.

04

We don't store your prompts

Request and response content streams through the gateway so it can be routed, checked against your budgets, and metered — but it is never written to the database. Only the per-request metadata above is kept. Upstream AI providers receive and process your prompt content under their own privacy policies when you use the service.

05

API keys and sessions

API keys are stored as an argon2id hash plus an envelope-encrypted copy; the plaintext is shown once when you create or rotate a key and is recoverable only through the reveal flow in the portal. Login sessions can be listed and revoked at any time in the portal's settings.

06

Cookies and local storage

The portal stores sign-in tokens in local storage so you stay signed in, and it uses the cookies needed to keep sessions secure. The marketing site counts page visits with self-hosted, cookieless analytics. No advertising cookies, no cross-site tracking, and no sale of data — anywhere.

07

Third parties

  • Upstream AI providers (OpenAI, Anthropic, Google, OpenRouter, and others) receive and process the content of your requests when you use the service.
  • Resend delivers transactional email such as verification and account notices.
  • Google Fonts serves the marketing site’s web fonts.
  • Nothing is sold, rented, or shared with data brokers.
08

Retention and deletion

Usage records are kept as long as needed to bill correctly, prevent abuse, and meet record-keeping duties. Account data is kept until you close the account. To close your account or request deletion of your data, use the portal's support page — records the law requires us to keep are retained as required.

09

Your rights

You can access, correct, and delete your account data: revoke sessions and rotate keys yourself in the portal, and reach out for anything else. If you have privacy questions or requests, use the portal's support page or open an issue on GitHub.

10

Changes

This policy may change as the service evolves. The last-updated date at the top reflects the current version.

11

Contact

Questions about privacy? Use the portal's support page or open an issue on GitHub.