The files you process with these tools are never uploaded to any server; from start to finish they stay inside your own browser. Two things are worth knowing: this site uses Microsoft Clarity for analytics, which records your clicks and scrolling on the page, and one tool — the video trimmer — has to send the video URL you paste to our server. Both are explained below.
This site is a set of static pages. There is no backend service, no database and no file storage. Merging and splitting PDFs, cropping images, checking transparency, computing MD5, formatting JSON, converting Markdown — all of it is done by JavaScript inside your browser: the file is read into memory, processed, and handed straight back as a download, without a single byte leaving your device. Disconnect from the network once a page has loaded and the tools keep working — that is the most direct way to verify this for yourself.
The third-party libraries these pages use — for PDF handling, Markdown parsing, image cropping and so on — are all hosted on this site's own server rather than loaded from a public CDN. So opening a tool page does not make your browser fetch anything from a third party, and leaves no record of your visit with one.
This site stores exactly two values in your browser: the interface language you picked, and which way you prefer to enter time ranges in the video trimmer. Both exist only to remember your preference, are never sent anywhere, and disappear when you clear your browser data. If you want to check for yourself, they appear in developer tools as bt-lang and vt-seg-mode.
This tool differs from the rest: what it works on is not a file on your machine but a web address, so network requests are unavoidable. Here is exactly what happens.
The link you paste goes first to our resolver endpoint, which works out whether it is a share page or a direct link and derives a media address that can be read directly. That step sees the full URL you entered.
A browser cannot make cross-origin ranged requests against third-party storage directly — the CORS preflight blocks it — so the video bytes pass through our forwarding endpoint. It streams and nothing more: nothing is written to disk, nothing is cached, no video content is retained, and beyond the web server's ordinary access log nothing is recorded.
The bytes that come back are parsed and remuxed inside your browser, and the resulting clip is saved straight to your computer without ever being sent back. In other words: the URL and the fetching go through our server, the finished file does not. If that bothers you, simply do not use this tool — none of the others have anything to do with it.
This site uses Microsoft Clarity to understand how the pages are used — which tools people actually reach for, and which step trips them up. It records clicks, scrolling, mouse movement, time on page, browser and device type, and an approximate location inferred from your IP address (city level, not a precise position), and it writes a cookie in your browser. That data is sent to and processed by Microsoft under Microsoft's own privacy statement.
The contents of the files you process are not recorded — the files are never uploaded, so Clarity has no way to reach them. For the tools that display a result on the page — generated passwords, formatted JSON, rendered Markdown, computed hashes, file names and the like — those regions carry a masking marker, so Clarity treats them as obscured when it captures the page. Anything typed into an input field is masked by default.
Your browser's tracker-blocking setting, private browsing, or any ad blocker will stop Clarity from loading, and the tools work exactly the same without it — they never depended on the network in the first place. Clarity also only loads on the live domain, so local previews and test environments never trigger it.
This site is hosted on Cloudflare Pages, and the endpoints used by the video trimmer run on a separate server. As with any website, both produce standard access logs: IP address, timestamp, the address requested, and the browser identifier. They are used for troubleshooting and abuse prevention, never for profiling, and are neither shared with nor sold to third parties.
There are no accounts, so no email addresses, phone numbers or identifying details are collected; no ads, so no advertiser tracking code; no third-party share buttons and no comment system; and no data is sold or traded to anyone. This is not a promise of restraint — none of it was ever installed.
If you have a question about this page, or want to confirm what a particular tool actually does, write to [email protected]. All of this site's front-end code is delivered to your browser along with the page and can be inspected in developer tools — if what is written here and what the code does ever disagree, the code is what counts, and do point it out.
If this policy changes, the date at the top of this page will be updated.