MarginaGet Margina
Articles

Publié

The Case for Keeping a Private Reading Journal, No Account Required

A private reading log doesn't need an account to stay private. It needs a place with no server-side default that someone else can quietly change later.

The thought

A record of what you've read is worth keeping. It isn't worth performing. Those are two different activities, and most reading apps quietly collapse them into one — a "currently reading" shelf, a progress bar your friends can see, a feed that turns a private habit into a small, continuous broadcast.

This isn't a new idea dressed up in privacy-app language. A private reading journal with no account is closer to the oldest way readers have kept track of what they've read. For centuries, readers kept commonplace books — private notebooks organized by subject rather than by date, where a passage worth remembering got copied down for no one but the person doing the copying. John Milton kept one. So did Virginia Woolf, in her own less formal way. Not because anyone was going to see it. Because the record itself was the point.

Commonplace books weren't diaries, and that distinction matters here too. A diary is chronological and introspective; a commonplace book was organized by subject instead — a passage on grief filed near other passages on grief, regardless of which book or which year it came from. The organizing principle wasn't "what happened to me today" but "what did I read that I want to be able to find again." A private reading log does the same job, four centuries later, with a phone instead of a chest of index cards.

That's the distinction worth sitting with: a reading log and an audience are two separate things. What happens when you keep the first without the second is worth thinking through before you pick where to keep it.

The longer version

An audience changes what gets written down, even when the writer doesn't notice it happening. Writing without an anticipated reader lets you notice things rather than curate them — the difference between jotting down that a chapter genuinely unsettled you and marking a book "currently reading" because the cover looks good on a shelf. A private page doesn't have to be edited for presentation. A public one, even a small and well-intentioned one, always is a little.

And this isn't a hypothetical slide. Reading-tracking platforms tend to drift toward public by default over time, usually with good intentions behind it. In 2020, Open Library switched new accounts' reading logs from private-by-default to public-by-default, citing user demand and the fact that competing services already offered shareable lists. By then the feature had drawn nearly a million readers and 1.8 million logged entries — real appetite for tracking what you read, and real evidence that a private setting inside someone else's system can be revisited whenever the platform's incentives shift. Open Library kept the old private option available and said so plainly. Not every service will.

None of this means Open Library did anything wrong. It means a server-side default is, by definition, something the server controls — which means it can be changed by someone other than you, for reasons that have nothing to do with what you were trying to keep private in the first place. You opted into a private setting on day one; the platform reserves the right to revisit what "private" means on day eight hundred.

A no-account reading app sidesteps that risk structurally, rather than promising to manage it well. There's no dashboard your reading history feeds into, no setting that could get toggled in some future update, because there's no server-side copy of your log to begin with. Same logic behind owning your books as files, not app-bound records — the log lives with you, not with a company deciding what "private" means this quarter.

A useful corollary

The term for this general approach is local-first software: applications that keep your data on your own device as the primary copy, rather than treating a remote server as the source of truth. Researchers studying the approach have described seven qualities worth wanting from this kind of software — fast, works across devices, works offline, supports collaboration, lasts, stays private, and leaves you in control. Two matter most for a reading log specifically: privacy, since there's no account to breach or subpoena, and longevity, since your record doesn't depend on a company staying in business.

That second point is easy to underrate. A paper commonplace book outlives its author by default — it just sits on a shelf, legible to whoever finds it, for as long as the paper holds up. A cloud-based reading log lasts exactly as long as the service does, and not a day longer. When a reading app shuts down, gets acquired, or quietly sunsets a feature, the log usually goes with it. Not because anyone meant to delete your reading history — because it was never really yours to begin with. It was a row in someone else's database.

If local-first is the architecture, the practical version of that idea, for Margina, is simple: you can back up your reading library to your own iCloud, on your terms, without handing a copy to anyone else in the process. Margina reads PDFs, EPUBs, Word documents, and plain text without asking you to sign in first — the reading log stays exactly where the books do, on the device you're actually reading on.

None of this is about having something to hide. It's about keeping the record answerable to no one but you, the same reason readers have kept private reading notes for four hundred years. The habit hasn't changed. Only the tools have — and a private reading journal, no account required, is just the current version of the oldest one.