Your data stays here.
Inputs and firmware files are processed in your browser.
Inputs & files
Numbers, byte sequences, text, JSON, C struct definitions and field edits, TLV inputs and records, Strings extractor files, imported byte files, CRC files and byte ranges, selected Intel HEX/BIN files and their address/padding settings, ELF/GNU map builds, and GCC stack reports are processed locally by JavaScript. FirmwareKit does not upload them to a server.
Tool inputs stay in page memory. They are not saved in local storage, cookies, or URL parameters. Closing or reloading a page clears the app’s working state; your browser may restore form fields according to its own settings.
The app does not read a file until you choose it or drop it into a file tool. Exports create downloads on your device. Memory Lens reports include the filenames and build symbols you choose to export. Its offline download bundles the tool itself without your files or analysis.
Clipboard & browser features
Copy buttons write only the selected result to your clipboard, after you click them. FirmwareKit does not read your clipboard.
No accounts, advertising, analytics scripts, external fonts, or tracking cookies are included in this release. Calculations run locally. Some tools load additional static code when first used; file contents and tool inputs are never included in those requests.
Hosting & external links
Loading the site sends normal HTTP requests to its hosting provider. The provider may record connection metadata such as your IP address and requested page; tool inputs are not part of those requests.
GitLab feedback and format references open external sites, which have their own privacy practices.