<-- back to chat

Privacy Policy

Last updated: March 2026

1. Information Collected

streaming-LLM collects and processes the following categories of information during normal operation:

  • Prompts and messages: The text content you submit to the service is forwarded to third-party LLM providers (OpenRouter and/or AltLLM) for inference. Prompts are transmitted in real time and are not stored on streaming-LLM servers.
  • Wallet addresses: Your public wallet address is used to establish and manage MPP payment channel sessions. Wallet addresses are public blockchain data and are visible on the Tempo blockchain ledger.
  • Usage metadata: The service records operational metadata including token counts (input and output), the model selected for each request, timestamps of requests, and payment channel session identifiers. This data is used for billing reconciliation and service monitoring.

2. How We Use Information

Information collected by the service is used for the following purposes:

  • Transmit prompts to LLM providers: Your messages are forwarded to OpenRouter or AltLLM (depending on the provider you select) so that the chosen model can generate a response. The response is streamed back to you via SSE.
  • Process payments via MPP/Tempo: Your wallet address and token consumption data are used to calculate charges and process per-token payments through your MPP payment channel on the Tempo blockchain.
  • Improve the service: Aggregated, anonymized usage metadata (such as total token volume by model, error rates, and latency distributions) may be used to identify performance issues, optimize infrastructure, and inform pricing decisions. Individual prompts are never used for this purpose.

3. Third-Party Data Sharing

The service shares data with the following third parties as a necessary part of its operation:

  • OpenRouter: When you select the OpenRouter provider, your prompts and any system messages are transmitted to OpenRouter's API for model inference. OpenRouter's own privacy policy governs how they handle this data.
  • AltLLM: When you select the AltLLM provider, your prompts and any system messages are transmitted to AltLLM's API for model inference. AltLLM's own privacy policy governs how they handle this data.
  • Tempo Blockchain: Payment transactions, including channel open/close operations, payment amounts, and wallet addresses, are recorded on the Tempo blockchain. Blockchain transactions are public and immutable by design.
  • Cloudflare: The service runs on Cloudflare Workers. Cloudflare processes HTTP requests as part of its hosting and edge network infrastructure. Cloudflare's privacy policy governs their handling of request-level data (IP addresses, headers, etc.).

The service does not sell, rent, or trade your data to any third party for marketing or advertising purposes.

4. Data We Do NOT Collect

streaming-LLM is designed to operate without collecting personal information. Specifically:

  • No personal identifying information (name, physical address, phone number) is collected.
  • No email addresses are collected or required.
  • No passwords are collected. Authentication is handled entirely through wallet-based cryptographic signatures.
  • No KYC (Know Your Customer) data is collected. The service does not require identity verification.
  • No user accounts exist. Your wallet address is the only identifier associated with your usage.
  • No tracking pixels, fingerprinting scripts, or advertising identifiers are used.

5. Data Retention

  • Conversation content: Not stored. Prompts and responses are streamed in real time and are not persisted to disk or database on the service's infrastructure.
  • Payment records: Recorded on the Tempo blockchain. On-chain transaction data is immutable and permanent. The service operator does not control the retention of blockchain data.
  • Usage logs: Operational metadata (token counts, model selection, timestamps, error logs) is retained for a maximum of 90 days. After 90 days, usage logs are permanently deleted.

6. Security

The service implements the following security measures to protect data in transit and at rest:

  • TLS encryption: All API traffic between your client and the service, and between the service and LLM providers, is encrypted using TLS (Transport Layer Security). Unencrypted HTTP connections are not accepted.
  • No server-side prompt storage: Because prompts are streamed and not persisted, there is no stored prompt database that could be compromised in a data breach.
  • Payment security: Payments are secured via Tempo blockchain escrow contracts. The MPP payment channel mechanism ensures that funds are locked in on-chain contracts and can only be settled according to the channel's agreed-upon terms. The service operator never has custody of your wallet funds.
  • Infrastructure isolation: The service runs on Cloudflare Workers, which provides per-request isolation through V8 isolates. Each request executes in its own sandboxed environment.

7. Cookies

streaming-LLM does not use cookies. The web interface is built with vanilla HTML, CSS, and JavaScript. No session cookies, tracking cookies, or third-party cookies are set. No analytics scripts (Google Analytics, Mixpanel, etc.) are loaded. Local storage and session storage may be used by the client-side application for UI state (such as the last selected model), but this data remains entirely in your browser and is never transmitted to the server.

8. Children

This service is not intended for use by individuals under the age of 18. The service operator does not knowingly collect or process data from minors. Because no personal information is collected, the service has no mechanism to verify the age of its users. If you are under 18, you should not use this service.

9. Your Rights

Because streaming-LLM does not store personal data, there is generally no personal information to access, correct, or delete. Specifically:

  • Right to access: No personal data is stored on the service's servers. Usage metadata is linked only to wallet addresses, which are pseudonymous.
  • Right to deletion: There is no stored conversation data to delete. Usage logs are automatically purged after 90 days.
  • On-chain data: Transaction records on the Tempo blockchain are immutable by the nature of blockchain technology. Neither the service operator nor any other party can modify or delete on-chain data.
  • Right to data portability: On-chain payment data is publicly accessible and can be independently queried from the Tempo blockchain by anyone.

If you have questions about your data or believe the service has collected information it should not have, please contact us via the channel listed below.

10. Changes to This Policy

This privacy policy may be updated at any time. Changes will be reflected on this page with an updated "Last updated" date. Your continued use of the service after any changes constitutes your acceptance of the revised policy. We encourage you to review this page periodically.

11. Contact

For privacy-related questions, concerns, or data inquiries, please open an issue on the project's GitHub repository:

https://github.com/jiayaoqijia/streaming-LLM