Change device, without losing a thing.
This is the whole Fortress's moment of truth: the day you restore. With Ozorys it isn't stressful — it's a non-event, provided you wove your net.
Restoring, a non-event
People often picture restoring as a technical ordeal. Here it's the opposite: a new device, your code, and the vault comes back intact. The whole architecture of the previous modules converges on this simple moment.
The fear of “losing everything when I change phones” no longer has any basis — not by magic, but because you prepared the ground: a net, a key, a check that has already done its work.
The gesture, step by step
The principle is always the same: you retrieve one of your strands — the encrypted file, the Tribu cloud, or the paper QR key — you enter your code or scan the key, and Ozorys unseals the block to rebuild your vault. No data ever travelled in the clear; restoring merely puts the key back in the lock.
A few seconds later, your categories, your history, your RAV are exactly where you left them.
Restoring isn't “downloading your data”: it's unlocking, locally, a block you already had. The secret never leaves your side.
The recovery phrase
Depending on how you closed your vault, a second open-sesame may come into play: the recovery phrase. It's the fallback for combined mode in particular, where the code alone isn't enough to reforge the key. You keep it carefully, like the paper key — it's a rampart, not a detail.
Well kept, it turns even a lapse of memory into a mere setback. It's the last piece of the net, the one that closes the circle of peace of mind.
Write down your recovery phrase as soon as it's created, off the device, with the same rigour as the paper key. You almost never use it — but the day you need it, you're very glad to have it.
Pick up exactly where you left off
This is where the Fortress closes its promise: losing the device is no longer losing the budget. You open a new door, and there is your vault — intact, up to date, yours. Sovereignty was never a constraint; it was the guarantee of this continuity.
You've walked the whole Fortress: understanding the encryption, weaving a net, checking it, keeping the ultimate key, sealing, and restoring without fear. Your vault no longer has a blind spot — and your data, more than ever, belongs to you alone.
A calm restore assumes a net prepared beforehand: with no backup and no key, there's nothing to restore. Modules 19 to 23 aren't optional — they're the insurance policy for this one.
Let's check it stuck
Six questions, marked instantly. Your answers never leave this page.
1. With a net prepared, changing device is…
The whole architecture converges on this simple moment.
2. Technically, restoring means…
The key in the lock: the secret never leaves your side.
3. Which strands allow restoring?
Any one of the net's strands brings you back to your vault.
4. The recovery phrase serves in particular…
It's a rampart: well kept, it turns a lapse of memory into a mere setback.
5. After restoring, you find…
Total continuity: exactly where you left them.
6. The one real condition for a calm restore?
With no backup and no key, there's nothing to restore: the previous modules are this one's insurance policy.
Today's challenge
Do a dry-run restore: on a device you trust, restore from one of your strands and check that everything comes back. Succeeding at a restore in calm conditions means never dreading it again — and completing your Fortress path.