Skip to content

Privacy Policy

systemBlue edited this page Jun 11, 2026 · 1 revision

Privacy

DeadCat runs entirely on your machine and sends no data off it.

What DeadCat collects

DeadCat collects nothing. The servers and the terminal command have no telemetry, no analytics, no accounts, and no network calls beyond the OSC messages they exchange with your DAW.

This documentation site is static pages with no analytics; your browser stores only the theme preference.

Where your data goes

deadcat-reaper runs on your machine and talks to REAPER on your machine, over UDP on the loopback interface by default (control to port 8000, feedback from port 9001). The data in those messages is DAW state: transport flags, track names, fader and pan values, tempo, marker numbers, and the file paths you ask it to insert. None of it leaves the machine unless you point --host at another machine yourself.

Your conversation with an assistant belongs to the MCP client you run DeadCat in, not to DeadCat. The server sees only the tool calls the client sends it and answers only with DAW state. What the client does with the conversation is governed by that client's own privacy policy.

What DeadCat stores

The server keeps REAPER's last reported state in memory while it runs, to answer the read tools, and forgets it on exit. The media bridge writes one request line to /tmp/deadcat-bridge/request.tsv and reads REAPER's answer from /tmp/deadcat-bridge/response.txt; both contain only the file path, track, and position of the insert, and macOS clears them when it clears the temporary directory. DeadCat writes no other files, no logs, and no configuration.

What DeadCat reads

reaper_insert_media reads only the audio file paths you name, checks they exist and carry an audio extension, and hands them to REAPER. No other tool touches the filesystem.

Retention and sharing

DeadCat retains nothing between runs and shares nothing with anyone, including us. There is no server side.

DeadCat is built by systemBlue, an indie Swift studio. This page changes only with a release, and the changelog records when it does.

Clone this wiki locally