What 'free online video editor' usually costs
The standard architecture behind that search result: you upload the footage, it sits in a queue, a server renders the edit, you download the result, and a copy lives on infrastructure you'll never see, governed by a retention policy you didn't read. For a clip of your lunch, fine. For anything sensitive, the upload leg is the entire problem, and no privacy policy fixes it, because the policy governs a copy that now exists.
This editor can't upload footage. Not won't. Can't.
This is a private video editor with no upload in the architectural sense, not the marketing sense. Decoding the video, every cut and crop, and encoding the export all execute in the page, on your hardware. There is no server-side render pipeline, so there is nothing to send footage to.
On top of that, the page's Content Security Policy pins its connect-src to the site itself, so the browser refuses to let page scripts send data out through fetch, XHR, WebSockets, or beacons. Full disclosure on what the page does load: ads and a cookieless, self-hosted visit counter, the things that keep it free, neither of which can read your footage. A promise is a sentence in a policy document; the CSP is a rule your browser applies on every load.
The wifi test, which you should actually run
Load the page. Turn the wifi off. Load a clip, cut it, caption it, export it. Everything works, because nothing was ever making a round trip. A tool with a server in the loop becomes a spinner the moment the network drops; this one doesn't notice. Run the test once for peace of mind, or edit on airplane mode permanently. It costs nothing either way.
Footage that should never touch third-party infrastructure
- Unreleased product demos. The feature is embargoed; a converter's server shouldn't be the first place it ships.
- Internal tools and dashboards. Screen captures of admin panels tend to be full of customer data around the edges.
- Your kids. Family footage has no business in an anonymous processing queue.
- HR, legal, and incident material. Chain of custody gets much simpler when the file never leaves the machine.
- Anything under NDA. 'We ran it through a free web editor' is a sentence nobody wants to say to counsel.
For sensitive screen captures specifically, the screen recording page covers the capture side of the same discipline.
Scope, stated plainly
The output is silent, always: a GIF, an APNG, or a muted MP4, aimed at short-form work. Within that scope the editing is genuine: sequence multiple clips, trim with frame accuracy, split at the playhead, crop to exact ratios, change speed, add captions and shape overlays, undo freely, and save the project as a local .wtg file on your own disk, not a cloud doc.
If the sensitive footage needs its audio or an hour-long timeline, use an installed desktop editor; software running locally keeps files local too. The trap this page exists to flag is narrower and very common: the free web editor whose first step is taking your footage. The private converter page applies the same architecture to straight conversion, and the editor itself lives at the tool.