What If You Lose It

Someone we know left a notebook on a train. Fourteen months of it, gone between one station and the next. The interesting part came afterwards: they couldn't work out how bad it was. Sitting down to inventory the loss, they could remember perhaps six entries out of several hundred — not the words, just the fact that those evenings had been written about at all.

What was actually lost wasn't the text, since the text was already unreachable in every practical sense. It was the feeling of having a record. That's a real thing to lose, and worth being precise that it's a different thing from losing the pages.

The weight of a page that has to last

Give a page a future and it starts making demands.

If this notebook is going to survive you, then the handwriting matters, and the first sentence matters, and the standard of thought on display matters, because someone will read it — even if that someone is only you at sixty. So you write the presentable version. Out goes the pettiness, the repetition, the fourth night in a row of the same worry because it looks bad written down four times.

Every one of those is the anticipated reader doing the editing, and that reader is a censor with excellent manners. Permanence is the biggest single cause of the shapes you write around without noticing. The page that will be destroyed on Sunday gets the honest version, because there's no one left to manage.

That's the trade at the centre of this: durability costs candour. Not always — but often enough that it's worth choosing rather than drifting into the expensive option by default.

A page that will be read behaves like a document. A page that will be lost behaves like thinking. You can have either, and it's worth choosing on purpose.

What is actually lost

An honest accounting, because the fear is larger than the event.

Most of it you had already lost. An unread archive is functionally identical to a missing one. Eleven notebooks nobody has opened in three years are available to you in principle, which is the relationship you have to most of a library. Losing them takes your access from theoretical to nil, and that difference is smaller than it feels.

The bit you'd genuinely miss is small and specific. Nearly always a handful of entries around one period: the weeks after a move, the year a child was small. People who've lost journals can name the passage they'd want back within ten seconds, and it's rarely more than a few months of the run.

The rest is symbolic, and symbolic isn't nothing. Something you were building is no longer being built. That's a real deprivation — but it's a loss of continuity rather than content, and continuity can be restarted tonight.

Two honest positions

There are two coherent stances on backup, and the misery lives entirely in between them.

Both are fine. What isn't fine is the default, I sort of hope it lasts — all the weight of permanence, none of the protection. You write carefully for an imagined future reader and lose the lot to a dropped phone anyway: paid the price, didn't get the goods.

If you pick the first, here's the whole of it:

1. 1

   Pick the copy that leaves the building

   A copy is only a copy if it survives whatever kills the original. Same phone, same account, same app is not a second copy. Name the disaster, then check whether both copies are inside it.

2. 2

   Put it on a date, not on an intention

   Once a year is enough, and short enough to actually happen. Attach it to something that recurs — the week you do the tax, a birthday. Backup plans that depend on remembering don't survive a normal year.

3. 3

   Check one old copy, once

   Open something from two years back and confirm it still opens. Ninety seconds, and it catches the format you can no longer read, the export that was empty, the drive that died quietly in 2024. An unverified backup is a belief, not a backup.

Where our own journal stands

We should be specific about our own product, because a piece like this that stays vague about the thing hosting it isn't worth much.

The journal on this site keeps your entries under your own account. They aren't shown to other people using the site, don't appear in the community pages, and feed nothing public.

Now the limits, plainly. It is not end-to-end encrypted. Your entries sit on a server we operate, which makes them technically readable by the operators of that database — us — and by anyone who ever compromises it. We don't read them and we've built nothing that surfaces them anywhere, but "we don't" is a policy rather than a mathematical guarantee. If something would be genuinely damaging in someone else's hands, it shouldn't go into this journal, or into most journals like it.

There is also no lock on the page. No passcode, no PIN, nothing between an unlocked device with your session on it and your entries. If someone else uses your phone, they can open your journal. True of an enormous number of apps, and still worth saying out loud.

And it is not permanent. No digital archive is, ours included. Services change, companies stop, accounts get lost, and a site that exists cheerfully today is no promise about 2039. Anyone who says otherwise about their own product is describing their intentions.

So: export anything you'd mind losing. There's a download button under the editor and on each entry in the archive — an image and a PDF of the page, one entry at a time. It is not a bulk export; a year is a year of clicks, and we'd rather say so than let you discover it. Keep those files somewhere that has nothing to do with us, and treat whatever lives only on our server as convenient rather than safe. An app ought to be the one telling you that.

The notebook you burn on purpose

Which brings us to the option nobody offers, and it has a long history: write it, keep it a while, destroy it deliberately.

Not in anger, and not as a gesture about the contents. As a storage decision made in advance and known while you write — which is what makes the writing different. A page definitely going into the fire in April is the freest you'll ever produce, because nothing on it has to be defensible.

The version we'd suggest: keep the run for a season, read it once, move two or three lines somewhere permanent, destroy the rest. The reading is what makes it a practice rather than a discard. That transfer yields less than you expect — the same lesson three lines a night teaches from the other end.

Writing lighter

Nobody needs a policy. What changes is the sentence you write tonight. If the record is disposable, the page gets the unpresentable version — the repetition, the pettiness, the line you'd cross out — which is better writing and better information both. If it's an archive, back it up properly and stop half-worrying: the half-worry was costing you candour and buying you nothing.

The person on the train got a new notebook the same week and started again on the Tuesday. They say the second one is better, and the explanation was short: they already know how this ends, so they've stopped writing it for anybody.

The evening is warm here.