Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.

Your password manager is Canadian. Your passwords might not be.

An end-to-end encrypted password manager running on infrastructure we own and operate, so there is no US provider in the chain that holds your vault.

Residency is not sovereignty

When you chose your current password manager, you asked whether the data stays in Canada. It is the reasonable question, it is the one in every procurement checklist, and most vendors can answer yes. It is also the wrong question.

A server can sit in Montréal and still answer to Washington

The US CLOUD Act reaches data held by an American provider wherever in the world it is stored. FISA Section 702 reaches American service providers. This is the same reasoning the Court of Justice of the European Union used to strike down Privacy Shield in Schrems II.

So a password vault hosted on a US cloud platform can be physically Canadian and legally American at the same time. The provider may also be prohibited from telling you that a request was made.

Sovereignty is a property of who operates the infrastructure, not of where the rack sits. Anyone can rent a Canadian region. Almost nobody owns the hardware. We do.

What this means under Law 25

Québec's Law 25 requires a privacy impact assessment before personal information is communicated outside Québec, and requires the receiving jurisdiction to afford adequate protection. Because US jurisdiction follows the hosting provider rather than the rack, that assessment is owed even when the server is in a Canadian region. It has to be written, maintained and defended at audit.

With Patrii there is nothing to assess, because nothing leaves. That is a procurement shortcut, not a feeling: one fewer assessment to produce every time somebody asks.

Where our own chain runs

We hold ourselves to the test we just described. The infrastructure that stores and serves your vault is ours, in Canada. Two things sit outside it and we would rather say so plainly than have you find them: payments are processed by Stripe, which never receives vault data, and the browser extensions are distributed through the Chrome and Mozilla add-on stores, which distribute the client and never hold vault data. A directly downloadable signed Firefox build is available for organizations that prefer to avoid even that.

How your team uses it

1

Create your vault

Choose a master password and print your emergency kit. Both happen on your device, and we never see either one.

2

Install the extension

Chrome or Firefox. Pair it once with a code from the console, and it stays signed in until you lock it.

3

Save and fill as you work

The extension offers to save new logins, fills known ones, and generates strong passwords when you need them.

4

Share what the team needs

Put shared credentials in a team vault so they are handed over once, instead of being emailed around and never rotated.

Questions people actually ask

You may not need to. One question worth asking first: has anyone completed the Law 25 assessment for the cross-border transfer? Most teams assume a Canadian head office settles it. It does not, because the test applies to the hosting provider, and most password managers run on American cloud platforms.

That covers physical location, not legal reach. The US CLOUD Act applies to the provider rather than the rack, and the provider can be barred from telling you that a request was made. That gap between residency and sovereignty is the reason this product exists.

Their emergency kit recovers their own vault, which is why printing it is a required step at setup and not an optional one. If they lose both the password and the kit, that personal vault is gone permanently and we cannot retrieve it. Shared team vaults are unaffected, because other members hold their own keys.

Really. It is the direct consequence of the guarantee: if we held anything that could recover your vault, we could be compelled to use it. Organizations that need guaranteed recovery on shared credentials can enable administrative recovery per team vault, and every member of that vault sees a permanent notice naming exactly who can read it. It never applies to personal vaults.

Not yet. Today it is Chrome, Firefox and the web console. If mobile or SSO is a blocker for your team right now, tell us on the first call and we will say honestly whether it makes sense to wait.

You should not take it on our word. The design is documented, and the client is auditable: the browser extension ships through the Chrome and Mozilla stores, versioned, so anyone can inspect what it sends. What we will not do is claim a certification we do not hold. When we complete a third-party security audit, we will publish it.

You export everything, unencrypted, in a standard format, at any time, and it is written into the contract. Your credentials are not a retention mechanism.

Bring us the assessment you wrote for your current password manager

If you do not have one, that is exactly the conversation worth having. Our bilingual team can walk through what changes when the infrastructure is Canadian-operated.