Privacy Policy

• Last updated: 29 October 2026
• Operated by: an individual, not a company
• Contact: admin@lbrouter.com

1. Who runs this

lbrouter is a single-person project. There is no company, no data team, and no marketing department behind it — one individual runs the gateway and is responsible for the data described here. That person is the data controller for the purposes of this policy. Reach them at admin@lbrouter.com.

2. What is collected

Only what running the service requires:

• Account details: your email address, an optional display name, and a salted hash of your password. The password itself is never stored or logged.
• Sign-in identity: if you sign in with Google or GitHub, the provider's user id and the email it reports, so the account can be linked.
• API keys: stored hashed, with a short preview (last few characters) so you can tell them apart. The full key is shown to you once, at creation.
• Usage records: per request — timestamp, model, provider, token counts, cache tokens, HTTP status, latency, cost, and the key that made the request. This is what powers billing and the Usage and Wallet views.
• Wallet ledger: top-ups, spends and adjustments, with the payment processor's transaction reference.
• Referral anti-abuse data: if you join through a referral, the sign-up IP address, recorded solely to stop the same person farming reward credit through duplicate signups.
• Operational logs: error and request metadata (paths, status codes, timing) kept for a short period to diagnose faults. Prompt text is not part of these logs.

This project does not collect analytics profiles, run advertising trackers, use third-party session-replay tools, fingerprint your device, or build a marketing profile of you.

3. Prompts and outputs

The message content you send is forwarded to the upstream model provider to fulfil your request. It passes through the gateway in memory and is not written to the database or to any log by this project. The gateway keeps only the metadata listed above. Note that the upstream provider you call has its own retention and training policies, which are outside this project's control — check theirs if the content is sensitive.

4. Why it is collected

• to operate your account and authenticate you;
• to meter usage and keep the wallet ledger accurate;
• to prevent fraud and referral abuse;
• to diagnose faults and keep the gateway running;
• to email you about your account, a low balance, or a password reset.

That is the whole list. Nothing is used for advertising, profiling, or sale.

5. Cookies and local storage

The portal keeps a session token so you stay signed in, and stores a couple of preferences (colour theme, interface language) in your browser's local storage. These are required for the site to work as expected and are not shared with anyone. There are no advertising or cross-site tracking cookies.

6. Who it is shared with

Never sold. Shared only where the service cannot function otherwise:

• Upstream model providers — your prompt and parameters, to serve the request you made;
• Payment processors — the details needed to take a top-up payment (they handle your card; this project never sees it);
• An email provider — to send account, reset and low-balance emails;
• Authorities — if compelled by a valid legal order, limited to what is actually requested.

7. How long it is kept

Account and wallet records are kept while the account exists. Usage records are kept for as long as needed for billing history and your own usage views; you may ask to have older ones deleted. Short-lived operational logs are rotated and discarded automatically. When an account is deleted, the account, keys and wallet are removed; anonymised or aggregate spend figures may be retained where they no longer identify you.

8. Your rights and deletion

You can view and update your profile and delete your API keys from the portal at any time. To export or permanently delete your account and its data, email admin@lbrouter.com from the address on the account. Requests are handled on a best-effort basis — this is a hobby project, not a compliance department — but they will be honoured. Where the law gives you further rights (access, correction, objection, portability), they apply and can be exercised through the same address.

Note that deleting your account does not refund credit; see the Terms.

9. Security

Passwords and API keys are stored hashed, traffic is served over HTTPS, and the database is not exposed publicly. That said, this is a one-person project running on modest infrastructure — it is maintained carefully but without the guarantees of a funded security team. Use a unique password, and do not send secrets you could not afford to lose.

10. Children

The service is not intended for anyone under the age required to consent to online services in their jurisdiction. Do not create an account if you are below that age.

11. Changes

This policy may be updated as the service changes; the "last updated" date above reflects the current version. Significant changes will, where practical, be announced by email to registered users.