Privacy

edytlab is a local-first desktop application. This page describes what data the app handles and how it handles it. It is intentionally short because the app is intentionally simple: we do not operate servers, we do not collect telemetry, and we do not handle your audio.

Audio files

Every audio file you load is decoded, processed, and rendered on your machine. Stem separation, transcription, mixing, and rendering all run locally in the desktop app. We do not upload, copy, mirror, or otherwise transmit your audio. There are no “cloud projects” and there is no server-side processing.

LLM API keys

edytlab supports multiple LLM providers (Anthropic, OpenRouter, OpenAI). When you add an API key, it is stored in your operating system's secure credential store: macOS Keychain on Mac and Credential Manager on Windows. Keys are never written to plain-text files and never sent anywhere except directly to the provider whose key it is.

Network traffic

The only outbound network traffic the app makes during normal use is chat requests to the LLM provider you have selected. These requests contain your prompt text, agent context, and tool-call results — never your raw audio. You can inspect the full set of requests in your OS network tools at any time.

Telemetry and analytics

There is none. The desktop app does not send usage analytics. The marketing website you are reading does not run Google Analytics, Plausible, Mixpanel, Segment, or any other analytics or tracking provider, and sets no analytics cookies.

Crash reports

Future builds may include opt-in crash reporting for stability debugging. If we add it, it will be off by default, surfaced in settings, and limited to stack traces with no user content attached.

Updates

The app may check for new releases. This check fetches a small JSON manifest from the public release host. No identifying information is sent.

Contact

Questions about this policy can be raised as an issue in the public GitHub repository.