An autofill extension needs to recognize fields on a page. That technical access does not tell you what it stores or sends elsewhere. Before saving personal or business information, distinguish three actions: reading, saving and transmitting.
Saving should be deliberate
A clear workflow starts with an explicit action. In FillKit, you can complete a form and choose Save this form, or select individual fields with Pick fields.
The first method stages fields containing values; the second lets you select them individually. Review the selection and remove unnecessary information before keeping the set. Visiting a page is different from saving its form. The autofill-set documentation explains both routes.
Local storage, backup and sync
According to ToolClack’s privacy policy, FillKit without an account stores snippets, sets, details and settings in the browser and sends no telemetry to ToolClack.
Cloud options change the data route: Drive backup places a copy in your Google Drive; sync transfers the necessary content to your ToolClack account. Both are optional. Local-first describes the core workflow, not an absence of remote services in every configuration.
Sensitive fields and saved text
FillKit states that it ignores password, one-time-code, card-number and CVV fields. Do not interpret this as a filter that removes every secret from any text. A free-text note can contain confidential information; avoid saving it unnecessarily.
Local copies and exports also need care. If you share the computer or backup file, consider who can access them.
Test before everyday use
Create a set with fictional data on a familiar form. Apply it and check which fields change and whether the website recognizes the values. Remove the test data afterward. An autofill button does not guarantee compatibility with every custom control.
Does a broad permission mean an extension is unsafe?
It is not enough to decide on its own. Examine the permission’s purpose, the data policy and documented behavior together.
Where should I start?
Read the form-filling guide and the local-first explanation. Evaluate FillKit against the data route you intend to use, locally or with backup and sync.
