File processing and security
Last updated: 25 July 2026 · Document set version 2.0 · Effective 25 July 2026
This page describes how FERVIST Tools processes files and which safeguards protect you — in plain language, matching what the code actually does.
Where your files go (and where they don’t)
Files you select are read into the memory of your browser tab and processed there by the tool’s own engine. They are not uploaded: after the page has loaded its own program files, the site makes no network request carrying document bytes, names or passwords, and no third-party request at all. The result is offered as a temporary local download URL, which is revoked after use. Closing the tab ends the working session.
What we cannot do
Because your files never reach us, we cannot scan them for viruses and cannot recover them for you. Damaged or malicious files are handled with controlled, per-file errors so one bad file does not take down your whole task. Keep your own copies of important documents.
Technical safeguards
The site ships a strict Content Security Policy generated from the actual build, sends hardening headers (including HSTS on the production host), self-hosts its fonts, uses no third-party scripts and stores no cookies. Dependencies are audited as part of the release process.
Responsible disclosure
Found a vulnerability? Email contact@fervist.com with a description, steps to reproduce and the affected URL. Please give us reasonable time to fix the issue before publishing, avoid tests that disrupt the service for others, and never use documents of third parties. We do not run a paid bounty program, but we credit reporters who wish to be named. Machine-readable details: the project’s SECURITY.md.