01
The short version
nomark has no server, no database, no accounts and no analytics. Images and videos you drop into it are processed by code running in your browser and are never transmitted anywhere. There is no upload endpoint to disable, no retention period to state and no data to request the deletion of, because none of it exists.
02
What runs in your browser
The page is static HTML, CSS and JavaScript. When you add a file it is read into memory, decoded into pixels, processed, and offered back to you as a download. Batch work runs on background worker threads on the same machine. The video path additionally downloads a denoising model file the first time it is used; that request fetches the model and carries nothing about you or your clip.
03
What we do and do not measure
We do not measure anything. There is no analytics script, no tag manager, no tracking pixel, no session recorder, no experiment framework and no error reporting service. No page view, click, file name, file size or device fingerprint is collected by nomark. The hosting server keeps ordinary web server logs of requests for the page itself, as any web server does; those logs contain nothing about the files you process, because your files are never requested from it.
04
Third-party requests
There are none. Fonts are self-hosted, icons are inline, and no script, stylesheet or image is loaded from another origin. This is not only a privacy position: it is what makes the offline behaviour work. You can confirm all of it in the network panel of your browser’s developer tools.
05
Local storage
nomark does not use cookies, local storage, session storage or IndexedDB to hold your content or to identify you. Your files exist only in the tab’s memory and are released when the tab is closed or reloaded. Your browser will cache the page’s own assets exactly as it caches any website, and clearing your browser cache removes them.
06
SynthID and provenance
nomark removes the visible watermark. It does not remove SynthID or any other invisible provenance signal, and it does not attempt to. A file processed here remains identifiable as generated content by tools that inspect for those signals. We state this plainly, because a privacy page that implied otherwise would be misleading.
07
Changes to this page
If the behaviour described here ever changes, for example if an optional feature required a network call, this page will be updated before that feature ships and the date at the top will change with it.
08
Contact
Questions about this page go to the maintainer, Vladimir Mihalevich, at mihalevich.dev.