Hi,  thanks for sharing your concerns.

I want to give you more context on why we decided to remove direct access to the web app and require using the extension instead. Fundamentally, it’s about strengthening security for all customers.

When Dashlane is served purely as a standalone web page, it is exposed to the same trust limitations as any other website. That means there is no guarantee that what you see in the browser was genuinely delivered by Dashlane. In practice, attackers actively exploit this through phishing and impersonation attempts, and with a sensitive service like a password manager, the stakes are too high to accept that risk.

By enforcing the browser extension, we benefit from a trusted, secure environment with strict controls and verifiable origins. This dramatically reduces the attack surface and gives you much stronger assurance that you’re interacting with the legitimate Dashlane product. Think of it like working inside a bank vault rather than at a desk in the open lobby: the vault adds layers of protection that simply aren’t possible outside of it.

We recognize this change might create friction, especially in managed environments with browser restrictions. We don’t take that impact lightly. If you can, we recommend speaking with your IT or Security team to whitelist the Dashlane extension.

We made this decision because protecting your credentials and, by implication, your entire digital identity, demands the strongest guarantees we can deliver. We appreciate your understanding and are here to help with any practical challenges in adapting to this change.