Trust and transparency

Limited access, by design.

The goal is to help you reach a few essentials without turning an emergency card into a way to control your entire account.

Current status: This is a development preview. The complete account and emergency recovery system is still being built and tested.

01 / PREPARATION

Choose what belongs here.

The planned first version stores selected contacts and essential text. You decide which details are useful when your phone is unavailable.

02 / TWO FACTORS

A card and a separate phrase.

The planned flow combines a printed recovery card with a memorized emergency passphrase. Each card is intended for one successful use.

03 / SHORT ACCESS

Read only, then end.

A verified recovery would issue a 30-minute, read-only session for selected information. Account settings and billing remain outside that session.

Data minimization

What this first version is designed to leave out.

ContinuKey is not being built as a phone backup or password vault.

Built with boundaries

Work completed and work ahead.

The codebase now has field encryption, passphrase hashing, recovery-secret verification helpers, and database tests. Those parts need to be connected to account and recovery routes, then tested as a complete journey before anyone should rely on the service.

In development

No real recovery yet

The public demo is fictional. It does not verify identity, issue a session, or store your data.

Explore the simulation

Common questions

What does a borrowed device change?

Will my information stay on the borrowed browser?

The planned recovery app will use no-store responses and avoid saving secrets in browser storage. A device you do not control can still capture what appears on its screen, so end the session when finished.

Can someone use a found card by itself?

The planned flow also requires the separate emergency passphrase, applies attempt controls, and permits unused cards to be revoked from the normal account. These controls are not active in this preview.