Habits the browser taught you · habit 02 of 40

Letting the browser remember

A strip slides down from the top of the window and asks whether you would like it to remember this. The answer has been yes for years and nothing bad has ever come of it.

What it does everywhere else

On the ordinary web this is one of the great time savings of modern computing. A delivery address typed once fills every checkout afterwards. A phone number entered on a slow form on a train never has to be entered on one again. People fill in fewer boxes, abandon fewer forms and make fewer typing errors in the fields where errors matter.

What it does on this one

Here the same yes writes a row into the same database, and the row records where it came from. Later, on a completely unrelated site with a similarly named field, the stored value is offered back as a dropdown suggestion. That dropdown does not care who is looking at the screen at the time.

The habit

You say yes to the save prompt, because saying yes has been the right answer everywhere else for years.

Why it is automatic

This is not laziness, it is arithmetic that already worked out. Anyone who fills in forms online has done the sum without noticing: yes costs one click and buys back a hundred small tasks. Nothing in that trade has gone wrong on a shopping site or a council form, so the reflex has never been given a reason to weaken.

The prompt itself is doing work too. It appears as the task finishes, when attention has already moved on, and it puts the agreeable answer under the cursor. That is ordinary interface design rather than a trick. A prompt that was easy to refuse would be refused by people who wanted to accept it.

Add to that the fact that almost nobody has seen where any of it lands. Saved values do not present themselves as a file. They appear as a dropdown at the moment they are needed, which makes them feel like a property of the form rather than a record of your own.

What it actually does here

Three separate stores are usually involved and they behave differently. Passwords go to the manager vault. Addresses, names, phone numbers and card details go to an autofill store. Loose form values, meaning anything typed into a plain text field, go to a third list that is the least visible of the three and the least often cleared.

All three are files in a profile folder. That folder has a predictable path and survives the browser closing, the machine sleeping and in most cases a reinstall over the top. Deleting history does not necessarily touch any of it, because history and form data are different stores cleared by different checkboxes.

Sync changes the scale rather than the kind. The same rows exist on every device signed into that profile, and they arrive without a further prompt. A value typed once on a home machine can be offered on a phone in a meeting, and the phone gives no sign of where it learned it. What a phone adds is set out in the phone section.

The suggestion behaviour is the part people are least ready for. Saved form values are usually matched on the name of the input field rather than on the site, so a value typed into a field with an ordinary name is offered on any other page with a field of the same name. It appears on the first letter, in front of whoever is watching.

The prompt is a piece of design

It is worth being fair to the people who built the save prompt. A feature nobody discovers is a feature that does not exist, and their answer was to offer it at the instant its value is obvious. That is why it appears after a successful sign in rather than before, why the accept button is the emphasised one, and why the wording asks about convenience rather than about storage.

The consequence is that refusing takes a deliberate act and accepting takes none. Over years a person builds a very high rate of yes and no memory of any individual instance. Nobody can tell you what their browser has saved. That is not carelessness, it is what the interface was optimised to produce.

Where the dropdown turns up next

The uncomfortable case is not the machine being seized. It is ordinary: a shared laptop, a form on an unrelated site, and a suggestion list dropping open with something on it that has no business being visible. Autofill has no notion of context or audience and was never asked to have one. It has a field name and a stored value and does the obvious thing with them.

A username typed here, offered later on any page whose sign in field carries the same common name.
A recovery phrase or a note pasted into a plain text box, kept in the form value list long after the page is gone.
An address saved for one purpose, offered on a delivery form in front of somebody standing over the screen.
A card entry synced from another device, appearing on a machine where you never entered it.

What to do instead

The workable position is not distrust of your own browser. It is keeping this activity out of the profile that carries everything else.

Use a profile for this with autofill, form saving and address saving switched off from the start, so there is nothing to decline later.
Refuse save prompts explicitly rather than closing them, since a no is usually remembered for that site and a dismissal is not.
Turn off form value saving separately from password saving, since they are different settings and clearing one leaves the other.
Keep sync off here, and look at what is already in the account first, because removing a device does not always remove the rows.
Type into a plain text field only what you would be content to see suggested elsewhere, and paste the rest.

How to notice you did it anyway

Everything saved this way is listed somewhere in settings, and the lists are short enough to read properly rather than skim.

Open the autofill settings and read the saved addresses and payment entries one by one instead of glancing at the count.
Find the form data list, usually a separate screen from history, and see what is in it.
Click into a plain text field on a scratch page and press the down arrow to see what the browser offers unprompted.
Check the sync status on each device, then confirm the lists look the same on all of them.
After clearing anything, reopen the browser and look again, because some stores are only written out at shutdown.

What readers ask about this habit

Does clearing browsing history remove saved form values?

Usually not on its own. History, cookies, passwords and form data are separate stores with separate checkboxes, and the default selection does not always include form data. Open the list itself afterwards to confirm.

Is a saved address really a problem if it is just a street?

The question is not what the value is but where it can appear. A saved address is offered on any later form that asks for one, on any device holding the profile, in front of whoever is present.

Why not just use a guest window every time?

It does help, because most of these stores are not written from one. It is not complete, since downloads, some extension state and anything typed into an already open profile still land normally. It works as one layer rather than the whole answer.