Publié
What Goodreads (and Readwise) Actually Do With Your Reading Data
Goodreads and Readwise both ask for your reading history, but their privacy disclosures point in different directions. Here's what each one actually says it does with your shelves and highlights.
"Goodreads" and "reading app" promise the same thing — a shelf that remembers what you've read. But they answer very differently when you ask who else gets to see that shelf. Readwise has been independent since it launched. Goodreads has been an Amazon company since March 2013, and that ownership shows up in what each service actually discloses about your data, not just in how each one feels to use.
The thought
The short version: Amazon's 2013 acquisition of Goodreads wasn't just a change of logo. In May 2013, Goodreads went back to sourcing its book metadata from Amazon after a stretch of using Ingram and other providers, tightening the technical link between the two catalogs. Then, in December 2020, Goodreads deactivated API keys older than thirty days and stopped issuing new ones — closing the door that had let independent tools read your shelving and review data on your behalf. Neither fact, on its own, tells you where your data goes today. Together, though, they describe a service that's spent over a decade folding itself into a much larger company's systems, one integration at a time.
Readwise's history runs the other way: no acquisition, no parent company, one product that does one thing — hold onto the highlights and notes you save from what you read. That doesn't make either service's disclosures more or less true. It just means the two are answering slightly different questions when they tell you what they do with your data — one from inside a company whose core business is advertising and retail, the other from a company whose only product is the thing you're using.
The longer version
What Goodreads discloses on its own App Store page
You don't need a leaked memo to see where Goodreads' data goes — Apple makes developers disclose it. The App Store privacy label for Goodreads lists data collected for the developer's own advertising and marketing: your email address and name, a user ID and device ID, product-interaction data, and advertising data. Separately, it lists a much wider bucket of data linked to your identity — purchase history, contact information, the reviews and content you post, your search and browsing history inside the app, device identifiers, and diagnostic data.
Apple sorts every disclosure into three tiers, and they're worth knowing regardless of which app you're looking at. Data used to track you is data combined with information from other companies' apps and sites for targeted advertising, or shared outright with data brokers. Data linked to you stays inside the developer's own app but is still tied to your identity. Data not linked to you is the closest thing to anonymous — nothing ties it back to you off-device. Goodreads' label places a meaningful share of what it collects in that first, most consequential tier.
None of this requires speculating about what happens behind the scenes. Your shelving and reviews sit in the same corporate ecosystem as your Kindle activity, your Audible listening, and your Amazon purchase history — that's the documented shape of the integration, not a guess about it. If you want the fuller comparison of what "owning" a reading library means across the two companies, we've written about two very different ideas of owning what you read.
What Readwise says in its own privacy policy
Readwise's privacy policy makes a direct claim: "Our business model has never been to sell data and it never will." It goes further, adding that this commitment "does not give us the right (nor do we want the right) to sell your information to a third-party." What it actually collects is narrower than Goodreads' advertising-linked categories — account information, the highlights and titles you save from Kindle, Apple Books, newsletters, and the web, plus ordinary usage analytics and the integration tokens you connect (Notion, Evernote, and similar tools).
It's a real, checkable commitment, worth taking at face value. It's also narrower than it might sound: "we don't sell your data" says nothing about how long the company keeps it, who can subpoena it, or what happens to it if Readwise is ever acquired the way Goodreads was. The highlights you save still live on Readwise's servers, under a policy that — like any company's — can be updated going forward. It doesn't say what happens to years of saved highlights if the company changes hands or shuts down, which is a different question worth asking before you build a reading habit around any cloud service. We've looked at what happens to your highlights when a reading app shuts down if you want the fuller version of that question.
A useful corollary
Reading either policy closely, before committing years of shelving and highlighting to it, is worth doing. Both Goodreads and Readwise put their disclosures in writing, in places you can go check for yourself right now — that's more than most services offer. But there's a policy that requires no trust at all to evaluate: the one that never sends your reading data anywhere in the first place. Margina has no account, no server, and no ads — there's no privacy policy about your reading data to parse, because there's no reading data leaving your phone for a policy to govern. Backups go to your own iCloud or Drive, not to us, so the choice of who to trust with them stays yours.
If keeping a reading history that never gets uploaded anywhere sounds better than the alternative, that's really the case for a private reading journal with no account required — the same idea, applied to the shelf as well as the highlights. Margina is on the App Store and Google Play if you want to try it.