Privacy note · 20 August 2026
Your history is not the product.
This note describes the data flows a person using Obelus can reasonably care about. Deployment-specific processors and retention remain the responsibility of the instance operator.
Your archive
Music, game, film, and television records are scoped to your account in the Obelus database. Obelus does not sell this history, build an advertising profile, or expose a social feed. Connected services receive only the requests needed to import or enrich the records you ask Obelus to maintain.
Optional AI processing
When AI processing is enabled, the deployment's configured provider may receive selected listening, play, watch, rating, and recommendation feedback summaries to produce analysis, recommendations, taste profiles, and Shrine prose. Obelus currently supports Anthropic as an external provider. Raw credentials and OAuth tokens are not included in those prompts. You can stop all new personal-history AI generation under Settings → Account. Previously generated text remains in your archive until you delete the account or its underlying records.
Operational monitoring
An operator may configure Sentry for error and performance reporting. Obelus disables browser session replay and does not send default user PII through the backend integration. Before transport, Obelus removes user identity, console/log breadcrumbs, error-message values, request bodies, raw URLs and transaction names, query strings, cookies, headers, span payloads, extra fields, and frame locals. Reports can still contain browser, timing, stack, and technical failure type/context. Separate instance stdout logs may name an account or internal record while diagnosing an import; deployment operators control access and retention for both stores.
Public instance preview
An operator can enable an anonymous sign-in preview made from aggregate listening records on that instance. It may include totals, one artist, and top tracks, but not the account username or email. This deployment choice is separate from authenticated archive access.
Credentials and connected services
Passwords are stored as hashes. Supported OAuth and service credentials are encrypted at rest and used only for their connection. Obelus can import data from services such as Last.fm, Spotify, YouTube Music, Steam, Trakt, and TMDB; those services apply their own privacy terms when you authorize or use them.
Your controls
From Account settings you can disable new AI processing, download a machine-readable export of your account-owned records, disconnect services, or permanently delete the account and its associated data. Operators remain responsible for infrastructure backups and their retention window; deletion cannot retroactively erase an older backup until that backup expires.