Private beta. Founding applications are open.

Eddy docs

What leaves your Mac

What stays on your Mac, what goes to your AI provider, and what reaches the Eddy team.

This page explains the app's behaviour in plain words. The privacy policy is the formal version, and it wins if the two ever differ.

Stays on your Mac

Goes to your AI provider

To edit, Eddy sends the transcript, other relevant text and a few selected frames to ChatGPT or Claude, through your own account. That provider's terms apply to what it receives.

For scene labels, you can also let ChatGPT or Claude look at a few still frames. That is off unless you turn it on for a project.

If you connect ChatGPT or Claude as an agent (see For AI agents), that agent also receives what its Eddy tools return, such as the transcript, frames of your edit and file names. That provider's terms apply to it too.

Reaches the Eddy team

Anonymous usage, on by default. The app sends the team anonymous usage events and a masked screen replay of the app window. The events say which buttons and screens you use, how long each step takes, which tools Eddy ran and whether they worked. In the replay your video, pictures, words and file names are blanked out. It never sends your footage, audio, transcript, chat or file names. It goes to PostHog's US cloud under a random id, not your name or email. Turn off Send anonymous usage in the Doctor sheet and it stops at once.

Everything else, only when you choose to send it:

Feedback notes and support reports are cleaned first: your home folder path, user name, email addresses and keys are removed. Crash reports are different: they are the app's crash dumps, sent as they are, and can include bits of the app's memory such as a file name.

Notes and reports are stored privately for the team. Besides the team reading them, automated AI runs sort them into the team's private task list.

Other connections

Written from the app's source code and last checked against it on 3 November 2026. Tables marked as generated are rebuilt from the source every time, and the build stops if a page disagrees with the app. Not every behaviour here has been hand-tested in the beta build. Something wrong or missing? Email support@eddystudio.ai.