Privacy

Privacy notice

This notice describes the data used by the Flonno API service and its account dashboard.

Who is responsible

For this website, the publisher is Jonas Boos. Postal address: Route de Saint-Cergue 24Bis, PMB 133, 1260 Nyon, Switzerland.

Accounts and API keys

Clerk provides sign-in and account management and may process account information and necessary authentication cookies. When you create a Flonno API key, the full token is shown once. Flonno stores a one-way SHA-256 hash for authentication, together with the key name, permissions, allowed models, creation time, expiry, and last-use time.

Model requests and inference routing

Flonno runs the model itself on its own GPU inference system in Switzerland. Your HTTPS request reaches the Flonno gateway for API-key authentication and usage accounting, then goes to our GPU inference runtime for processing. We do not send model requests to another AI API provider. The current runtime uses an RTX 3090; automatic routing or overflow to an external AI API provider is not configured. Hosting infrastructure is part of the processing chain. This inference location does not mean that authentication, payment or other service data is processed only in Switzerland.

No durable retention of request content

Flonno does not log or save API prompts, uploaded request media, tool content, reasoning content or model completions. Content is processed in memory to answer requests. Prefix and prepared-media caching may reuse content in GPU or host RAM; cached state is removed on eviction or runtime restart, with no fixed retention deadline. Our configured inference runtime does not write request content, context caches or response bodies to disk. Request-body logging and core dumps are disabled. Request content is not used to train models. This policy applies to both streaming and non-streaming API requests without an account setting.

No durable request-content storage does not mean immediate deletion from RAM or no retained service data. Account records, API-key hashes, request metadata, token counts and payment records are retained as described below. Your own application or coding tool may save its conversation history. This policy does not control storage on your device or independently operated services you send content to.

Infrastructure and security boundaries

Flonno operates both the API gateway and the model inference runtime. Our GPU runtime and its hosting infrastructure process request content to generate responses. This notice does not establish hardware-isolated processing or verified attestation of the execution environment. Transport encryption does not make prompts inaccessible to Flonno or infrastructure administrators and does not establish end-to-end encryption.

The current inference server is in Switzerland. The locations of other service recipients, infrastructure retention, processor agreements and applicable international-transfer safeguards require documented confirmation. This notice does not promise exclusive Swiss or EEA processing or universal compliance. Obtain these details from the publisher before submitting personal data requiring these assurances.

Purposes and service recipients

Account information is used to authenticate users and manage access. Request content is used for inference. Request metadata supports access controls, security, troubleshooting and usage accounting. Clerk provides authentication; web hosting, database hosting and inference hosting infrastructure process data needed for their respective functions. Cloudflare acts as the CDN and reverse proxy in front of www.flonno.com: it terminates TLS, caches public pages and static files, and passes API requests (including prompts and responses) through to our servers without caching them.

If you purchase prepaid credit, Stripe processes checkout and payment information. Flonno stores payment references, credited amounts, balance entries and usage reservations to account for payments and model usage. Card details are entered through Stripe Checkout.

Processing abroad and contractual information

External infrastructure may process personal data outside Switzerland. This notice does not establish that processing is limited to Switzerland or the EEA. Confirmed recipient information, destination countries, applicable transfer safeguards and any required data-processing agreement must be obtained from the publisher before submitting personal data that requires these assurances. These deployment-specific details are not yet fully documented here.

API access logs

For each request authenticated with a known Flonno key, the service may store the key name and prefix, endpoint, model, request time, source IP address and the proxy header it came from, user-agent, HTTP status, duration, and token counts when the provider reports them. The logs do not contain the bearer token, prompt, or response. Short-lived abuse counters use source IP and account identifiers; scheduled maintenance removes counter windows older than one day. Log records are stored in the PostgreSQL database configured for the service and are removed in scheduled batches after 30 days.

On Vercel, the service uses the platform-set x-vercel-forwarded-for header. Outside Vercel, production requires a configured trusted proxy header whose value is sanitized by the hosting operator. In the self-hosted setup, our edge proxy accepts the cf-connecting-ip header only from Cloudflare network addresses; client-supplied cf-connecting-ip and x-real-ip are otherwise ignored. If no valid address is available, IP-restricted requests are denied.

Campaign attribution

When a page address includes a campaign label (utm_source, utm_medium, or utm_campaign), Flonno stores that label and, when the browser provides one, the referring site’s hostname. The label is kept in a first-party cookie for 30 days so it can follow the sign-up flow. If you then create an account, Flonno stores the same label with your account id. The full referring address, your IP address, and API prompt or completion text are not stored for this purpose. A separate daily counter records how many browser sessions opened each campaign link. Those counters are not tied to an account. A visit referred by x.com, twitter.com, or t.co, without a campaign label, is counted in that daily total as a visit from X and does not replace a campaign label you open later. This measurement stays on Flonno’s own service.

Campaign labels stored with an account are kept with that account record. Daily visit counters are kept as totals. You can ask the publisher to delete an account label together with other account data.

Website analytics

Flonno runs Umami on its own website server to measure page visits, navigation, scroll depth, and product actions such as sign-up clicks, sign-in, API-key actions, and checkout. That server is separate from the GPU inference system in Switzerland. The website server’s public network address currently geolocates to Austria. Umami does not use cookies. It does not receive names, email addresses, account identifiers, API keys, prompts, responses, or form contents. Page addresses are reduced before storage: values other than short public campaign labels are removed, and account-specific paths are grouped. A connection address may be used to derive a country and an anonymous session. It is not stored as a visitor profile, and visit data is not sent to Google.

On public pages, Umami also records anonymous click positions (heatmaps) and a reconstruction of page layout, scrolling and clicks (session replays) to improve navigation. Typed input is masked, and the dashboard, sign-in and account widgets are excluded from recording. Replays are kept only on the same website server and are not linked to an account.

The analytics program is part of the website. There is no separate analytics consent banner. Ad blockers and interrupted visits mean the analytics record is not a complete accounting record. Payment and API access records remain the authoritative operational records.

Retention

API request content is not written to Flonno logs, databases or backups. The scheduled maintenance process removes metadata-only API access logs older than 30 days in bounded batches; large backlogs may take additional runs. Revoking an API key stops its use but does not delete historical metadata logs or billing records. Account, payment and metadata-backup retention periods are not fully specified here. You may contact the publisher to request access or deletion; applicable accounting obligations and legitimate security needs may limit deletion.

Your choices and rights

Depending on applicable law, you may have rights to access, correct, erase, restrict, object to certain processing, or request portability where applicable. You may also complain to the competent data protection authority, including the Swiss Federal Data Protection and Information Commissioner. Contact the publisher by post at the address above for inquiries about this website. Contact the operator of a separately deployed Flonno instance about that instance’s data.

Updates

This notice may be revised when the service or its data practices change. Check this page for the current version.

Free-credit abuse prevention

To issue the one-time $1 evaluation credit, we check your verified primary account email and retain a keyed, non-public hash of that email with the credit claim. This helps prevent duplicate claims, including after account deletion. The claim record does not store the raw email. We retain this limited abuse-prevention record while the offer operates and review retention when the offer ends. Account email and authentication data are processed separately as described above.

Last updated 31 October 2026.