How to Stop a Chrome Extension Saving Passwords
Published: September 29, 2026. Updated: October 2026 by Andrew Apell, who builds Form ReDraft
Quick Answer
Short answer: Read the extension's permission list, then look at what it actually stores, then test whether it refuses password and card fields by name and by type. After that, check whether you can switch that protection off and whether you can delete what it kept. If any of those fails, remove the extension.
Key Takeaways
- The permission list honestly describes what an extension can reach. Read it first, not last.
- A tool that blocks credentials by field type alone misses the sites that label a password box as ordinary text. That is why the name check counts too.
- Recording should be reversible in both directions. You should be able to switch it off and delete everything, not merely hide it.
The worst reviews of form history tools are rarely about features. They describe a card number stored after the browser prompt said never, or a password that turned up in a history window nobody else knew existed. Both complaints are fair. Both are avoidable by looking at four things before you trust a tool with a year of writing.
Check 1: Read the Permissions
Open the extension's detail page in the browser and read the permissions it asks for. A form tool needs to read and change page content, which is a serious grant. It can see and alter the text of every page you open.
What counts after that is what the tool does with the access. A listing that states plainly that text stays on the device, and names the one network request it makes, gives you something you can check. A listing that says nothing about storage has not answered the question that decides whether the permission is acceptable.
Check 2: Look at What Is Actually Stored
Use the tool for a day, then look for a way to see the saved drafts. If the interface offers a list, a count or an export, you can audit it. If the only sign that anything was saved is a badge, you are trusting a claim rather than observing a behaviour.
Then read what the stored records contain. A draft tool should hold the text you typed and enough context to put it back, and nothing else. Records carrying form values from fields you never touched mean the capture is broader than the promise.
Check 3: Does It Refuse the Field, or Just Miss It?
Blocking credentials by input type catches the well-behaved cases. Blocking by field name catches the ones where a site presents a password box as a plain text input, and those are common enough to matter. A tool that does only one of the two will store something it should not.
Here is the test. Open a site with a login form, type a few characters, wait for the save cycle and then check whether a draft appeared. If it did, the exclusion is weaker than advertised.
Check 4: Can the Protection Be Turned Off?
A refusal that a setting can disable is a preference, not a guarantee. The stronger design gives you no switch at all, because the exclusion is part of the capture path rather than a filter applied afterwards.
You also want the reverse control, a per-site pause, so recording stops on a banking session or a medical form without uninstalling anything. Convenience and caution should not be in conflict here.
The Fifth Thing Worth Checking
Deletion. Ask what happens when you remove the extension, and what happens when you delete a single draft. A tool that keeps data after an uninstall, or hides deleted drafts rather than removing them, has a different privacy posture from the one its listing describes.
Look for a plain answer in the documentation, and prefer a tool whose local default means the question is small in the first place. The Form ReDraft documentation describes its own storage, exclusions and deletion in the same terms used here.
What a Good Answer Looks Like
A trustworthy answer takes four sentences and no more. The tool says what it stores, where that storage lives, which fields it refuses and how to delete everything. Anything shorter is a marketing claim. Anything longer is usually an attempt to avoid those four statements.
FAQ
How do I find out what an extension stores?
Open chrome://extensions, switch on developer mode and note the extension identifier. Then open the Application tab in DevTools, choose Extension Storage and select it. Everything the extension has written is listed there.
Can any extension read my passwords?
An extension with access to the page can read password field values as they are typed. Whether it does is a question of its code and its permissions, which is why the audit is worth doing.
Why do form tools block fields by name as well as by type?
Sites disguise sensitive fields. A password box is often a plain text input with autocomplete turned off, so matching on the identifier, class and label catches cases that the type attribute misses.
Should I be able to turn credential blocking off?
No. A setting that disables protection against credential capture will get used eventually, by accident or otherwise. The block should be unconditional.
Related Articles
Check What You Install
Form ReDraft refuses credential fields unconditionally, scrubs secrets out of ordinary text and keeps everything encrypted on your own device by default, with optional sync as the only network path.
Read the privacy policy