Home Privacy and updates Privacy, error reports and diagnostics

Privacy, error reports and diagnostics

Last updated on Nov 14, 2026

Solco analyses your music on your computer. Your music files, library, playlists and analysis are never uploaded unless you choose to send a file in Feedback. This page lists everything Solco does send. The full legal notice is the app privacy notice.

Error and crash reports

Error and crash reports are how problems get fixed. A report holds the error, what led up to it, and details about the app version, operating system, graphics and analysis. It can name tracks and parts of file paths, with your user folder's name replaced by ~. It never includes your music, your library or your credentials. It carries your licence ID, so we can get in touch if we need to ask about a problem. We use it only for that. A crash can also send a small memory snapshot of the app.

Reporting is on by default, and you can opt out. Untick Send error reports on the first screen, or turn it off any time in Settings › About. A choice you already saved is kept when you update Solco or enter a new licence key. With it on, reports go as they happen, errors that are not crashes included: every problem Solco shows you, such as a track it couldn't analyse, a file a scan couldn't read or a tag it couldn't save, with the name of one file it happened to.

With it off, Solco asks first. After a crash it keeps the report on your computer, and the next time it starts it asks whether to send it: Send, Always send or Don't send. Nothing is sent until you answer, and Don't send deletes the report. Always send turns Send error reports on. Otherwise only the crash reports you agree to are sent.

A report that can't go straight away, because you're offline or the server is down, is kept and sent the next time Solco starts. Solco keeps at most 20 of them, 32 MB in all, for 30 days, and at most the last five crash reports waiting for your answer.

Reports go to Solco's own error tracker at errors.plenty.is, on our server in Nuremberg, Germany. No third party receives them.

Your licence key

During the private beta Solco works only with a licence key issued to you. Activating it needs the internet once: Solco sends the key, its random installation code (which identifies this copy of Solco, not you) and a computer code to Solco's server, which records that the key is in use on this computer and when it was activated. That is how we know how many people use the beta and can limit a key to three computers. The computer code is how the server recognises this computer when you reinstall Solco, so it does not count twice. Solco makes it on your computer by scrambling the identifier your operating system gives this installation of the system together with your licence, in a way that cannot be undone: the identifier itself never leaves your computer, and the code is different for every licence, so it says nothing about your computer outside your licence, not even to another licence on the same computer. Solco's server keeps your email address, the key's dates and, for each computer, its installation code, a scrambled copy of its computer code and its activation date; when the Solco team frees a computer for you, its record is deleted. After activation Solco checks the key on your computer. While your licence is active, Solco also asks the server for a renewed key when it starts and with each update check, sending exactly what activation sends and nothing more; the server keeps only the key's new dates. See "The private beta and your licence key".

Update checks

With Check for updates on (it is on by default), Solco checks for a newer version when it starts and then every few hours. It asks Solco's server at api.getsolco.com first, saying which version, release channel (private beta or stable), operating system and processor it is, since that is what decides which update fits. The server answers with the list of releases from GitHub and counts the check: it keeps only how many checks came in each day for each version, channel, system and processor. That is how we know how many people use each version. It stores no IP address, no installation ID and nothing that tells one person or computer from another. If Solco's server doesn't answer, Solco asks GitHub directly. Downloads always come from GitHub. With each check Solco also downloads the Solco team's signed list of revoked licence keys from the same server. That request sends nothing about you, your computer or your key: everyone gets the same list.

Turn Check for updates off in Settings › About and Solco makes no update requests at all, and isn't counted. See "Updating Solco".

Settings, About: the version with About this beta, Check for updates and Install updates automatically both on, Keep running in the background, Send error reports, the keyboard shortcuts, the Help centre link and Report a problem

Tag and cover lookups

Lookups run only when you start them. Solco asks Solco Vault first: Solco's own catalogue service at vault.getsolco.com, on our server in Nuremberg, Germany. Each request carries your licence key, so Solco Vault can check it, and your Solco version. For each track, up to 20 in a request, it carries the track's tags, its length, an audio fingerprint (a short code computed from the sound, never the audio itself) or what that fingerprint matched, a search you changed, the file's own name and Solco's own number for the track. Never its folders, and never the audio.

