--- title: "Privacy: Your Footage Stays Put | stabilize.video" description: "How stabilize.video handles data: shaky clips are measured, steadied and saved in your own browser, nothing is uploaded, and analytics can be switched off." url: https://stabilize.video/privacy --- # Privacy at stabilize.video Last updated: 8 November 2026 ## In brief Stabilising happens on your own device, so your footage stays there. We see three kinds of information, all small: visit statistics (which you can turn off), the rating card’s answers when you choose to give one, and technical reports when something in our code breaks. ## The clips you open Opening a video hands it to this page, inside your browser tab. Everything after that runs there too: decoding frames, following the camera’s movement from one frame to the next, working out a calmer path, redrawing every frame on your graphics chip and encoding the new file. We run no server that could accept your video, so none of it, nor its sound, its metadata or anything measured from it, reaches us. ## Stored in this browser, and nowhere else * **Projects.** So that a refresh or a closed tab doesn’t cost you your work, each clip you open becomes a project kept by your browser. A copy of the video goes into the browser’s private file storage for this site (the Origin Private File System, or IndexedDB where that isn’t available), and the studio’s settings and a small picture for the list go into an IndexedDB database called `vt-projects`. A small count in local storage lets the home page offer “Continue where you left off” straight away, and if a tab closes before the latest change is saved, that change waits in local storage until the project next opens. [Your projects page](https://stabilize.video/app) lists them and can delete any of them. Ten are kept, and the oldest are dropped first if space gets tight. * **The motion analysis.** The camera movement the studio measures from your clip (the points it followed and the path they traced) is saved with the project, in the same private file storage, so reopening the project doesn’t measure the whole clip again. It is deleted with the project. * **Large exports.** A long or high-resolution export is written straight into that private file storage while it is made, instead of being held in memory, and**Download** saves it from there. Shorter exports never touch storage. A cancelled or failed export is deleted at once, and each time a new large export starts, older ones are deleted except the one before it, so at most your last two large exports are kept on the device. * **Preferences,** in local storage: light or dark theme (`vt-theme`), whether the studio has shown you its first tips, whether you paused the demo at the top of the page or turned down the offer to install the site as an app, your choice about analytics (`vt-consent`) and the rating card’s timing (`vt-feedback`). All of this stays on your device: none of it is uploaded, and we never receive any of it. To wipe it all, clear this site’s data from your browser’s settings. ## When a file needs converting Some formats (an old camcorder’s MTS, an AVI or a WMV, say) can’t be read by browsers directly. For those, the page downloads ffmpeg.wasm, an open-source converter of about 10 MB that we host on stabilize.video, and runs it on your device to make a copy your browser can play. That download happens only when such a file is opened, and it carries nothing of yours. ## Hosting by Cloudflare Pages reach you through Cloudflare. Like any web host, its servers see your IP address, browser and the page requested while delivering it and screening out attacks. We use that for nothing beyond keeping stabilize.video up and safe, on the basis of legitimate interests (Article 6(1)(f) of the UK GDPR). How Cloudflare handles those logs is set out in[its privacy policy](https://www.cloudflare.com/privacypolicy/). ## The rating card Once you’ve downloaded or shared a stabilised clip, a small card may ask you to rate the site from one to five stars; ignoring it is fine. Four or five stars bring a thank-you, a Share option and a link to Trustpilot, which is a separate company (we pass it nothing when you follow the link). One to three stars let you pick what went wrong and, if you want, add a few words, ideally without anything personal in them. What we save with each answer: * the stars, the reason picked and any note; * whether Trustpilot or Share was tapped, and which action brought the card up; * the page’s path, with any project id hidden, and the site’s version; * a country code worked out from the connection; * browser family, operating-system family, and phone, tablet or computer. No cookie or identifier links answers to you, and they contain nothing from your footage. Your IP address is checked for a moment to block abuse, then dropped. Answers are erased within 24 months. In `vt-feedback` your browser notes when you last answered or dismissed the card, so it waits 180 days after a rating and 21 days after a dismissal, and never returns after three dismissals. Google Analytics is told the number of stars and the reason chosen; the note never goes there. ## Error reports If our code fails unexpectedly, your browser sends us a report so we can fix it. It holds the error message, the place in our scripts where it occurred, the page’s path, the site version, a random id used for that single page view, your browser, system and kind of device, and your country. Before it leaves, addresses are trimmed and anything resembling an email address or a file name is stripped, so it never includes your video or anything you entered. Each report is deleted after 30 days; a short summary of each distinct fault stays until 180 days after it was last seen. Google Analytics gets one `js_error` event that names just the type of error. Ratings and error reports are kept on Cloudflare Workers and Durable Objects, which act on our behalf. We rely on legitimate interests (keeping the stabiliser working and making it better), and for a written note on your decision to send it. The section on your rights below explains how to object or ask for deletion. ## Counting visits Two cookieless services,[Cloudflare Web Analytics](https://www.cloudflare.com/web-analytics/) and[Ahrefs Web Analytics](https://ahrefs.com/web-analytics), tell us totals: how many pages were viewed, which sites sent visitors, and approximate country and device. We also use **Google Analytics 4** to learn which guides and studio settings people find useful. It records page views and actions in the studio (opening a clip, changing a setting, exporting), with values rounded into bands such as a clip’s length or size, tied together by a random id stored in a first-party cookie. Your footage, its frames and sound, file names and any measurement taken from the video are never sent to it. Google signals and every advertising feature are switched off. Google handles the data under[its privacy policy](https://policies.google.com/privacy), and explains its use of information from websites like this one in[a page for partner sites](https://policies.google.com/technologies/partner-sites). Data sent to the United States is covered by the EU-US Data Privacy Framework, and Google Analytics deletes events once they are 14 months old. The basis for this measurement is legitimate interests: understanding how stabilize.video is used so it can improve (UK GDPR, Article 6(1)(f)). Its cookie is permitted without consent by the statistical-purposes exception that the Data (Use and Access) Act 2025 added to the UK’s Privacy and Electronic Communications Regulations. Objecting is simple and can be done whenever you like; the next section shows how. ## Cookies and opting out stabilize.video carries no adverts. Its only cookies belong to Google Analytics:`_ga` and `_ga_*`, each lasting at most two years, which a notice points out the first time you visit. Choose **Cookie settings** at the foot of any page, then **Turn off analytics**, and your browser keeps that choice. If your browser sends a [Global Privacy Control](https://globalprivacycontrol.org/)signal, we treat it the same way and the cookies are never written. Personal data is never sold. ## Who is behind the site stabilize.video is an independent project, paid for by its makers, without user accounts or visitor profiles. The only records we hold are the rating answers and error reports described above, and none of them is tied to a name, a cookie or an identifier. ## Your rights The law where you live may let you see the personal data held about you, correct or erase it, limit or object to how it is used, receive a portable copy, and complain to a regulator (in the UK, the Information Commissioner’s Office). Because projects exist only in your browser, clearing the site’s storage there is how you exercise those rights over them. Turning off analytics takes one click in Cookie settings, and[your Google Account](https://myaccount.google.com/data-and-privacy) has further controls. Ratings and error reports aren’t linked to you, so if you’d like one removed, describe roughly what it said and when it was sent. For anything on this page, email[hello@stabilize.video](mailto:hello@stabilize.video) or see the [contact page](https://stabilize.video/contact). ## Updates to this page Any change in how stabilize.video handles data will be described here, with a new date under the heading.