▰▰~/flume

Privacy Policy

last updated: 11 June 2026

1. Data controller

The controller responsible for the processing of personal data on this website and the Flume service is:

Swiss Web Development Kiefer
c/o Marvin Kiefer
Steinstrasse 60
5406 Rütihof, Switzerland
marvin.kiefer@swisswebdev.ch

This policy applies to the website and application at useflume.dev. It is written to satisfy both the Swiss Federal Act on Data Protection (FADP) and, for users in the European Economic Area, the EU General Data Protection Regulation (GDPR).

2. What data we collect

Account data (via Clerk). When you create an account, our authentication provider Clerk processes your email address, name, optional profile picture, sign-in credentials or social-login identifiers, and authentication events (sign-in timestamps, device/browser information).

Vaulted provider API keys. AI provider keys you store with us are encrypted with AES-256-GCM before being written to the database. The encryption secret exists only in the backend environment. Keys are write-only: no interface exists to read a stored key back out; keys are decrypted only in memory, per request, by the proxy itself.

Proxy tokens. We store only a SHA-256 hash of each proxy token you mint, together with the name and provider scope you assign to it.

Usage metering data. For each request routed through the proxy we record: timestamp, endpoint path, model name, token counts (input/output/cache), estimated cost, response latency, and HTTP status code. We do not store the content of your requests or responses — prompts and completions pass through the proxy and are discarded.

Technical access data. Our hosting infrastructure processes IP addresses, user-agent strings, and request metadata in server logs for security and operation of the service.

Correspondence. If you contact us by email, we process the data you provide in your message.

We do not use analytics, advertising, or tracking services on this website.

3. Purposes and legal bases

We process personal data for the following purposes:

  • ▰Providing the service — account management, proxying API requests, metering usage and cost (GDPR Art. 6(1)(b), performance of a contract).
  • ▰Security and abuse prevention — authenticating requests, detecting misuse, server logging (GDPR Art. 6(1)(f), legitimate interest in a secure service).
  • ▰Communication — responding to your inquiries (GDPR Art. 6(1)(b) or (f)).
  • ▰Legal compliance — fulfilling statutory retention and disclosure obligations (GDPR Art. 6(1)(c)).

Under the Swiss FADP, we process personal data in accordance with the principles of lawfulness, proportionality, and purpose limitation (Art. 6 FADP).

4. Proxied request content

The core function of Flume is to forward your API requests to the AI provider you choose (e.g. OpenAI, Anthropic, Google). Request and response bodies — which may contain personal data you include in prompts — are transmitted to the selected provider on your instruction and are not stored by us. The privacy policy and terms of the respective AI provider apply to that processing. You are responsible for ensuring you are permitted to send any personal data contained in your prompts to the provider you select.

5. Processors and third-party services

We use the following processors to operate the service:

  • ▰Clerk Inc. (USA) — authentication and user management.
  • ▰Convex Inc. (USA, infrastructure on AWS) — application database and backend, including encrypted keys, token hashes, and usage logs.
  • ▰Vercel Inc. (USA, global edge network) — website and application hosting, including server logs.

Fonts are self-hosted; no requests are sent to Google Fonts or other font CDNs when you visit this site. We do not sell personal data and do not share it with third parties except the processors listed above and AI providers you explicitly route requests to.

6. International data transfers

The processors listed above are located in the United States, so personal data is transferred outside Switzerland and the EEA. Transfers are safeguarded by the respective provider's certification under the Swiss–U.S. and EU–U.S. Data Privacy Framework and/or by EU Standard Contractual Clauses (with the Swiss addendum recognized by the FDPIC), as applicable to the respective provider.

7. Retention

  • ▰Raw request logs: automatically purged after 90 days.
  • ▰Aggregated usage statistics: retained while your account exists.
  • ▰Account data, vaulted keys, token hashes: retained until you delete them or your account.
  • ▰Email correspondence: retained as long as needed to handle your inquiry and any statutory retention periods.

Deleting your account immediately and permanently removes every key, token, log entry, and aggregate we hold about you.

8. Your rights

Subject to the conditions of the FADP and GDPR, you have the right to:

  • ▰access the personal data we hold about you (GDPR Art. 15, FADP Art. 25),
  • ▰rectification of inaccurate data (GDPR Art. 16),
  • ▰erasure (GDPR Art. 17) — available self-service via account deletion,
  • ▰restriction of processing (GDPR Art. 18),
  • ▰data portability (GDPR Art. 20) — available self-service as a JSON export in your account settings,
  • ▰object to processing based on legitimate interests (GDPR Art. 21),
  • ▰withdraw consent at any time, where processing is based on consent.

To exercise any right, email marvin.kiefer@swisswebdev.ch. You also have the right to lodge a complaint with the Swiss Federal Data Protection and Information Commissioner (FDPIC) or, if you are in the EEA, with your local supervisory authority.

9. Security

All traffic is encrypted in transit with TLS. Provider keys are encrypted at rest with AES-256-GCM; proxy tokens are stored only as SHA-256 hashes; request and response bodies are never persisted. Access to production systems is restricted to the operator.

10. No automated decision-making

We do not use your personal data for automated decision-making or profiling within the meaning of GDPR Art. 22.

11. Cookies

This site uses only strictly necessary cookies for authentication. See the Cookie Policy for details.

12. Changes to this policy

We may update this policy to reflect changes in the service or in legal requirements. The current version is always available at this address; the date above indicates the last revision. Material changes affecting registered users will be announced in the application.