Fonyx
Fonyx has no account, no telemetry and no server of its own. This page covers the application first and this website second. The left column is the short answer; the right is the detail.
Last updated 6 October 2026, for version 0.1.0.
Fonyx works on the sound your applications send to your speakers. That audio is processed in memory and passed straight on to your output devices. It is not kept, analysed for content, or sent anywhere.
It does not open your microphone. The small level meters beside each app read that app's own output, and are marked so your desktop doesn't mistake them for microphone use.
A recording is a WAV or FLAC file written to the path you choose, on your disk, with your user's permissions. Fonyx never starts one by itself.
Everything Fonyx remembers is in ~/.config/fonyx/:
config.toml: your groups and their settings, scenes, rules, and which app belongs in which group.aliases.toml: short names you have made for the command line.To recognise an app or a device next time, the file stores the app's name or id and an identifier for each output. For some devices that identifier is a serial number or a Bluetooth address. A rule you write for a particular website stores that site's name.
The desktop app also keeps a few interface choices, such as mutes, fader links, your own EQ presets and the theme, in its window's local storage.
The mixer service and the command line contain no networking code. They talk to PipeWire and to each other on your machine, and that is all.
The exception is the desktop app's window. When it opens, it loads two typefaces, Inter and JetBrains Mono, from Google Fonts. That request tells Google your IP address and that a page asked for those fonts. Offline, or with fonts.googleapis.com and fonts.gstatic.com blocked, the app falls back to your system fonts and works the same.
Fonyx is controlled over the desktop's session bus, like most Linux desktop services, and adds no password of its own. Any program already running under your user account can read the mixer's state, change routing, or start a recording. Programs running as other users cannot.
When run as a service, Fonyx writes diagnostic messages to your user's systemd journal. They can include the names of apps and groups. Nothing collects them from your machine.
Delete ~/.config/fonyx/ and any recordings you made. There is nothing held anywhere else to ask for or to erase.
These pages set no cookies and store nothing in your browser. They contain no analytics, advertising or social-media scripts, and no forms.
The demo on the home page plays songs that come with the site. On a computer, in Chrome or Edge, it can also take the sound of a browser tab you pick in your browser's own sharing prompt. Either way the audio is processed inside your browser and played back to you. It is not uploaded, recorded or kept, and pressing Stop clears everything the song was using.
The demo never asks for your microphone. Your browser shows a sharing indicator for as long as a tab is shared, and you can end it there at any time.
The typefaces and the 3D desk are served from the same place as the page itself. Your browser contacts no other company to display it.
Whoever serves these pages receives your IP address and browser details with each request, as every web server does, and may keep them in access logs. Fonyx's author does nothing further with them.
The source code, documentation and issue tracker are on GitHub, which has its own privacy policy. To ask a question about anything on this page, open an issue there.