Privacy policy

Your video files

Video files you open in the editor are never uploaded, transmitted, stored or seen by anyone but you. This is a property of how the tool is built rather than a policy choice: the file is read from your disk into the browser tab, edited there by FFmpeg compiled to WebAssembly, and written back out as a download. The application has no upload endpoint and no server-side storage. Closing the tab discards everything.

No filenames, durations, resolutions, thumbnails or any other metadata about your video is sent anywhere either. Nothing about the file reaches the analytics described below.

Analytics

Every page on this site loads a small analytics script, P-analytics, from api.panalytics.money. It is there so the operator can see which pages get visited. Per page view it sends exactly four things:

• the address of the page you are on
• the page that referred you to it, if it was not a page on this site
• campaign parameters from the URL, if any — utm_source, ref, gclid and a handful like them
• how many seconds the page stayed open, sent once when you leave it

Nothing else is read from your browser: not your screen size, not your language, not a device fingerprint. Like every HTTP request, that request does carry your IP address and your user-agent string to the server — that is how a country and a browser name can be attached to a page view. Neither is sold nor shared.

The script does not set cookies, does not use localStorage, does not build a cross-site profile, and has no access to anything you do inside the editor.

If you would rather not be counted, any content blocker or a browser set to block third-party scripts will stop the request; the editor works exactly the same without it, because nothing in the tool depends on analytics loading.

Cookies and local storage

This site sets no cookies of its own, and stores nothing in sessionStorage or IndexedDB. There is no account system and no session.

It does write one entry to localStorage, and it is worth being precise about it. When you click an Output format or a Max resolution button in the editor, that choice is saved under the key alter.video:prefs so the next visit starts on the format you last picked. The stored value is only those two settings — for example {"format":"mp4","quality":"original"}. It contains no identifier, nothing about you and nothing about any file you have opened, it is never transmitted anywhere, and it is written only when you click one of those buttons — a landing page's own preset does not silently become your default. Clearing site data removes it.

The other thing your browser keeps between visits is its ordinary HTTP cache — which is where the ~32 MB FFmpeg WebAssembly engine lives after the first edit, so that later edits start immediately.

Server logs

The site is served by a Caddy web server in a container. Like any web server it handles ordinary HTTP requests, which carry your IP address and user agent by necessity. These are used only to serve the page and to keep the server running; they are not combined with the analytics data, not sold, and not shared.

Third parties

There is exactly one other origin involved in loading this site: api.panalytics.money, for the analytics script above. Everything else — the page, the styles, the JavaScript, the fonts (system fonts, in fact) and the FFmpeg WebAssembly engine — is served from alter.video itself. There are no ad networks, no tag managers, no embedded video players, no social widgets and no A/B testing tools.

Children

The site is a general-purpose tool with no account system and collects no personal information that could identify anyone, of any age.

Changes and contact

If the analytics setup or any third-party dependency changes, this page is updated in the same commit — the site is a static build, so the policy and the code ship together. The site is operated by Kyllian; questions can go to the GitHub profile listed on the about page.

See also: terms of use and about this site.