Skip to content

Privacy Policy

Last updated: 8 August 2026

The short version

Audiowire does not collect, store, transmit or sell any personal data. There is no account, no analytics SDK, no advertising identifier, no crash-report upload and no telemetry. The application has no network code at all, and licences verify offline, so it does not phone home even to check whether you paid.

That is the easy half. The half that matters more is what the software can do on your own machine, and it is a lot.

What this software can do, stated plainly

You should know all of this before you capture anything, and you should not have to find it in a licence agreement:

  • It can record the audio of other applications on this computer, individually and by name, including applications you did not start and are not looking at.
  • It can record system audio in aggregate, which includes anything played by any application, any browser tab, and any notification.
  • It can record hardware inputs, including the built-in microphone, and mix them with application audio.
  • It creates audio devices that other applications can see and select. A device Audiowire creates is a normal system audio device: anything routed into one is available to anything that can open that device.
  • It keeps a record of which applications you route audio from, on disk, in your routing graph, by absolute executable path, until you delete it.
  • On macOS, the system asks you once for audio-capture permission and you can revoke it in System Settings.
  • On Linux, any application in your session can already do all of the above to you, with or without Audiowire, and the operating system will not tell you.

What we commit to never doing

These are commitments the code is meant to be auditable against, not marketing copy. The repository is public; check them.

  1. No audio leaves the machine. No network code, no telemetry containing audio, no cloud processing, no “help us improve” upload — ever, under any flag. If a feature ever needs the network it ships as a separate process with its own consent.
  2. No capture without a visible indicator. Whenever an application source is enabled, the interface shows what is being captured, and that indicator cannot be dismissed or hidden. Hiding a device from OS pickers to reduce clutter is a feature; hiding a capture from Audiowire’s own window never will be.
  3. No headless capture. No flag, no config key and no “start minimised and record” affordance that begins capturing before you have seen the indicator at least once for that configuration.
  4. No content inspection. Audiowire moves samples. It does not transcribe, fingerprint, classify, detect keywords or derive anything from audio content — not locally, not optionally, not behind a flag.
  5. No collection of your application list. The running-application list exists so you can pick one. It is never persisted beyond your own routing graph, never logged, never sent anywhere and never included in a report.
  6. We will not build the covert-recording feature. Requests to make capture invisible, suppress the indicator, or hide Audiowire’s devices from the person using the machine get declined.

The uncomfortable version, said out loud: the legitimate use of this product (podcasting, streaming, teaching) and its illegitimate use (recording a colleague’s call without telling them) are the same feature. The only thing separating them is whether the person at the keyboard knows what is being recorded — which is why points 2 and 3 are not negotiable interface preferences.

Data processed on your device

Your routing graph (device names, the sources you added, wiring and gain), level-meter values while the app is open, and the list of audio applications currently running so you can choose one. All of it stays in your own configuration directory, owned by you. Deleting the configuration directory removes all of it.

Permissions, and why each is needed

Audio capture (macOS) — required for per-app capture via Core Audio process taps; asked for once, revocable in System Settings. Administrator, once, at install — the virtual device is a driver, and drivers install into locations only an administrator can write. The background service itself never runs as root and is designed so that it cannot ask to. Details: docs/privilege-model.md.

This website

This site is static. It sets no cookies, runs no analytics and embeds no third-party scripts or fonts loaded at runtime. The email form on the home page is not connected to a mailing list yet and stores nothing; when it is connected it will be double opt-in, and this page will say so before it goes live.

Payments

Nothing can be bought yet. When checkout opens, a merchant of record will process the transaction and receive your billing details directly under their own privacy policy. We would receive only your email address and an order reference, used to issue your licence and provide support.

Children

Audiowire is not directed at children and collects no data from anyone, including children under 13.

Contact