Effective September 23, 2026 · Operated by Tripsittr LLC · Draft pending legal review · PDF
SoundChex Server — Privacy
The short version is absolute: the server sends nothing to Tripsittr LLC. Ever. No telemetry, no analytics, no crash reporting to us, no update phone-home, no account with us. This page exists to be specific about what data exists, where it lives, and where it goes.
1. What data the server holds — all of it on your machine
| Data | Where it lives |
|---|---|
| Accounts and passwords (hashed) for your household | The SQLite database file on your server |
| Profiles, listening/watching history, resume points, watchlists, highlights and notes | Same database |
| Your media catalogue and artwork | Same database + local storage folder |
| Your media files themselves | Your watch folders — never moved until catalogued, never deleted |
| Logs and device reports (what your own devices reported failing) | Local log files and the same database — "Admin → Device reports" is your devices reporting to your server, not to us |
Tripsittr LLC can see none of this. There is no mechanism by which it could reach us, because none was built.
2. Network connections the server makes
Every outbound connection is one you configured, and each goes directly from your machine to that service:
- Metadata sources — TMDB, MusicBrainz, AcoustID, Open Library, iTunes, Spotify, OpenSubtitles — queried only if enabled, with your keys, under their privacy policies. What they see is the lookup itself (e.g. a film title, an audio fingerprint), coming from your IP address.
- Subtitle and artwork downloads — same character: your server fetching a file you asked for.
- Server-to-server transfers — only between two machines you control, only after the four-digit-code approval on both ends.
- Nothing else. No connection to Tripsittr LLC infrastructure exists in the server. When SCNet launches, connecting to it will be a separate, explicit, off-by-default choice with its own privacy notice.
3. Data collected by Tripsittr LLC: none
We do not know you installed SoundChex. We do not know your library size, your uptime, your version, or your IP address. If the GitHub download counter ticks up, that's GitHub's statistic, governed by GitHub's privacy policy, and it isn't tied to anything you run.
4. Your household's privacy is your configuration
Because you are the operator, a few things are yours to decide and document for your users (your family, usually): who has accounts, that profiles carry no password and are not a security boundary (documented here), and whether the server is reachable from the internet. If you expose it publicly, login is rate-limited, but the choice — and the responsibility to your users — is yours.
5. Deleting everything
Delete the SoundChex directory (or the installed app), the SQLite database and the storage folder, and every trace of the catalogue, accounts and history is gone. Your media files, as always, remain exactly where they were.
6. Changes
If a future version ever adds any network behaviour beyond section 2 — even an update check — this document will change first, the changelog will say so in plain words, and it will be opt-in. "Zero data collection" is a commitment, not a default setting.