Does Cutroom upload my footage?

Not for the editing. The editing, transcription, and background removal all run on your own machine, so your source files stay on your disk. The exceptions are the AI features you turn on: image-to-video uploads the still you pass, and dubbing, voice isolation, voice change, and cloning upload the clip audio you choose, always to the provider whose key you brought. None of it ever routes through us.

What does the AI actually see?

A connected agent reads your frames and audio to do the edit and to check its own work, the same way you look at footage to cut it. That reading is part of the edit and is not stored by us or used to train anything. If you edit by hand, no AI reads anything.

When does anything leave my computer?

When you deliberately ask the AI to generate something, like an image, a video, or a voice. That request goes to the provider whose key you brought, on your own account. Image-to-video, dubbing, voice isolation, voice change, and cloning also upload the specific frame or clip audio you choose. It still never routes through us.

Where do my provider keys live?

On your machine. If you connect a generation provider for image, video, or voice, you paste your own key and it stays local. Cutroom is not a middleman for it.

Is there a Cutroom cloud tracking my projects?

No. Your projects, media, and edits live on your disk. There is no cloud project store watching what you make.

Can I use Cutroom fully offline?

Yes. The engines ship inside the app and are set up on first launch, so editing, transcription (Arabic and 90+ languages), captions, and cutout all run with no connection from the very first launch. You only need the network to connect an AI agent, run a generation, or install an even larger optional model. The core editing is fully local.

What can a connected AI do inside Cutroom?

A connected agent drives the app through its command layer, working on your Cutroom projects and a sandboxed asset library that is yours. It can keep more than one project going, editing one in the background while you work in another. It cannot read your keys, your secrets, or the licensing internals. It can trigger the same generation and upload steps you can, like image-to-video and the voice tools, always on your own provider key. Your provider key is never handed to a connected agent.

If I move to a new machine, what happens to my project?

Your project is one folder on your disk, and we keep no copy of it. Copy the whole folder to the new machine and your media travels inside it, because Cutroom copied it into the project and never touched your originals. Keep the folder together when you move it. If a clip ever loses its link, the file is still safe in the folder.

What does the licence check send, and what do you keep?

A one-way hash of your machine, plus the IP address and rough location (country and city) of each activation and check, which we keep for 180 days to catch a shared key. No footage, no audio, and no project data. Your licence is bound to your account with no cap on how many of your own machines, and the app keeps a small sealed marker locally to notice a clock wound back to dodge an expiry.

Can Cutroom be shut off remotely?

Yes, for piracy or a licence breach: a block or a revoke stops Cutroom at its next online check. Its reach is Cutroom only. It never touches your Delivvo account, your clients, your invoices, or your files. Tamper monitoring warns first and locks out only on a real, repeated pattern.

Is Cutroom private? Your footage stays on your disk

Your footage stayson your disk

Cutroom is built local-first. The cutting, the transcription, and the background removal all run on your own machine, so your footage is not bulk-uploaded to a server, ours or anyone else's. What does leave your PC is what you trigger: a generation request, or image-to-video and the voice tools, which upload the specific frame or clip audio you point them at, always to the provider whose key you brought. This page lays out exactly what stays and what moves, plus the licensing checks, what a connected AI can touch, and the one case where Cutroom can be locked out.

The AI reads frames to check its own work

When you connect an agent, it does read your frames and audio, because that is how it sees what it is editing and confirms a cut landed right. That reading happens as part of the edit, on your machine. It is not a training feed and it is not stored by us. If that honest exception matters to you, you can edit entirely by hand and no AI reads anything at all.

The agent reads frames and audio to do and check the edit

That happens locally, as part of the edit, not as a data feed to us

Edit by hand and nothing is read by any AI

What generation sendsGeneration goes to your own provider

Here is where bytes leave your PC: when you ask the AI to generate an image, a video, or a voice, or when you reach for image-to-video or the voice tools. Those go to the provider whose key you brought, on your own account, because that is where the model runs. They never route through us. Image-to-video uploads the still you pass, and dubbing, voice isolation, voice change, and cloning upload the clip audio you choose. Everything else stays put.

Only the generation and voice tools you invoke send anything out
It goes to your provider, on your key, never through us
Image-to-video and the voice tools upload the frame or clip audio you point them at

Where generation goes

Your footageStays local

TranscriptionStays local

GenerationYour provider

Moving machinesYour project is a folder, not a cloud account

Cutroom does not keep your work in a cloud you sign into. A project is a plain folder on your disk, and the edit needs nothing outside it: the media you imported, the fast proxies, anything the AI generated, and the edit list all sit inside that one folder. When you import a clip, Cutroom copies it into the project rather than pointing at wherever it came from, and it never changes your originals. Moving to another machine is a copy, not an upload: bring the whole folder across and your media travels inside it. Nothing about the move goes through us.

If the app is tampered withA modified copy can be locked out

Cutroom watches whether its own code has been changed, and it reports that, not your footage. A single odd signal only raises a warning and you keep editing; it takes a real, repeated pattern for a build to lock itself. Because this is a paid app with no per-device limit, we can also block a Cutroom account outright if a licence is pirated, resold, or charged back. A block or a revoke stops Cutroom at its next online check, and that is the whole reach of it: it never touches your Delivvo account, your clients, your invoices, or the files already on your disk. If you think a block is a mistake, open a support request and a person will look.

The app reports whether its own code was modified, never anything about your footage
One stray signal only warns; a build locks out only on a real, repeated pattern
A remote block or revoke stops Cutroom only, never your Delivvo account or your files

Lockout is about the licence, not your work.

Even if Cutroom is ever blocked on your account, your footage, projects, and exports stay on your disk, untouched, and your Delivvo account, clients, and invoices keep working. Cutroom and Delivvo are billed and locked separately on purpose.

Your footage stayson your disk

The work happens on your machine

The AI reads frames to check its own work

More on this

What generation sendsGeneration goes to your own provider

Moving machinesYour project is a folder, not a cloud account

Questions about privacy

Keep your footage yours

LicensingWhat the licence check actually sends

If the app is tampered withA modified copy can be locked out