ToolClack
Form fillers have a trust problem, and honestly, they earned it. To “magically” fill everything, many of them read every page you open, record the forms you submit, and upload what they learn to suggest automations later. It works, in the same way a stranger following you around with a notebook would eventually get good at guessing your plans.
We think autofill is worth having without any of that. This post explains how FillKit’s autofill works, and just as importantly, what it never does.
Capture is explicit, not ambient
FillKit learns a form exactly one way: you point at it. You open the picker, click the fields you want to save, and those fields, with the values you chose, become an autofill set for that site. Nothing is captured from pages you merely visit, forms you happen to submit, or text you type during the day.
The difference sounds small and is everything. Ambient learning means software that watches first and asks questions later. Explicit capture means the extension knows only what you deliberately handed it, which for most people is a handful of forms they fill weekly.
Filling is a click, not a guess
A saved set is scoped to the site it came from, so the right fields show up on the right page and nowhere else. Filling happens when you click fill (or use the shortcut you configured), never automatically on page load. There is no heuristic engine silently deciding that a random search box looks like your street address.
Under the hood, each saved field remembers several stable attributes of its input, so the set keeps working when a site shuffles its markup. That matching runs at fill time, on the page you are on, in your browser. It is scoring logic, not surveillance.
Some fields are off limits, permanently
FillKit hard-skips three kinds of fields everywhere in the product, in the picker, the filler, the expander:
- Password fields. A form filler that handles passwords is a password manager without the security model of one. Use a real password manager; ours will not compete with it badly.
- One-time codes. 2FA prompts exist precisely so software cannot complete them for you.
- Card numbers and CVVs. Payment data does not belong in a productivity tool’s storage.
These are not settings you can toggle wrong. They are skipped by design, at the field-detection layer, in every code path.
Where the data lives
Everything you save, autofill sets, profiles, snippets, is stored in your browser via the extension storage API. The free version of FillKit has no account and makes no network requests to us: there is no server to leak from, no analytics, no telemetry. If you opt into backup, the file goes to your own Google Drive, visible only to you.
That architecture is the actual privacy policy. The written one at toolclack.com/privacy just describes it.
The test to run on any form filler
If you are evaluating a tool in this category, ours included, ask one question: what does it know that I did not explicitly give it? Read the permissions, watch what happens on pages you never told it about, and check whether “learning” can be turned off, or was never on to begin with.
FillKit’s answer is designed to be boring: it knows your snippets, your profiles and the forms you pointed at. That is the whole list. Try it and hold us to it.