The address is kept somewhere that outlives the browser

Storage that outlives the reader

The condition is a relation between two things: the place the string is kept, and the software you are reading the string in. The keeping place has to outlive the reader. If it does not, it is not storage. It is a temporary display that persists for as long as nothing is closed.

Much of what people treat as storage fails that by design. An amnesic session forgets on purpose; that is the feature. A private window discards its own history when it closes, and a bookmark made inside one goes with it. A browser set to clear itself on exit clears a bookmark as willingly as anything else, because the bookmark lives in the profile and the profile is what gets discarded. An open tab is weakest of all, since it survives exactly as long as the process does.

The test that separates real storage from the rest is a reboot. Not a closed window and not a locked screen, but a full shutdown and a cold start. Anything that can produce the string afterwards is storage. Anything that cannot was a view of a string, and the difference only becomes visible on the day you needed the second to be the first.

Three things this rests on

The string has the shape an onion address has supplies something worth keeping. Storage is content blind. It holds a truncated string with the same care as a correct one and hands back exactly what it was given, so the shape check has to happen before the string goes in, not after it comes out. The fixed count helps later too: because a current address is always fifty six characters before the dot, a stored copy that lost its tail can be caught by counting alone.

The address arrived by a route you can use again supplies the ability to derive it again, which decides what kind of object your store is. With a repeatable route the store saves you a trip and can be checked against the source whenever you doubt it. Without one, the store is the only witness to its own contents and nothing can contradict it.

Losing the device does not lose the account supplies the single copy problem, and this card inherits it whole. A store that exists in one place can be dropped, seized or reformatted, and the string goes with the hardware. That is not a different failure. It is the same one on a longer timescale: the reader outlived the store rather than the other way round.

What evaporating storage takes with it

Two cards depend on this one, and one of them is the last card on the map, so the reach is unusually long. You can log in a second time is the immediate one. That card draws a line between doing something once and being able to do it again, and its content is the second occasion, which begins by arriving at the same place. If the string is gone, the sequence never reaches the part where credentials matter. You are not finding out whether the password exists somewhere outside your head or whether you can produce the second factor. You are finding out whether you can locate a door. The two failures feel identical from where you sit: both look like not getting in.

You can come back tomorrow and still be you is the far end. It states that everything needed to become the same account again has to survive the end of the session, and the address is part of everything needed. It sits alongside the recovery phrase written down before it is wanted in that card, and the two behave alike: they are the components with no substitute and no fallback, because there is nobody to ask. If either is missing, the chain does not degrade gracefully. It has to be rebuilt from wherever the earliest surviving piece is.

There is a second and quieter mechanism, which does most of the actual damage. Losing the string does not stop you. It sends you looking. Going looking discards whatever route you had established and replaces it with whatever is nearest to hand at a moment when you are impatient, and the string that comes back has none of the history the original one had.

Skipping it: the session that starts with a search

The sequence is dull and it repeats. The machine restarts, for an update or a flat battery or an ordinary end to the day. The browser opens clean, because that is what it was built to do. No history, no open tab, no bookmark, and none of it is a malfunction. You reach for the tab, the tab is not there, and you notice you never wrote the string down anywhere.

What follows is the part worth avoiding. You go and find it again. Whatever you find is now the string you use, and it arrived under time pressure from a source chosen for being quick. From there every later condition on the map is satisfied against that string, and each is satisfied honestly. The chain is intact. It is pointed at whatever the search produced, and no card downstream is in a position to notice that the referent changed while nobody was watching.

The reboot test

Shut everything down completely: a genuine power cycle, not a closed lid. Start the machine again, and before opening any browser, produce the string from your store and read it.

A pass is producing the fifty six characters and the suffix from something that was not running while the machine was off, without hunting. A fail has two forms. The first is opening a browser in order to find the address, which means the browser is the store and the store is the reader. The second is reconstructing from memory, which feels like a pass and is not, because a string of this length recalled by a person carries an unknown number of errors and no way to find them.

Not a tool recommendation

This card names no product, no application and no medium, and takes no position on which is appropriate for anybody. The single property under discussion is whether the store outlives the reader. It is also not the same condition as losing the device, which asks about second copies. A store can outlive every browser you own and still exist in exactly one place, and those are two separate questions with two separate answers.