Security & privacy
Private by architecture, not by promise
A privacy policy describes what a company chooses not to do. A good architecture makes the question irrelevant: data that never reaches a server cannot be misused there.
Who sees what
| Information | Your library | Gateway | Third parties |
|---|---|---|---|
| Your music files | Yes (they live there) | Never stored | Never |
| Audio on a direct link | Sends it | Does not see it | Never |
| Audio when no direct link is possible | Sends it | Passes it through in memory, never stores it | Never |
| What you listen to, and when | Answers requests | No listening history kept | Never |
| Artist, album and track names | Yes | Playlist snapshots | Only for artwork and lyrics look-ups, if enabled |
Transport
- HTTPS everywhere, with automatically renewed certificates
- Direct links use WebRTC's mandatory DTLS encryption
- Library-to-gateway traffic is encrypted between paired nodes; any relay in between forwards ciphertext only
- The home network accepts no inbound connections
Access
- Sign-in is rate-limited; the session cookie is HttpOnly, Secure and SameSite=Strict
- Every state-changing request requires a header browsers cannot add cross-site
- Libraries accept only devices paired with a one-time, 24-hour code
- Each paired device can be revoked on its own
Share links
- 128-bit random codes — not guessable, not sequential
- Stored only as a hash, plus an encrypted copy readable by the owner
- Each listen uses a signed, time-limited ticket bound to that link
- A link opens one song only, and nothing else on the server
What we never do
- No analytics, advertising identifiers or tracking pixels
- No upload of your library to anyone's cloud
- No modification of your audio files
- No cookies on this website
Optional look-ups. If artwork and lyrics enrichment is enabled, the library sends artist, album and track names — nothing else — to MusicBrainz, the Cover Art Archive, Deezer and LRCLIB, and stores the results beside your music so each look-up happens once.