Last updated 23 June 2026

Privacy.

Obol connects to your self-hosted music server, reads what you listen to, and pays the artists behind it. That means it touches a few pieces of data about you. Here's exactly what, and why.

What we collect

When you connect a server, we store its URL, your username, and your password so the agent can sign in and read your listening history on your behalf. We read your play history (scrobbles) to know which artists to pay. We send artist names to MusicBrainz to resolve them to a canonical identity. For each payment we record the track title, amount, timestamp, the sending and receiving wallet, and the on-chain transaction hash.

How it's stored

Your data lives in our application database. Server credentials are kept only to operate the agent. Encrypting stored credentials at rest is on the roadmap and not yet in place, so don't reuse a password here that protects anything you can't afford to expose.

Who we share it with

We don't sell your data and we don't run ads. Operating the service means a few third parties see parts of it: MusicBrainz (artist names, for resolution), Circle (wallet and payment settlement), and our database host. Each sees only what its job needs.

Payments and the chain

Payments settle in USDC on the Arc testnet. On-chain transactions are public by nature: wallet addresses and amounts are visible to anyone reading the chain. Testnet tokens carry no real-world monetary value.

Removing your data

Want your server credentials and records deleted? Open an issue on the GitHub repository and we'll remove them. On-chain payment records can't be deleted, since the chain is immutable.