AI browsers, password fields and card numbers
Short answer
An assistant that reads the page can read what is on it, including a form you have filled in. The protection is architectural: an assistant that transmits nothing cannot leak a card number to a vendor.
What a page-reading assistant can see
Whatever is rendered. That includes form fields you have typed into, an order confirmation with the last four digits, an account number on a statement page.
Password fields are masked visually, but any assistant reading the DOM is reading the document rather than the pixels.
Two separate risks
Transmission: a hosted assistant sends page content to a vendor, so anything on screen can end up in someone else's logs. A local assistant does not transmit, which removes this entirely.
Action: an agentic browser that can fill and submit forms on your behalf can be induced to do so by prompt injection. Nightjar's assistant reads and answers; it does not fill or submit forms for you.
Sensible practice regardless of browser
Close the assistant panel on banking and checkout pages if you are unsure what a browser does with the page.
Prefer a password manager for credentials over a browser's own store, and review every field before submitting a filled form.
Other ways people ask this
- Should I worry about an AI browser seeing my password manager?
Related
- Up a levelGuides: local AI, browser privacy and the hardware to run it
- Closely relatedAI assistants and your banking pages
- Closely relatedWhat Brave Leo sends to Brave, and how to check
- Closely relatedChatGPT Atlas has been retired: what happened to your data
- Elsewhere on the siteAI browser alternatives, compared honestly
- Elsewhere on the siteAI browsers compared: where each one sends your pages