Your files stay on your device.

What happens to uploaded files?

For the core image, signature, PDF and application-pack workflows, the selected files are read by your browser and processed locally. The web page does not need to send those file contents to a FileFix upload server.

What leaves the browser?

The website itself still loads ordinary web resources, such as HTML, JavaScript, stylesheets and browser-delivered advertising when advertising is enabled. These resources are separate from the local file-processing workflow.

Advertising

FileFix may show clearly labelled advertising in separated content areas, including after a download has started. Ads are kept separate from the download control and are not presented as a file-processing action.

Optional product analytics

The current FileFix release ships with product analytics disabled by default. When a site operator explicitly enables a supported analytics endpoint, FileFix can collect limited product-usage and performance events after consent where consent is required. These events exclude file contents, image pixels, filenames and the raw text of requirements; values are reduced to coarse categories where practical.

Browser security protections

FileFix uses a browser Content Security Policy to limit where scripts, connections and embedded resources may come from. The PDF helper is loaded only when needed and is pinned to a specific library version with an integrity check.

Third-party resources

Some PDF functionality loads a pinned, integrity-checked copy of the pdf-lib browser library from a content-delivery network when you choose PDF merge or PDF re-save. The library receives the code needed to run locally; your selected PDF bytes are processed in the browser and are not uploaded by FileFix.

Good practice for sensitive documents

Always use the destination website's own requirements and privacy terms as the final authority. Avoid sharing completed files through services you do not trust.