Privacy

A short version: your music, your library, and your listening history stay on your computer. The only network calls Audeeport makes by default are the ones it has to.

What stays local

These never leave your machine:

• Your music files. Audeeport reads them in place and never copies them off-device.
• Your library index. ~/.audeeport/audeeport.db, a SQLite database. Stays on the machine that owns it.
• Your EQ presets and output profiles. ~/.audeeport/eq_state.json and related files.
• Your skins. ~/.audeeport/skins/.
• Your listening history. What you played, when, for how long, and what you skipped. None of this is logged anywhere outside your machine, unless you connect Last.fm scrobbling (opt-in, see below).
• Your search queries. Never sent off-device.
• Library statistics. Track counts, format breakdowns, top genres, total playtime. Calculated locally.

What goes out, and why

Audeeport makes the following network calls:

• License validation. On activation, and periodically thereafter, the app verifies your license against our server. The verification is signed and offline-cacheable. Once validated, the app keeps working without internet for an extended grace period. The server sees your license key, your device name, and your IP. It doesn’t see your library, your tags, or what you’re playing.
• Update checks. The Testing Center polls our updates endpoint to see whether a newer build is available for your channel (beta vs stable). The endpoint sees your current version and your platform. Nothing else.
• Crash reports (opt-in, off by default). If you turn this on in Settings > About, Audeeport sends a stack trace, the app version, your OS, and a hashed machine ID when the app crashes. Nothing identifying. Nothing about your music.
• Feedback (you-initiated). When you use the Send Feedback form, Audeeport sends what you typed, the app version, the OS, and a hashed machine ID. We read it, we reply.
• Metadata lookups (opt-in, per-album). When you Analyze an album, Audeeport queries online music databases with the tags you have or with an audio fingerprint generated from the file. The query doesn’t include any identifying information about you. Audio fingerprints are short hashes of acoustic properties, not the audio itself.
• Streaming metadata. Radio station info, podcast feed metadata, news RSS contents. These come from public endpoints whenever you load the relevant view.
• Audio streams. The radio you tune to, the podcast you play. These are direct connections to the publisher’s server.
• Last.fm scrobbling (opt-in). If you connect a Last.fm account in Settings, Audeeport sends a “now playing” update when a track starts and scrobbles the track to your Last.fm history after you have played enough of it. This is the one path by which your listening history leaves your machine, and only for the account you connect. It is off until you set it up.

What never goes out

• Listening history, unless you connect Last.fm scrobbling (opt-in).
• Library contents (your file paths, tags, or audio data, except for opt-in fingerprint queries during Analyze).
• Analytics on which features you use, how long you keep the app open, or what you click.

Local automation surface

Two features run a small local server that never leaves your machine:

• Headless daemon and MCP. If you enable the headless service (Settings > Network, or audeeport --daemon), Audeeport runs an HTTP server bound to 127.0.0.1 only, so nothing off your machine can reach it. It is authenticated with bearer tokens stored under ~/.audeeport/ (master-token, per-client records in tokens/, and mcp-token when you use the MCP integration). This is off by default; you turn it on explicitly.
• Wireless device link. When you pair a phone, the desktop app runs a token-authenticated HTTP server on your local network to push albums and audiobooks to that device. It is a direct connection over your LAN and does not route through us. Forgetting a device from Settings > Network revokes the token on both sides.

Cookies on the website

Three essential cookies, all first-party:

• audeeport_token. Your sign-in session. HttpOnly, SameSite=Lax, 30 days.
• audeeport_invite. Invitation-gate access for /private. Cleared on sign-out.
• audeeport_cookies_ack. Remembers you’ve dismissed the cookie banner. 1 year.

No analytics cookies. No third-party trackers. No marketing pixels.

Wiping your local data

Quitting Audeeport and running rm -rf ~/.audeeport removes everything Audeeport has stored on your machine: library index, presets, skins, transcripts, backups, logs, and any automation tokens (master-token, tokens/, mcp-token). Your music files, sitting in your music folders, are not touched.

On Windows, the equivalent path is %USERPROFILE%\.audeeport. On Linux, it’s ~/.audeeport.

Account deletion

Email hello@audeeport.com with the address you signed up under and “delete account” in the subject. We deactivate your license, remove your device list, and purge the account record within seven days.

If you’ve sent us crash reports or feedback, those records are anonymous (no email attached) but you can ask us to delete entries by approximate date in the same email.

Questions

Anything not covered here, or anything you want clarified, ask us at hello@audeeport.com or via the contact form.