What the extension does with your data. And what it doesn't.
This page is written for two very different readers: the one who just wants to know whether the tool is safe, and the one who has to approve it inside a company. The first only needs the next paragraph. The second will find everything else, permission by permission, with the means to verify every statement for themselves.
Verifill has no technical means of sending anything over the internet: the package does not contain a single line of networking code, and you can check it yourself in ten seconds.
Four permissions, and the reason for each.
An extension declares upfront everything it is allowed to do, and the browser forbids the rest. Here is our complete declaration: there is nothing else.
activeTabAct on the tab on screen, at the moment you click the icon or use the keyboard shortcut. Not on other tabs, not in the background, not without your action. Access ends as soon as you move to another page.
scriptingRead the fields of the form in that tab, labels, types, constraints, options, and write into them. That is the tool's whole purpose: without this permission, it can't fill anything.
storageKeep your settings, values and history in the storage the browser reserves for the extension, on your machine.
unlimitedStorageLift the size limit on that local storage: tens of thousands of fills and the selector memory fit in it. Nothing goes anywhere else, it's space on your disk, not extra access.
- Your other tabs
- Your browsing history
- Your cookies
- Reading your clipboard
- Your downloads
- Your passwords
- Standing access to websites
- Any remote server
Turn the internet off. The tool fills exactly the same.
It's the simplest test, and nobody needs to be technical to run it. It takes ten seconds, and it's worth more than any claim.
Turn off Wi-Fi
Disconnect completely.
Open a form
Any form already loaded in a tab, our try-it page, for instance.
Fill it
Everything works. A tool that sent your data couldn't.
To go further, your team can review the package line by line: it contains no third-party library, no obfuscated code, and no code is downloaded after installation.
Everything stays with you, and everything can be erased.
What is stored
Your per-form settings (skipped fields, forced values, chosen options), your own values and custom fields, the datasets you import, what the tool learned by watching you fill, the selector memory, the fill history, and the address of the pages concerned, used to find your settings again.
Where exactly
In the storage the browser reserves for the extension, on your machine's disk. No server, no sync between devices. One exception, and you decide it: the full backup is written to the folder you choose.
For how long
Until you erase it. Settings → “All memory, by address” shows and erases everything; history is cleared by date. Uninstalling the extension deletes its storage. Your backup and export files stay in your folders: they are your files.
What we see of it
Nothing. We receive neither your settings, nor your values, nor your reports, nor how often you open the tool. We have no way of knowing you use it.
The clipboard
The “copy” button in the Selectors tab writes a selector to your clipboard, because you ask it to. The extension never reads your clipboard.
The diagnostics log
When a write fails, full disk, storage unavailable, the extension records it on your machine: what could not be done, when, and the technical reason. Never your values. This log goes nowhere.
From the store, or rolled out by your administrators.
No workstation needs to create an account or reach a server to use the tool.
From the Chrome Web Store or Microsoft Edge Add-ons, like any extension. For a managed fleet, the package can also be rolled out through the browser's admin console.
The published package embeds no model: label understanding comes from rules written in the code, readable by unzipping the package. It isn't an unticked option, it's an absence your team can verify by listing the files.
The complete package can be handed over for review before any rollout.
The extension requires no account: nothing to activate online, no credentials to manage, no data to declare to us.
The complete package, ready to hand over.
Everything above can be checked piece by piece: the privacy policy, the measurements, and the package itself if your IT department wants to review it before any rollout.