What Happens to Your Passwords If Your Password Manager Shuts Down?

Encryption answers “who can read the data?” Continuity answers “can the user still obtain and use it?” A product can be excellent at the first and poor at the second.

NIST notes that many cloud password managers are designed so the service cannot access the vault even if the cloud service is compromised, while also warning users to protect the master secret carefully. See the NIST Digital Identity Guidelines FAQ. That confidentiality property is valuable during a breach, but it does not by itself guarantee continued access after a shutdown.

Four different failures

Temporary server outage

The provider may be unavailable for minutes or hours while installed clients continue serving locally cached data. Whether you can view or edit entries offline depends on the product.

Test this before relying on it:

1. Sync the vault.
2. Disconnect the device from the network.
3. Restart the client if safe to do so.
4. Confirm that you can unlock and view entries.
5. Determine whether offline changes sync correctly later.

Do not assume an offline-looking application is independent. Some clients require periodic online authentication.

Extended operational failure

The company may suffer a prolonged outage, lose infrastructure, or disable synchronization during an incident. Local access helps, but new devices may not be able to enroll and old devices may eventually lose sessions.

Acquisition or product discontinuation

A buyer may change pricing, policies, applications, or export formats. The service may give users time to migrate, but that is a business decision rather than a cryptographic guarantee.

Abrupt shutdown or bankruptcy

Servers may stop before users export. Support may disappear. Domains and signing certificates may expire. App stores may remove clients. A locally installed application can also become incompatible with future operating-system updates.

This is the scenario your exit plan must survive.

What determines whether your vault survives

A usable export

An export is valuable only if:

• It includes every important record type.
• Its format is documented or widely importable.
• You know whether it is plaintext or encrypted.
• You can decrypt or import it without the provider's live servers.
• You have tested the process.
• You protect the exported file appropriately.

Plaintext CSV exports are portable but extremely sensitive. Encrypted proprietary exports are safer at rest but may become useless if only the discontinued client understands them.

Local data

A synchronized local copy can bridge an outage, but local cache behavior varies. Determine whether the client keeps a complete encrypted vault, what unlock requires, and whether logout erases the cache.

Independent key possession

If the provider holds the only decryption key, shutdown or account denial can make the data inaccessible. A zero-knowledge system keeps user-controlled key material outside the provider, but the user still needs functioning software to apply it.

Available software

Open-source clients, documented formats, escrowed source, and standard primitives can improve recoverability, but none guarantees an easy migration. Build dependencies, signing, platform restrictions, and server protocols still matter.

Advance warning

Even a good export system is useless to users who wait until after access ends. Treat vendor shutdown as a low-frequency event with potentially high impact.

Lockstep's current continuity boundary

Lockstep encrypts vault records on the client and stores opaque encrypted data on the server. Its web client includes an endpoint for exporting encrypted entries, folders, and folder relationships.

That protects exported data from casual exposure, but an encrypted export is not automatically a vendor-independent recovery package. A complete continuity system must also provide and document a supported way to restore or decrypt that export without depending on a live Lockstep service.

As reviewed on August 27, 2026, users should not interpret the existence of an encrypted export endpoint as proof of indefinite standalone recovery. Lockstep should document the export format, restoration procedure, offline behavior, and shutdown plan before making a stronger claim.

This is a product limitation worth stating—not hiding behind “your data is encrypted.”

Build an exit plan now

1. Verify that export exists for your plan and device.
2. Export a test vault.
3. Confirm what the file contains.
4. Determine whether it is plaintext or encrypted.
5. Import it into a clean test account or compatible alternative where safe.
6. Protect backup files separately from the device that created them.
7. Record the software and instructions required to restore them.
8. Repeat after major product updates.
9. Keep provider recovery material outside the vault.
10. Monitor official service and security notices.

If an export is plaintext, create it only on a trusted device, minimize how long it exists, encrypt the destination, and securely remove unnecessary copies. Cloud-sync folders, email attachments, and ordinary downloads directories are common accidental leak points.

What to evaluate before choosing a provider

Ask:

• Can the client unlock offline?
• How long can it operate without the service?
• Does export include attachments, notes, passkeys, folders, and custom fields?
• Is there an encrypted export?
• Is the format documented?
• Can another product import it?
• Does restore require a live provider account?
• What happens after subscription cancellation?
• Is there a published discontinuation or data-portability policy?
• Can the user delete server copies after migration?

For the underlying key boundary, read Can a Password Manager Provider Read Your Passwords?. For recovery planning, read What Happens If You Forget Your Master Password?.

The bottom line

A password manager's disappearance should be an inconvenience, not a permanent loss. Achieving that requires more than encryption: local availability, portable exports, usable software, user-controlled key material, tested restoration, and clear documentation.

Until you have personally tested the exit path, you have a feature—not a backup.