SReader Reading Notes
Why Your Reading App Knows Too Much About You
Cloud reading apps collect your highlights, reading habits, and device data. A private PDF reader that processes files locally keeps your intellectual life yours.
Every article you save, every highlight you make, every page you abandon mid-read. That data flows to servers you don't control. The reading app on your phone or laptop knows what time you read, how far you got, what topics interest you, and which passages you found worth marking. It may know what you searched for, how long you spent on each section, and what you skipped entirely.
Your physical bookshelf doesn't phone home. So why should your e-reader?
Reading is one of the most personal things we do with screens. The books and articles we choose reveal our beliefs, our struggles, our career moves, our health concerns, and our aspirations. Yet the default architecture of modern reading apps treats this information as raw material for someone else's business. There is a better way: SReader, a local-first reading tool that keeps your library on your device and out of the cloud.
What Cloud Reading Apps Actually Collect
Reading services that sync to the cloud need to collect data to function. But the scope of collection goes well beyond what most users would expect.
Readwise Reader's privacy policy, last revised December 20, 2024, explicitly confirms that the service collects "titles, metadata, tags, highlights, and annotations from books and articles" you save. That covers content pulled from Amazon Kindle, Apple iBooks, Instapaper, Twitter, subscription newsletters, RSS feeds, email, websites, PDFs, and EPUBs. The policy also lists device data including IP addresses, unique advertising identifiers, and general location, plus online activity data such as pages viewed, time spent, and browsing history. Layered on top: cookies, local storage, web beacons, and Google Analytics.
The policy is direct about one more thing: "We currently do not respond to Do Not Track or similar signals."
Pocket and Instapaper follow similar patterns. Both collect URLs, timestamps, reading completion rates, tags, and highlight content. Even read-it-later services that don't sell ads still amass a detailed behavioral record of what you read and when.
Then there is the question of who can actually see your data. Readwise's own FAQ addresses end-to-end encryption plainly:
Do Readwise or Reader support end-to-end encryption? No. Readwise and Reader are consumer softwares optimizing for user experience over enterprise compliance. If you're dealing in matters of national security requiring NSA-level encryption, you should definitely not save anything containing your state secrets to Readwise or Reader (or any cloud-based software, for that matter).
That is an honest answer. It also means company staff technically have access to everything you store. For anyone reading sensitive legal documents, medical records, or confidential work material, that matters.
Your Reading List Is a Behavioral Fingerprint
Individual data points seem harmless. A saved URL here, a highlight there. But assembled together, your reading history forms an intimate portrait of your intellectual life.
Medical articles reveal health concerns. Legal documents reveal disputes. Professional reading reveals career moves. The books on your nightstand and the articles in your queue expose what you care about, what you worry about, and what you are trying to become.
This is not abstract. PCMag reported in February 2026 that "many apps quietly harvest a ton of data they don't need, mostly so that data can be packaged and sold, or used for advertising." The FTC has found that data brokers "combine and analyze data about consumers to make inferences about them, including potentially sensitive inferences."
A new dimension has emerged. A Pocket competitor updated its privacy policy in 2023 to add "improving our AI services" as a permitted use of user data. The company said it would not train language models on private saves, but the trend is clear. Reading-app data is being eyed as raw material for AI training, and the policies are being rewritten to permit it.
The Pocket Shutdown: What Happens When Your Library Disappears
Privacy is one risk. Permanence is another.
Mozilla permanently shut down Pocket on July 8, 2025. Pocket was once the most popular read-it-later service in the world. By October 8, 2025, all remaining user data was deleted: saved articles, highlights, notes, archives. Gone.
Users who had spent years building curated libraries, annotating articles, and organizing their reading lost everything overnight. This is not a hypothetical scenario about what might happen someday. It happened to one of the most widely used reading services on the internet.
Cloud services shut down regularly. When they do, your data dies with them. Local-first reading inverts that risk. Your library lives as long as your files do. EPUB and PDF are open, portable formats that outlast any single app or company. No server sunset can take them away.
Privacy-by-Design: What Local-First Reading Really Means
The local-first software movement, articulated by researchers including Martin Kleppmann in a 2019 paper, argues that applications should store data primarily on the user's own device rather than on remote servers. Users can read and write without an internet connection. The core principle is data sovereignty: the user retains full ownership and control at all times.
Wired reported that the movement considers the cloud model fundamentally extractive. The default path for cloud software is to "monetize your users' data for resale or advertising." Local-first rejects that path at the architectural level.
This distinction matters. Privacy-by-design means privacy is not a setting you toggle on after the fact. It is baked into how the software works. If files never leave your device, there is nothing to breach, nothing to subpoena, and nothing to sell.
As GDPR, CCPA, and newer state-level privacy laws raise consumer awareness, local-first is gaining traction as a category. People are asking harder questions about where their data goes and who profits from it.
Cloud Readers vs. a Private PDF Reader
No single cloud reading tool dominates on every dimension. Each category makes tradeoffs that leave gaps.
Speed-reading tools like Spreeder and Spritz optimize for velocity but feel clinical and stressful. Cloud readers like Pocket and Readwise Reader offer convenience but require accounts, sync data, and profile reading habits. Open-source readers like Foliate and Thorium respect privacy but lack UX polish and focal-point innovation. Accessibility tools like Speechify and NaturalReader focus on audio, not visual focus.
Feature
Pocket / Readwise Reader
Foliate / Thorium
Speechify
SReader
Account required
Yes
No
Yes
No
Data synced to servers
Yes
No
Yes
No
End-to-end encryption
No
N/A (local)
No
N/A (local)
Ad tracking
Possible
No
Possible
No
Focal-point reading
No
No
No
Yes
On-device processing
No
Yes
No
Yes
Formats supported
Varies
EPUB-focused
Audio-focused
EPUB, PDF, Markdown, text, web
SReader occupies a specific niche: calm pacing plus local-first processing plus focal-point reading across all major formats. No major competitor serves these three dimensions at once.
Read EPUB Without an Account
The searches "private PDF reader" and "read EPUB without account" reflect a real and growing need. People want to open documents without creating a traceable identity, uploading files, or generating a behavioral record.
SReader processes everything on-device across EPUB, PDF, Markdown, text files, and web articles. No servers, no accounts, no data harvesting. You can read a legal brief, a medical record, a confidential work document, or a personal essay without leaving a digital trail that someone else controls.
On-device processing means no behavioral profiling, no reading-speed analytics, and no highlight databases that could be breached or subpoenaed. Files stay where they belong: on your device, under your control.
This matters for professionals handling sensitive material. It matters for anyone researching health conditions, legal issues, or personal topics they would rather not have attached to an advertising profile. And it matters for readers who simply believe that what they read is nobody else's business.
Practical Steps to Reclaim Your Reading Privacy
You do not have to switch everything at once. Here are concrete things you can do today.
Audit your current reading apps. Check their privacy policies for data collection clauses, AI training provisions, and whether they respond to Do Not Track signals. The answers may surprise you.
Move sensitive documents to a local-first tool. Legal PDFs, medical records, and confidential work material should never touch a server you don't control. A privacy-first reading app that requires no account eliminates that exposure.
Check for end-to-end encryption. Most reading apps don't offer it. If yours doesn't, assume that company staff can access your content.
Delete unused cloud accounts. If you signed up for a reading service months ago and stopped using it, your reading profile is still sitting on their server. Close it.
Transition your library to portable formats. EPUB and PDF are open formats that outlast any single app. Files you control locally survive service shutdowns, policy changes, and acquisitions.
Reading Should Be Private Again
Every book you read, every article you save, every passage you highlight is a piece of your intellectual life. It should not default to someone else's server.
Local-first reading is not just a feature. It is a philosophy that puts the reader back in control. SReader processes everything on-device with no ads, no accounts, and no data harvesting, across EPUB, PDF, Markdown, text files, and web articles. Your library stays on your device. Your reading habits stay yours.