SQUEEZEVID

Privacy

Last updated: 2026-10-17

Your videos

SqueezeVid never receives your videos. Files are opened, analyzed, re-encoded and saved entirely inside your browser using WebCodecs. There is no upload endpoint on this site: not a policy choice we could quietly change, but how the product is built. If you watch your network tab while compressing, you will see no video data leave your machine.

Filenames, file contents, thumbnails and metadata all stay on your device. Nothing about a specific video is stored by us anywhere, because it never reaches us.

What is collected

We use Vercel Web Analytics, which is cookieless, to count page views and understand which pages are useful. Alongside those page views, the site reports a small set of anonymous interaction events: that a file was opened (dropped or browsed for, and which size range it falls in — “25–100 MB”, never the actual number), that a target was picked, that a compression started, succeeded (which duration range it took), failed (one of a fixed list of reasons, such as target_too_small orencoder), or was canceled, that a download happened, and which links, sections and scroll depths a page saw.

Every value in those events is either a fixed word chosen in advance or a range, and a single module enforces that — it accepts no free text, so there is no path by which a filename could reach an event even by mistake. No filename, no duration, no file size, no text you typed, and no identifier of any kind is ever attached. They exist to answer questions like “do compressions fail more often on MOV input?” and “does anyone read past the tool?”, not to profile anyone — there is nothing in them that could single out one visitor or reconstruct what a video showed.

Cookies and accounts

There are no accounts, no logins, and no cookies set by us. Your settings live in the page while it is open and disappear when you close it. The site makes no requests to third-party domains: fonts are self-hosted, there are no ad or tracking scripts, and the analytics described above are served from this site’s own origin.

Hosting

The site is hosted by Vercel Inc., whose full address is on the legal notice. Like any web host, Vercel processes the technical data needed to deliver pages (your IP address and request headers in transient access logs) and computes the aggregate, cookieless statistics mentioned above on our behalf. We never see raw IP addresses or individual visitor profiles, only aggregate counts.

The legal detail, for completeness

Those page views and events are the only processing of personal data this site carries out, and they rest on the publisher’s legitimate interest (article 6(1)(f) GDPR) in knowing whether the pages are useful — an interest a counter that cannot identify anyone does not weigh against. Vercel keeps them for twelve months, the reporting window of the plan this site runs on.

Vercel processes them on the publisher’s behalf in the United States, under a data processing agreement. The transfer rests on two safeguards rather than one: Vercel is certified under the EU–U.S. Data Privacy Framework, and the same agreement incorporates the European Commission’s 2021 Standard Contractual Clauses (decision 2021/914, Module Two). A copy is published at vercel.com/legal/dpa.

Who runs this, and your rights

SqueezeVid is published and operated by Damien Yvert, an independent developer, who acts as the data controller for the little data described on this page. You can reach the operator at damienyvert.dev@gmail.com for any privacy question, including the access, rectification, erasure, restriction, portability and objection rights granted by the GDPR. His postal address and telephone number are on the legal notice. In practice there is usually nothing to retrieve or erase: we hold no account data and no content, and the usage events are anonymous aggregates that cannot be tied back to you. You also have the right to complain to a supervisory authority — the publisher being established in Portugal, the CNPD.

Questions

This page is deliberately short because the architecture does the heavy lifting: a tool that cannot see your files has very little privacy left to explain. If anything is unclear, write to the address above. Security reports are welcome too, via security.txt.