MarginaGet Margina
Articles

Published

What Cloud-Based Reading Apps Actually Collect

Cloud reading apps sync your library, your place in a book, and your highlights to a server. Here is what they can collect, and what local-first changes.

The word "cloud" in a reading app does quiet work. It means your library, your place in each document, and the notes you write in the margins don't stay on your phone. They live on a server somewhere, tied to an account — and there, syncing them to your next device and collecting them run through the same pipe. None of this is sinister, and none of it belongs to one app in particular. But it's worth understanding plainly, because choosing between a cloud app and a local one is really a choice about where your reading life is kept.

What "cloud-based" actually means for a reading app

A cloud-based reading app keeps the important state of your reading on the provider's servers, tied to your account: which books and documents you have, where you stopped in each one, and every highlight and note you make. That's what lets your annotations reappear when you open the app on a new tablet.

The structural point is simple. Once that data sits on someone else's infrastructure, the provider can reach it. As the general description of cloud computing puts it, the service operator can access data held in the cloud at any time. Whether they do, and for what, is governed by a privacy policy — a document the provider writes and can revise. The exposure isn't an accusation; it's a property of the design. "Synced" and "private" are not the same word.

Why it matters

Reading data is unusually revealing. The passages you highlight and the notes you scribble are closer to your real opinions than anything you post in public, because you wrote them only for yourself. When those annotations sync, they're stored on a server the way your email passes through a mail provider — no longer as private as a pencil mark in a paperback, as one survey of ebook privacy describes it.

There's a settled standard for how little an app ought to gather. European data-protection law calls it data minimisation: under Article 5 of the GDPR, personal data should be "adequate, relevant and limited to what is necessary" for the purpose at hand. Mozilla's privacy principles say the same thing in plainer words — no surprises, collect only what's needed, give people control. Most reading apps land somewhere short of that line, and the gap is rarely visible from the bookshelf screen.

Where you'll see it

You won't see most of it at all, which is rather the point. Technically, a synced reading app can record when you open and close it, how long each session runs, the interval between page turns, the words you look up, the passages you share, your theme and settings, and of course every highlight and note. Coverage of e-reader privacy notes that platforms such as Kindle log page turns, dictionary lookups, highlights and notes by default, that some newer e-readers add location, and that a subscription title is often counted as "read" once you pass roughly 15% of it. Opt-out controls exist on Kindle and Kobo, but they're partial, and collection is the default posture.

Sideloading your own files doesn't exempt them. Emailing yourself a contract, or sending a public-domain EPUB from Project Gutenberg to your account, feels like keeping the document to yourself — but the moment you open and sync it, it's processed like everything else in your library. Apps like Goodreads and Readwise are built around capturing and centralizing what you read; that's their function, and for some readers it's genuinely useful. The question is whether you want it to be the default for everything you open.

How Margina handles it

We built Margina the other way around. There's no account, no server, and no ads — so there's nothing to opt out of, because nothing is collected. Your documents, your reading position, and your margin notes stay on the device.

In practice, you send a document straight in from the share sheet — a PDF, an EPUB, a Word file, a Markdown export — and Margina renders it without conversion or upload. You highlight and write notes that stay attached to the document, and the app reopens each file exactly where you stopped. Backups go to your own iCloud or Google Drive, under your control rather than ours. For a researcher working through a stack of papers, a lawyer marking up a contract, or someone who just AirDrops chapters to their phone and wants the reading kept private, the data never leaves in the first place. The honest trade-off: there's no cross-device sync, by design. Privacy here costs you the convenience of seeing the same highlight on three devices.

A short checklist before you trust a reading app

Four plain questions tell you most of what you need to know. Does it require an account? Where do your highlights live — on the device, or on a server? Can you back up to storage you actually own? And what does it collect by default, before you change a single setting? If the answers are vague, the cloud is doing more than syncing.

There are more essays like this one in the Margina journal, and Margina itself is on the App Store and Google Play.

Frequently asked questions

Do reading apps really track what I highlight?

They can. Highlights and notes are part of the data a synced app stores on its servers so they can follow you between devices. Whether a given app analyzes them depends on its privacy policy, but technically the annotations leave your device.

Are my own PDFs and EPUBs private if I sideload them?

Not automatically. A file you email or send to a cloud reading account is processed like any other document once you open and sync it. Keeping it private takes an app that renders it locally, without uploading it.

Is a cloud reading app unsafe to use?

No — "unsafe" is the wrong frame. The point is awareness: cloud apps trade some privacy for the convenience of sync. If you understand what's collected and you want sync, that can be a fair exchange.

What makes a reading app local-first?

A local-first app keeps your documents, reading position, and annotations on your device instead of on a server, and it usually works without an account. Backups, if any, go to storage you control, such as iCloud or Google Drive.

How can I tell what a reading app collects before I trust it?

Check whether it needs an account, read where it says highlights and reading data are stored, and look for whether backups go to your own storage. An app that collects nothing has nothing to disclose.