So in terms of the addon being detected and being used to fingerprinting you, it seems unlikely (but it is always possible - there is always a chance). However, pages cannot know the extension is used. The extension adds content to the page DOM when needed. On KeePassXC-Browser extension's private policy ( ) it states:

(I believe) it's just not worth the risk given that even one error can completely deanonymize you. It's complicated and for me, I wouldn't use it. It does refer the reader to the Surveillance Self-Defense guide for KeePassXC, which includes instructions for the browser extension, but does not mention Tor (or Tor Browser).Īfter reading a bit, I've come to believe that this particular extension may or may not affect your anonymity. The Tails documentation for KeePassXC says nothing about the browser extension. This is not particularly helpful.Įdit: Tails includes both Tor Browser and KeePassXC, but not the browser extension. I found that the extension developers specifically worked on Tor Browser integration in issue #4123 and the extension is listed in the ArchWiki page for KeePass (with no comments on the extensions-in-Tor Browser issue).

Is this of any concern with this particular extension? Tor Browser already comes with HTTPS Everywhere, NoScript, and other patches to protect your privacy and security. Plugins or addons may bypass Tor or compromise your privacy. We do not recommend installing additional add-ons or plugins into Tor Browser This all seems fine, except perhaps for the last item about update checks.Ĭrsi’s answer goes on to say (the cited page is also accessible via an onion service):īut you should not add extensions to your TBB. To allow using KeePassXC-Browser on all websitesįor checking the latest KeePassXC version from GitHub To show browser notifications on install or update Allows password to be copied from password generator to clipboardĪllows communication with KeePassXC applicationįor storing extension settings to localStorage

Keepassxc plugins