Everything filed here is a normal habit. Not one of them is a mistake on any other website you use.

Habits that do not travel The check afterwards

Three addresses for Mars Market, set down the way they arrived

marsautbk3di5cj75eh4dakjjrngddnjwqfdltbq2sy6cf7unzkd2bad.onion
marsautkudspgk6j23cxdtrk36ae4fpis2eoe7izu5y2rsksvmfji2ad.onion
marshjhtog245vzjzcicnmv2ci6yljibvdm4pngq5kmkfvcutppboxad.onion

They carry no name, no number and no order of preference. This site never opens them, so it has nothing to tell you about what any one of them is doing at this moment, and you will not find a light, a percentage or a date of checking anywhere on it.

Home Habits from paying for things Keeping the receipt

Habits from paying for things ยท habit 22 of 40

Keeping the receipt

Anyone who has ever had a delivery go missing keeps confirmations. It costs nothing, it takes a second, and once in a while it saves an afternoon. The reflex fires here too, and what it produces is a different sort of object.

What it does everywhere else

A receipt is the artefact that ends a dispute. It carries a reference, a date and an amount, all three issued by a party that both sides accept, which is precisely why it settles things. Producing one usually stops the argument before it starts. People who keep them get better outcomes than people who do not, and everybody learns this the hard way once.

What it does on this one

A confirmation page from a market is not that. Nothing on it was issued by a neutral party, nobody outside the transaction has any obligation to accept it, and there is no forum where producing it changes an outcome. What it does have is a full description of an order, a time, sometimes an address, and the fact that you were the one looking at it.

The habit

You save the confirmation screen so that you can prove later what happened.

Why it is automatic

Every institution in your life has trained you to do this and most of them have told you so in writing. Keep your receipt for warranty purposes. Retain this for your records. Proof of purchase required. The wording varies and the instruction does not, and the people giving it are not wrong.

The reinforcement is uneven, which makes the habit stronger rather than weaker. Ninety-nine confirmations are never looked at again and the hundredth saves a serious amount of money or a serious amount of time. Intermittent reward is the most durable kind of training there is, and this one has been running since your first paper receipt.

It is also cheap. A screenshot is one key. Saving a page is one menu item. Nothing about the act feels like a decision, and because it costs nothing people do it reflexively rather than deliberately, which means they do it without asking what the file is for.

What it actually does here

The file lands wherever your system puts screenshots, which on most setups is a folder that already syncs. That is the default on current phones and on a good number of desktops, and the sync happens without a prompt because it was agreed to at setup time and never mentioned again. The record you meant to keep locally is now a record kept somewhere with an account attached.

The name gives it away before anyone opens it. Systems name screenshots by date and time, and people rename them into something they can find, which means the useful name is a description. A file called after what the order was is readable in a listing, in a search index, in a backup manifest and in a preview pane, without the file ever being opened.

A saved page is worse than an image in one specific way. It brings the page structure with it, and often the addresses, scripts and references embedded in the markup, so the saved copy carries more than what was visible on screen. An image carries what was on the screen, which on a confirmation page is usually the whole story anyway.

The last part is the awkward one. The file is evidence about you and nobody else. It contains your order, your timing and your session. It cannot compel anyone to do anything, because there is nobody it can be shown to who has an obligation. It is a one-sided record, which is the opposite of what a receipt normally is.

The record that is useful and the record the habit makes

There is a genuine reason to write something down after an order. If a delivery does not arrive, you want to know which order you are talking about and roughly when it was placed. That is a real need and pretending otherwise would be dishonest. The question is what shape it should take.

The useful version is short, opaque and offline. A line on paper with a made-up reference and a date is enough to reconstruct which order you mean, and it says nothing to anyone who finds it out of context. The version the habit produces is long, descriptive and online, because a screenshot captures everything on the screen without asking which parts you needed.

That is the whole difference. Not privacy against convenience, but a specific record against a complete one. The habit was trained on situations where complete was free and useful, since nobody was ever going to read your receipts except you and a shop assistant.

A receipt works because a third party stands behind it, and here there is no third party to stand behind anything.

Keeping receipts is not paranoia in either direction

It would be silly to treat receipt-keeping as a bad habit. It is how people run households, claim warranties, do their tax and hold companies to what they said. Somebody who saves confirmations is somebody who has been paying attention for years, and that instinct is worth keeping intact for everywhere it works.

What changes here is only the audience. Everywhere else the saved file is a card you can play. Here it is a card that sits face up in a folder and can never be played, since the reversal machinery covered in expecting somebody to refund it does not exist to play it against. The instinct is fine. The output has no use.

The same reasoning applies to the words people type into order forms, and putting a reference on it follows that from the other end. In both cases the fix is the same shape: keep the meaning, drop the description.

What to do instead

Decide what the record is actually for, then make the smallest thing that does that job.

  1. Write the reference and the date on paper. Paper does not sync, does not index and does not preview.
  2. If you must have a digital note, keep it in something that is not backed up, and write it in your own shorthand rather than plain description.
  3. Turn off automatic upload for the screenshots folder if you have not looked at that setting since the machine was new.
  4. Never name a file after what it contains. Names are visible in listings and search results without the file being opened.
  5. Set a point at which the note is destroyed, and destroy it then rather than when you next think about it.
  6. If a screenshot already exists, deal with it now rather than deciding to be careful in future.

How to notice you did it anyway

Screenshots are easy to audit because the system files them in one predictable place.

What readers ask about this habit

If I delete the screenshot straight away, is that the end of it?

Not necessarily. Deleting removes it from the folder, and on most setups it then sits in a trash area for a period, and if it synced before you deleted it there may be a copy elsewhere with its own retention. Dealing with it quickly is still much better than not, it is simply not instant.

Is a written note on paper really better than a file?

For this purpose, yes, and not for mystical reasons. Paper is not searchable by anything but a person holding it, it does not replicate itself, and it does not get carried around by default. It is also easy to destroy completely, which files are not.

What if I need proof for a dispute with a seller?

Whatever dispute process exists lives inside the market and works from its own records, not from your image file. Your copy is not what convinces anyone. The work machine section covers a related version of this reflex, where the file lands on equipment somebody else administers.

Everything on this site