No telemetry
Athenaeum does not phone home. Release binaries and container images ship with no product analytics, no usage beacons, and no crash reporting turned on.
No ads or trackers
The web UI, docs site packaging for the product, and shipped clients do not embed advertising networks or third-party tracking pixels.
Your library stays yours
Books, covers, progress, and accounts live on the host you run. The project does not operate a cloud that receives your catalog by default.
Optional ops tools are yours
Prometheus metrics and Sentry or GlitchTip error reporting exist only when you configure them for your own instance. They send to endpoints you choose, not to Athenaeum.
What this covers
- Official release binaries and GHCR container images do not include enabled telemetry, advertising, or usage tracking.
- The Athenaeum project does not receive browsing history, library contents, reading progress, or account data from default installs.
- Planned AI features (research chat, tagging, metadata help) are opt-in. Defaults prefer local backends such as Ollama or LM Studio. Cloud or OpenAI-compatible endpoints only run when you configure them. Prompts then go to the provider you set, not to Athenaeum.
- If you point your instance at an external identity provider, SMTP host, object store, or metadata API, that traffic follows those services' policies. Athenaeum only makes the connections you configure.
This page describes how Athenaeum is built and shipped. It is not legal advice for every jurisdiction. Your deploy may add logging or reverse proxies that record access on your network. That is under your control.