Private today.
Private later?
“Harvest now, decrypt later” means sensitive data captured today could face better decryption tools in the future. The useful question is not a date. It is how long your data needs to stay confidential.
How long should this information remain private?
Pick a horizon to begin.
The right preparation starts with data lifetime, not a dramatic prediction. Make the dependency visible, then ask your security team about migration paths.
Start with an inventory
Manual confidentiality-horizon choices and the source export fallback
Read the explanation
The source offers Short lived, Long lived and Mission critical. Each selects one fixed readiness band and action paragraph. Bars compare three manual choices with zero inspected cryptographic systems at one hundred fifty pixels per item. This explains the local planning aid; it does not evaluate keys, algorithms, certificates, actual exposure or a quantum timeline. The labels are source-defined text, not an externally verified threat model or guarantee. Before a choice, the page shows a waiting label and zero active horizon buttons. Export nevertheless uses the short horizon by default. Bars compare zero selected buttons with one default exported horizon at one hundred fifty pixels per item. The manual inventory checkbox can also be true while no horizon is selected; the screen status stays empty, but export records true. These are source fallback rules, not evidence that an inventory was actually performed. The actual export has seven fields: real timestamp, horizon, horizon label, readiness band, action, inventory step completion and scope. Bars compare seven document fields with two stored properties at fifty pixels per item. The stored properties are horizon and the manual completion boolean. Reload restores both. Reset saves an empty horizon and false rather than deleting storage, so the screen waits while the next export again uses short. Nothing is scanned, migrated, sent or evaluated by a model.