Legal

Hosting

rascher.online is served by a server-side web application running on a single Fly.io machine in the Frankfurt region (fra). Fly.io processes technical request data that is necessary to deliver the site, route requests and operate the service reliably.

The production deployment does not store login sessions, newsletter audit data, or any other personal data on its persistent volume. Authentication and the operator-notes newsletter are currently available only on a separate staging environment that is not linked from this page.

Fly.io is operated by a US company. Data transfers are covered by Fly.io's data processing agreement and standard contractual clauses. See the Fly.io Privacy Policy and Fly.io Data Processing Addendum.

Cookies

The production deployment of rascher.online sets no cookies of any kind. The pages you see are fully static from your browser's perspective; no first-party session cookies, no third-party cookies, no tag managers, no advertising pixels, and no analytics scripts are loaded.

Server Logs and Security

Fly.io and the application record technical log data such as request time, HTTP method, requested path, response status and network metadata. The request IP address may be processed briefly for operational security, abuse prevention and debugging. Query strings, form bodies and authorization headers are deliberately excluded from access logs.

This data is not used to build personal profiles. Logs are kept only as long as needed for those operational purposes or as required by law.

Your Rights

You can request access, correction, deletion, restriction of processing, data portability and objection where the GDPR grants these rights. For privacy requests, contact contact@rascher.online.

You can also lodge a complaint with a competent data protection authority.

International Transfers

Hosting with Fly.io may involve transfers of technical request data to the United States. These transfers are covered by Fly.io's data processing agreement and standard contractual clauses.

Application Stack

For transparency, the public components of the running application are:

• Server: a Rust binary built with the Axum HTTP framework, rendered HTML via Askama templates, served from a slim Debian container as a non-root user behind tini.
• Persistence: no personal-data persistence is active on the production deployment. Pulse signal storage that staging maintains is not exposed on production.
• HTTP clients: reqwest with rustls is used where outbound calls are required. The production deployment does not call any external identity provider, newsletter platform, or LLM API. All outbound calls go over TLS.
• Static assets: CSS, fonts and brand assets are served directly from the container; no external CDN, font service or analytics provider is loaded by the browser.
• Build and deploy: source lives on GitHub, container images are built on GitHub Actions runners pinned to commit SHAs and deployed to Fly.io with the flyctl CLI.