Privacy Policy
FileBrix is built so that there is almost nothing to write a privacy policy about. This page explains what that means in practice, and is honest about the exceptions.
Last updated
The short version
Your files are never uploaded. They are read, processed and saved entirely by your own browser, on your own device. FileBrix has no accounts, sets no cookies, stores nothing on your device between visits, and operates no server that receives file contents.
What happens to a file you open
When you choose or drop a file, the browser hands the page a reference to it. Everything after that — detecting the format, parsing, converting, rendering a preview, producing the result — runs as code inside your browser tab. When you download the result, the browser writes it from memory straight to your disk.
Nothing in that sequence crosses the network, and closing the tab discards all of it. There is no “we delete your files after an hour” promise here, because there is nowhere for a file to be stored in the first place.
Cookies and local storage
FileBrix sets no cookies. It does not use localStorage, sessionStorage, or IndexedDB. A file you are working on is held in the page’s memory so that it survives moving between tools, and is discarded when you press Clear, load something else, or reload the page. Nothing is written to your device.
Analytics
No analytics or tracking service is connected. The application contains a small internal event system used during development, and it is deliberately built so that it structurally cannot carry file contents, filenames, cell values or anything derived from your data. At present those events are not transmitted anywhere at all.
The one exception: map tiles
The geospatial tools that display a map load background map images from a third-party map provider (CARTO, using OpenStreetMap data). Those requests contain only the coordinates of the map squares being displayed, and your browser’s normal request information such as IP address — the same information any website you visit receives.
Your geometry, coordinates and file contents are never included in those requests; the map is drawn on top of the tiles by your own browser. This is verified by an automated test that inspects every off-origin request the map tools make. Tools that don’t show a map never contact the tile provider at all.
Advertising
No advertising network is currently connected. Some pages reserve blank space where an ad could later appear, but no third-party advertising script runs and no advertising cookie is set.
What is hosted by us
Everything the application needs to run is served from this site’s own domain, including the processing engines it loads on demand. Fonts, code and processing libraries are not fetched from third-party content delivery networks, so visiting a tool page does not announce your visit to anyone else.
Server logs
As with any website, the hosting provider that serves these pages may record standard request information such as IP address, timestamp and requested URL for operational and security purposes. That log covers the delivery of the web page itself and never contains file contents, because file contents are never sent.
Your rights
Since no personal data is collected, stored or processed by FileBrix itself, there is normally nothing to access, correct or delete. If you believe otherwise, or want to ask about any of the above, contact details are on the contact page or email info@filebrix.com.
Verifying any of this
You do not have to take these claims on trust. Open your browser’s developer tools, switch to the Network tab, and use any tool on this site: you will see the page’s own assets load, and no request carrying your file.
Changes to this policy
If this policy changes, the date at the top of this page changes with it. Material changes — such as connecting an advertising network that uses cookies — will be reflected here before they take effect.