Everything stays on your computer

Your music is never uploaded. There are no WavRead servers to upload it to, no account inside the app, and no telemetry. This page lists every request the app can make, so the claim can be checked rather than trusted.

What WavRead never does

No uploads

Audio, stems, documents and measurements stay in a folder on your machine.

No app account

The desktop app has no sign-in, licence server, email address, or tester identity.

No silent telemetry

No analytics, no usage counters, no identifier. Problem reports are off until you turn them on, and readable before they go.

No background activity

WavRead does nothing while you are not using it, beyond one daily version check you can switch off.

Every request the app can make

The app can make the requests listed below. Analysis stays local. Update checks and model downloads carry no filenames or measurements; optional linking and reports carry the data described here.

Update check	Once a day, one request to wavread.com, asking only what the newest published version is. It has no body and no identifier — the only thing it says about your computer is whether it runs Windows or macOS, so that it hears about the right build — fails silently when you are offline, and is switched off for good in Settings if you would rather it never ran.
Installing an update	Only when you press Update now, and only for a build that is published openly: the download itself is checked against the checksum the catalog carries. The current build is behind your account, so WavRead tells you a newer version exists and sends you to your account to fetch it. Nothing installs on its own.
Lyric transcription model	About 460 MB, fetched once from its publisher the first time you transcribe lyrics, then cached. Skip lyrics and it is never downloaded.
Problem reports (off by default)	Only with reports turned on in Settings: a crash record or a report you wrote, sent to WavRead's report service. Contents are listed in full below; every record is kept on your machine and readable before and after sending. Turn reports off and this request never exists.
Linking a device (optional)	Only when you type a link code from your dashboard into Settings: one request that trades the code for a report token, so your reports show up on your own dashboard. The app never holds your email or a sign-in — only that token, revocable from either side.

The lyric model is a download of software, not an upload of your audio: the model comes to your machine and runs there. Everything else — measurement, structure, chords, melody, the whole Feedback Report — needs no connection at all, and the app runs normally with the network off.

Melody transcription needs no download: that model ships inside the app.

Where your files are

One folder holds everything: analyses, documents, stems and copies of the audio you analyzed. Settings shows you the exact path, how large it is, and how much room is left on that drive — and moves the whole library somewhere else if you want, copying first and removing the original only once the copy is complete.

You can delete any part of it from inside the app, or in Finder. WavRead keeps no second copy anywhere, and nothing is retained after you delete it.

What is in a document

Track Documents contain measurements, structure, estimated chords and lyrics, and your own notes — no audio. If you paste one into an AI assistant, that is your decision and your assistant's privacy policy; WavRead never sends a document anywhere itself. Nothing in the app requires an AI at all.

From 1.5.6 the app carries a helper for AI assistants. The app does not show it anywhere, and it does nothing until you add it to an assistant yourself. Once you do, the assistant can ask WavRead to analyze files, read measurements, rename tracks, change settings and delete things. The helper and the app talk only on your computer, and audio is never sent. What each request returns (measurements, track names, document text and your notes) goes into the assistant's conversation, under that assistant's privacy policy. The app answers only requests from your own computer, and refuses changes that come from other web pages open in your browser.

Problem reports, in full

From 1.4.37, WavRead can report its own failures — a crash, an analysis that died, an update that would not install. Reporting is off until you turn it on in Settings, and three things stay true whichever way the switch points:

Every record is written to your machine first, into the library folder where you can read it, and stays there whether or not it is ever sent. Settings shows each record and whether it went.
A report is scrubbed before it exists. Your username becomes ~, audio filenames become <audio>, and library paths are shortened to their role. A report never contains audio, track names, measurements, documents, or lyrics.
What is sent is exactly: the app version, operating-system version and chip type, the kind of failure, the scrubbed error summary and stack trace, when it happened, and a random install ID that identifies the install — not you. With a linked device it also carries the report token, so the report appears on your dashboard.

A report you write yourself on the Report a Problem page additionally contains what you typed, and — only if you tick the box — a scrubbed excerpt of WavRead's own error log, shown to you in full before sending.

To stop one sender flooding the report service, it counts crash reports per network address using a keyed hash of the request IP address. Each count expires within the hour and is removed on a later request. Raw IP addresses are not stored, and nothing in the report itself changes.

The Windows notification list

Before the Windows build shipped, this site offered to notify people when it did. That form is gone. The addresses it collected — email, the request itself, whether news and offers were separately asked for, the wording version of that choice, and the signup date — are kept in a private database until each person has been told once that Windows is available, and are deleted after that. Nobody on the list has been emailed yet. To be removed now, write to support@wavread.com.

Optional accounts on this website

Owners may sign in to a separate area on this website. That account is not used by the desktop app and never receives audio, filenames, analyses, documents, or app activity. The account service stores a WavRead-owned account ID, account email, join date, status, future complimentary-release eligibility, purchases, entitlements, linked-device records, and the reports and feedback described above. Feedback may include the selected feedback type, title, description, optional reproduction steps, app version, operating-system name, and whether follow-up is allowed.

Attachments on feedback. A report can carry up to two files — screenshots or short clips, 25 MB each — whether you write it on your dashboard or in WavRead itself. This used to say the desktop app never sends a file of any kind. That changed: the app can attach a picture now, and this paragraph changed with it rather than after someone noticed. Either way only the files you picked yourself are uploaded, and only when you send the report; nothing is gathered from your machine, and nothing is attached without you choosing it. Audio cannot be attached at all — not by the form, not by the app, and not by the service behind them, which refuses the type and stores it in a bucket that refuses it again. An attachment is stored privately against the report it belongs to, is readable only by WavRead, and is deleted when that report is. The claim on the front of this site — that your music stays on your computer — covers analysis, and is the reason audio is the one thing an attachment may never be.

A $50 purchase is processed by Stripe on Stripe's own pages; WavRead never sees or stores card numbers. WavRead keeps the purchase record — your email, the amount, the date, and Stripe's checkout reference — because that record is what makes the purchase yours across devices and years. Stripe's own processing is governed by Stripe's privacy policy.

If you reached the purchase page from an advertisement, its link carries a short campaign label — reels-a and the like. The label says which advertisement was clicked, not who clicked it: it is read from the address you arrived on, carried in links between public pages and checkout, sent once with the purchase, and kept alongside the purchase record so WavRead can tell which advertisements are worth paying for. It is not an identifier, it is never combined with anything else, nothing is stored in your browser to carry it, and arriving without one changes nothing about the purchase or the price.

Access, ownership, and reports are protected by account ownership and database policies. Removing the sign-in-provider account disconnects access but does not erase the stable account record, its purchases, or its reports, because that history is what future eligibility is honored from. A deletion request can still be handled by WavRead directly. The public product website uses no analytics or advertising trackers.

Last checked against WavRead 1.5.6. The model download size is the actual size on disk after a first run: 464 MB for lyric transcription. WavRead no longer ships or fetches a separation model at all — stems come from you, from your DAW, or from a tool you configure yourself.