Requests to Solco Vault pass through Cloudflare, which decrypts them, so it sees your IP address, your licence key and those track details. We can't promise what Cloudflare logs. Solco Vault itself writes your lookups, your licence key and your IP address to no log and no database, and counts your requests only in memory, for its limits. If a request fails unexpectedly, it sends our error tracker the error and its message, without the request's content, your licence key or your IP address. Solco Vault matches fingerprints against its own copy of AcoustID's open data, on the same server, so it sends them nowhere else and keeps none of them.

Your computer asks MusicBrainz, AcoustID and Discogs directly, sending search details such as artist, title or a fingerprint, when Solco Vault doesn't answer or you turned it off, for a track Solco Vault doesn't know or can't answer for, for a search you changed and for Look up again. If you saved an AcoustID key and Solco Vault can't match fingerprints, your computer asks AcoustID first and sends Solco Vault the results in place of the fingerprints. Covers never go through Solco Vault: they come straight from the Cover Art Archive, and from Discogs when Solco asks it directly. Keys you save in Settings › Tags & covers stay on your computer, outside your library. To turn Solco Vault off, untick Use beside it on the same page.

Playlist assistant

The playlist assistant is optional and runs on Solco's own service. It sends nothing until you send it a message, and a line under the message box says what goes. Each request sends what you type and the recent conversation. While it plans, the assistant looks things up in your library, and Solco answers on your computer: how many tracks you have of each genre and style and how their tempo, key, energy and Feel spread, and samples of the tracks that match what it searched for or put in the plan, a few dozen at a time. For each of those tracks Solco sends what you see in the track list and can search in a Smart Playlist: title, artist, genre, style, BPM, key, energy, Feel and the other characteristics, rating and colour. A file without a title tag goes by its file name, as in the track list. It never sends audio, file paths, folders, albums, comments, cues or your playlists, though anything you type is sent. When you ask about one of your playlists, it looks it up by name: Solco sends the names, folders, sizes and lengths of the playlists that match the words it searched for, and for the playlist it reads, its tracks in order, each track's length and a Smart Playlist's rules. Planning a new night sends no playlist names. The message box shows how many of your tracks have been shared in this conversation. Solco's service passes it to the providers that run the assistant, named in the app privacy notice, and keeps no copy of the conversation unless a request fails unexpectedly. To share nothing, don't send the assistant a message: nothing else in Solco needs it.

The assistant is automated, and its suggestions can be wrong. It is part of the private beta, and your licence key turns it on; an invite code you already have still works under Connection. The plans it suggests are checked on your computer, and nothing is added to your library until you create the folder. See "Planning a gig with the assistant".

Feedback

Messages you write in Feedback leave your computer only when you send them. They go, with your Solco version, operating system and processor type, to the Solco team's support system, which we run ourselves at support.plenty.is on our server in Nuremberg, Germany. Feedback comes from your licence, so it is never anonymous: the first time you write, Solco sends your licence's ID to Solco's server, which opens your conversation in the support system with the email address your licence was issued to. Solco itself never sends your email address, and Solco's server keeps nothing new about you; the support system keeps your email address with your conversation. The diagnostic attachment includes a short recent log and is sent only if you add it. Read it shows the exact text first. Logs can name tracks and files, with your home folder’s name and recognised credentials removed. Tell us selects this attachment for you; you can untick it before sending. The conversation stays in the support system until it is deleted. After you write, and while the Feedback panel is open, Solco keeps a connection to the support system for up to a week so replies arrive at once; it sends only the code the support system gave your conversation, and the team may briefly see you as online when it connects. The chat on this help centre goes to the same support system, with the email address and name you give it.

Local logs

Solco keeps small local logs of activity and errors, up to 8 MB in total, replacing older files automatically. Settings › About › Logs › Show folder opens their folder so you can review and share a file yourself. They can name tracks and files, with your home folder’s name and recognised credentials removed. Recording a log or opening its folder does not upload it. Automatic error reports keep their separate setting.

Diagnostic reports

A report from Settings › About › Report a problem is made on your computer and never uploaded by Solco. You read it, then copy or save it yourself. See "Contacting the Solco team".

Your data

To ask what we hold about you, or to have it deleted, write to hello@getsolco.com, as the app privacy notice explains.