Overview
FormKeeper is a Chrome browser extension that automatically saves what you type into web forms so you can restore it after a crash, a closed tab, or a session timeout. This privacy policy explains what data the extension does and does not collect.
Data we collect
None. FormKeeper does not collect, transmit, share, or sell any personal data. All form data is stored locally on your own device. Nothing is sent to any server, the developer cannot see it, and there is no analytics, telemetry, or tracking of any kind.
Data stored locally
The extension stores the following information locally in your browser using Chrome's built-in chrome.storage.local API:
- The text you type into form fields and text areas, keyed to the page you typed it on
- A short history of recent versions of each field, so you can roll back to an earlier draft
- Your settings — themes, accent color, banner position, floating button, hotkeys, and per-site preferences
This data never leaves your device. Password fields, credit-card fields, and one-time-code (OTP) fields are never saved — this is built in and cannot be turned off. Saved data expires automatically after a configurable period, and you can preview, restore, or delete any of it at any time from the dashboard.
Permissions used
- storage — to save your form input and settings locally on your own device.
- activeTab — to read and restore form fields on the page you're currently on.
- scripting — to inject the save and restore logic into the page.
- commands — to power the configurable keyboard shortcuts (save now, restore, open dashboard).
None of these permissions are used to read, collect, or transmit your browsing data.
Third-party services
The extension does not communicate with any third-party servers, APIs, or analytics services. There are no ads, no affiliate links, and no monetisation of your data.
Changes to this policy
If this policy changes in a meaningful way, we will update the "Last updated" date above and note the change in the extension's release notes.
Contact
Questions about this privacy policy? Open an issue on GitHub.