{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiergwocozl6mra33s7ejcdqzm4fousnoyxwyyinuc4quq7ilinq4q",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mhbv2kuaksr2"
  },
  "path": "/t/question-about-keepass-autofill-not-extension-and-privacy-on-mullvad-browser/36354#post_1",
  "publishedAt": "2026-03-17T20:27:01.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "I recently switched from Bitwarden to KeePass paired with Syncthing, and the setup is working smoothly. However, I have some lingering concerns about privacy, specifically regarding KeePass’ autofill functionality when used with Mullvad Browser.\n\nI understand that **browser extensions can be fingerprintable** since they often modify the DOM. But what about KeePass’ native autofill? From what I can tell, it operates more like a macro, simulating keystrokes to input the username, password, and hit Enter, without altering the page’s DOM. This leads me to believe it might be less detectable.\n\nIs this assumption correct? Could native autofill still introduce fingerprinting risks through other means (e.g., timing patterns, event behaviors)? Or does Mullvad Browser’s anti-fingerprinting protections effectively mitigate these concerns?",
  "title": "Question About KeePass Autofill (NOT extension) and Privacy on Mullvad Browser"
}