Privacy policy

Local file processing

When you choose a file, code running on your device reads it and creates the result. There is no FileGizmo account, upload queue, processing server, or cloud file history. Downloads are created as temporary browser URLs.

Refreshing or closing the page clears whatever a tool was holding in memory. Two things deliberately outlive it, both on your device and neither ever sent anywhere: the editors keep a recovery draft for seven days so that a crash does not cost you your work, and sending a result from one tool into another keeps that file for up to a day so the second tool can pick it up. Any editor page can clear both, for that tool or for every tool. Your browser or operating system may also retain a downloaded result according to settings you control.

Website data

In your browser’s local storage FileGizmo keeps the light or dark theme, recently opened tools, the settings you last chose, and anything you explicitly save for reuse: tool setups, stamps, workflow recordings, and form profiles. A saved form profile can contain personal details entered into PDF fields, so save one only on a device you trust. In your browser’s database it keeps editor recovery drafts and tool-to-tool transfers. None of this is sent to FileGizmo, and you can remove saved items in their tool or clear all of them with your browser’s site-data controls.

Passwordless accounts store the email address you use to sign in, your plan and billing state, and the devices attached to that plan. They do not store files, extracted file contents, tool history, or tool usage. FileGizmo does not sell personal information or use cross-site behavioral profiles.

Aggregate traffic measurement

FileGizmo counts page views, and that is the whole of it. Cloudflare Web Analytics records that a page was opened, which page it was, the country it came from and the kind of browser. It sets no cookie, stores no identifier on your device, and has no way to recognise you on your next visit or on any other site.

It cannot see your files, and not as a matter of policy. The analytics script runs in the page; your file is never handed to the page’s network layer at all, so there is nothing there for it to observe. What we learn is how many people opened which tool. What we do not learn, and could not learn from this, is who you are or what you converted.

There is no Google Analytics, no advertising tag and no session recorder. The check is still yours to run: open the browser Network panel and you will see one request that is not ours, for the analytics script, and no request anywhere carrying your file.

One file tool is an exception. Address to coordinates cannot work without asking a mapping service where a place is, so the addresses in the column you choose are sent to Geoapify, whose privacy practices are their own. The tool says so before you run it. Your file itself is never sent, only the addresses it needs to look up.

Bring your own key is a separate, paid provider mode and is off by default. When you explicitly enable it for a request, the original file is still opened locally, but the extracted text and your OpenAI API key are sent directly from your browser to OpenAI. FileGizmo does not receive either one. OpenAI's terms, retention controls, and billing apply to what you choose to send. Every ordinary file tool still processes files only on your device.

This has changed once, and here it is. Activate is not a tool and handles no files, but it does contact somebody: a licence key cannot be checked without asking the company that issued it, so pasting a key there sends the key and a device label (the word FileGizmo and your browser name) to Dodo Payments, who take our payments and whose privacy practices are their own. It sends nothing else, no tool page is permitted to make that request, and the answer is kept in your browser rather than anywhere we can read. If you never buy anything, nothing on this site ever contacts anyone except the one tool above.

Network and hosting data

Like any website, the hosting network may process ordinary request information needed to deliver a page, such as an IP address, requested URL, browser details, timestamp, and security signals. This is separate from tool processing: your selected file is not included in those page requests.

Third-party links

Links to documentation, research, or GitHub take you to services with their own privacy practices. FileGizmo does not control data you choose to provide on those sites.

How to verify the claim

Open your browser’s developer tools, select the Network panel, clear the list, and process a harmless test file. The tool may load code from FileGizmo’s own origin after your interaction, but it does not post the contents to a FileGizmo conversion endpoint.

Your file is sent to no oneOn every tool but address to coordinates, which asks a mapping service about the addresses you pick, nothing at all leaves this origin. This is a technical property of the product, not a promise to delete a server copy later.

Questions and changes

Privacy questions can be raised through the contact page. Material changes to these practices will update the date above before they take effect.