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 deployment has no persistent volume and exposes no account, newsletter, subscription or other data-entry functions. The application does not persist visitor data.

Fly.io is operated by a US company. Data transfers are covered by standard contractual clauses. See the Fly.io Privacy Policy.

Cookies

rascher.online sets no cookies of any kind. 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 felix.rascher@pm.me.

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 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 and rendered HTML via Askama templates, served from a slim Debian container as a non-root user.
• Persistence: the deployment has no persistent volume or external database service.
• External APIs: the application does not call an identity provider, newsletter provider or other external application API.
• 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 tested and deployed to Fly.io with the flyctl CLI.