What stays behind

When a session ends, the service stops treating you as signed in. That is one ending. It is about a record somewhere else and it has nothing to do with your machine.

The other ending is what happens locally when you close things: what the browser discards, what it keeps, and what other software on the machine picked up along the way. People experience these as one event and they are not connected at all.

• Anything you deliberately saved. A bookmark, a note, a file. This is the largest category and the one people forget because saving felt like a small action.
• Anything you copied. A clipboard holds what you put in it and often longer than you expect.
• Anything another application noticed. Screenshots, previews, sync services and backups all operate without asking.
• Anything you typed elsewhere. A search, a message, a note written while you were working something out.

Of everything in a session, the address is the item most likely to still be around later, because it is the one thing people deliberately keep. Each address is 56 characters, the published set is 168 characters in total, and that small amount of text is the part that has the longest life on a machine.

That is not a warning, it is a framing. The address has to be stored somewhere, as the panel on where an address lives sets out at length. The point is that storing it is a decision about persistence, and it deserves the attention that decisions get rather than the attention that habits get.

Clearing browsing data removes some of the first list and none of the rest. It does not touch a file you saved, a screenshot you took, a message you sent yourself, or anything another application copied.

This is worth stating because clearing has a strong feeling of completion attached to it. The feeling is out of proportion to what happened, and it tends to substitute for thinking about the items that were never in the browser to begin with.

Ask what you deliberately kept, not what the browser held. Deliberate keeping is the category with the longest life, the widest spread and the least attention, and it is entirely within your control at the moment you do it.

The moment to think about it is when you save something, not later. Later is when you have forgotten what you saved, which is the point of saving it.

Two of the tiles count the published addresses and two count this page. Nothing here can observe your machine, and a panel about persistence that showed figures about your storage would be showing figures it could not possibly have.

The address counts are relevant in the way described above: they are the size of the thing most likely to persist. The page counts are the board doing what it does everywhere, which is measuring the only two things it has.

Everything above assumes a machine you are the only person using. If that is not true, the whole subject changes shape, and it changes in a direction that no browser setting addresses.

A shared machine holds whatever was saved on it, and the person who saved it is not the only person who can find it. Browsing state, saved files, a clipboard, a screenshot folder, an automatic backup configured by somebody else years ago. None of that is exotic and all of it is ordinary computing.

The board is not going to hand out household advice. The one thing worth naming is that the question is not what a browser retains, it is who else uses the machine, and that second question is the one people skip because it feels like it is not about computers.

Does closing the browser end the session?

It may end your local state. Whether the service still considers you signed in is a separate question decided elsewhere.

Is clearing browsing data enough?

It handles one category. The things you deliberately saved and the things other applications copied are untouched by it.