What is sent

Anonymous usage and error data, so it is possible to tell which parts of the app people actually use and what is breaking on machines other than ours. It is a short list, and it is deliberately dull:

Which screens you open, and how long things take
How many samples a scan covered, and where the time went (decoding, analysis, saving)
Whether an export succeeded, and to which format
Errors and crashes, with the technical stack trace
App version, operating system, processor type and language
How many processor cores your machine has, as a rough band (for example “8” or “10”–12”) rather than the exact number — so we can tell whether a scan that took ten minutes was slow software or an older machine
How long your first library scan took, and how many samples it covered
A random ID for this installation — a number with nothing attached to it, so two visits can be counted as one person rather than two
The country and city your connection comes from, worked out from your IP address by our hosting provider. The IP address itself is not stored

What is never sent

File names, folder names, or any path on your disk
Your audio — no sample, recording or export ever leaves your machine
What you type into the chain builder
The contents of your library, or anything derived from it that could identify a file
Your IP address — it is used to work out a country and then discarded
Your name, address, or anything that identifies you personally
Your exact processor core count, machine name, serial number, MAC address or screen size — nothing that would let one machine be recognised as a machine

This is a rule in the code, not a promise in a document: the event definitions that the app is allowed to send are declared in one file, and none of them has a field for a path, a file name, or prompt text.

The installation ID

When you first open WeaveTone it generates a random ID and keeps it in a file on your machine. It is not derived from anything — not your computer’s serial number, not your username, not your network hardware — and it is not linked to your email address unless you give us one. Its only job is to let us count peoplerather than launches: without it, one person opening the app on Monday and Tuesday looks identical to two different people. Deleting the app’s data folder erases it, and the next launch generates a new one.

Turning it off

Open Settings → Privacy in the app and switch off “Share anonymous usage data”. It takes effect immediately — analytics, session recording and crash reporting all stop, and the choice is remembered, so nothing is sent during startup on later launches either.

Session recording

A share of app sessions is recorded as a replay of the interface, which is how it is possible to see where someone got stuck without asking them to write it up. All text is masked before the recording leaves your machine — file names, folder trees and the contents of your library are obscured in the recording itself, not filtered out later. Recording follows the same switch as everything else, and stops the moment you turn it off.

This website

The site measures which sections people read and which buttons they press, so the page can be made to explain the product better. It sets no cookies and does not track you between visits — which is also why there is no cookie banner. If you give us an email address for early access, it is used to email you about WeaveTone and nothing else, and it is never sold or shared.

Who processes it

Two services, both acting on our behalf: PostHog for anonymous product analytics and session recording, and Sentry for crash and error reports. No data is sold, and there is no advertising on this site or in the app.

Questions, or a request to delete

Email hello@weavetone.com. If you want the anonymous data associated with your installation removed, say so and it will be — though be aware there is nothing in it that identifies you, which is rather the point.