Forum Discussion
1Password now available in Comet, the AI-powered browser by Perplexity
- 2 months ago
Hi all, thanks for raising these questions and sharing your concerns.
At 1Password, our guiding principles are privacy, security, and transparency, and ensuring people can use the tools they choose safely. We know AI and new browsing technologies raise important questions, which is why our role is to give people choice without compromising trust.
To clarify a few points about our partnership with Perplexity on the Comet browser:
- Your data remains private. Nothing about this partnership changes how 1Password works. Vaults are end-to-end encrypted, and neither Perplexity nor Comet has access to your information. Your secrets remain encrypted and never leave your control.
- The extension is the same. The 1Password browser extension works in Comet exactly as it does in Chrome, Safari, Firefox, and other Chromium-based browsers. There is no special integration that exposes additional data.
- This is about choice. Our customers want us to be where they are. For those who want to try Comet, we are ensuring their login and autofill experience is secure, just as it is in other browsers.
We take trust seriously and will continue to make decisions with privacy, transparency, and security at the core.
- Your data remains private. Nothing about this partnership changes how 1Password works. Vaults are end-to-end encrypted, and neither Perplexity nor Comet has access to your information. Your secrets remain encrypted and never leave your control.
I just got another Comet related mail:
"1Password has introduced a Comet-compatible browser extension, giving you a safer, more seamless way to access and protect their credentials "
So maybe they have listened... I'm not about to test it mind you!
I'm still interested to know if the Comet agent can see what the browser is sending. If 1Password fills in a password filed and that password is then sent down an encrypted https connection does the Comet LLM see that password as part of the text that is encrypted and sent before it is encrypted? Just how closely entwined is this LLM to the guts of the browser?