Privacy Policy
Datenschutzerklärung — last updated October 2026
Controller
Denis Arnst (Sapd), Vienna, Austria. E-mail git@sapd.eu.
The short version
This site is a static website. It sets no cookies of its own, runs no analytics or tracking scripts, and loads all assets (including fonts) from this domain. Personal data is processed only where technically necessary: server logs at our hosting provider, a technical install identifier when a (currently free) license key is issued, and push notifications passed through our relay to Apple if you use the iPhone or iPad app with notifications on. Nothing is sold on this site today.
Hosting and server logs
The site is served by Cloudflare, Inc. (USA). When you access it, connection data (IP address, user agent, requested URL, timestamp) is processed and may be briefly retained in server logs for delivery, security, and abuse prevention. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) in operating the site securely. Cloudflare is certified under the EU–US Data Privacy Framework; transfers are additionally covered by standard contractual clauses.
License service
When a license key is requested or renewed, and about once a week to check in, your Lumastra install transmits its install ID (a random technical identifier generated by your installation), the Lumastra version it runs, and a licensing status code. It is not linked to your name. Legal basis for issuing and renewing keys: performance of a contract (Art. 6(1)(b) GDPR).
To know how many installations exist and which versions they run, we record for each such request the request type, the license tier, the release number, the country derived from the connection, and a pseudonymised install ID (a keyed hash of the install ID). These records contain no IP address and are deleted after three months. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) in knowing how widely and in which versions Lumastra is used. Installs can switch the weekly check-in off in their admin settings or in the setup wizard; key issuing and renewal, and the push relay token while iOS notifications use our relay, still take place.
An install contacts the license service at first start and about once a week, or every six hours while iOS push notifications use our relay; the connection's IP address is processed like any other request (see above). Nothing else leaves your server: no media, metadata, or usage data is transmitted to us.
Push notification relay (push.lumastra.org)
So that the iPhone and iPad app can receive notifications without every server needing its own Apple key, Lumastra servers can hand notifications to a relay we run (hosted by Exoscale in Frankfurt, Germany), which forwards them to Apple's push service. The relay receives the device push tokens of the recipient, a short-lived token carrying the install ID, and a content-free payload (the server's name, a generic text, a notification ID and links back to that server; no media titles, names or e-mail addresses). It keeps no copy beyond what delivery and abuse prevention need. For this data the operator of the Lumastra server is the controller and we act as processor (Art. 28 GDPR). Details: What Lumastra sends where.
Lumastra apps
The iPhone, iPad and Apple TV apps talk only to the Lumastra server you sign in to. Your library, watch history, error reports and diagnostics go to that server, not to us. The only data that reaches us is the push relay described above, if notifications are on. The apps are distributed by Apple (TestFlight / App Store), whose own privacy policy applies to that.
GitHub and community
The source code, issues and discussions are hosted on GitHub, and the community chat on Discord. Their own privacy policies apply when you use them.
Your rights
Under the GDPR you have the right to access, rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interests (Art. 15–21 GDPR). You also have the right to lodge a complaint with a supervisory authority — in Austria, the Datenschutzbehörde.
No profiling, no automated decisions
No automated decision-making or profiling within the meaning of Art. 22 GDPR takes place.