Adobe's Digital Editions e-book and PDF reader sends reading logs to company servers in plan text; Adobe says it's working on a fix
Adobe's e-book reader sends your reading logs back to Adobe—in plain text [Updated] — Adobe even logs what you read in Digital Editions' instruction manual.
Context & Ripple Effects
The disclosure lands on top of Adobe's worst security year on record: the October 2013 breach that exposed 2.9 million customer records and source code, followed by the November revelation of how badly Adobe had botched password storage. Now the same company's e-book reader is caught shipping unencrypted telemetry off every user's machine.
The breadth of pickup is notable for a single-app finding — EFF, The Register, Techdirt, PC World, Gigaom and Consumerist all ran it the same day, which suggests the story is being read less as an Adobe bug than as a case study in what desktop software quietly reports home. That Adobe confirmed both the logging and the pending fix keeps this a credibility problem rather than a denial fight.
First-order effects
- Every Digital Editions user's full reading history — including pages of the instruction manual itself — has been transmitted to Adobe servers without encryption, exposing titles and habits to anyone intercepting the traffic.
- Adobe is now committed publicly to shipping a fix, turning a routine telemetry design decision into a named engineering priority with press attention on the timeline.
Second-order effects
- Libraries and publishers who distribute DRM-protected e-books through Digital Editions face pressure from patrons over a client they didn't choose but must use to read borrowed books — the app's monopoly on Adobe DRM makes it everyone's problem.
- Rival e-book readers get a trust-based selling point, and privacy advocates like EFF gain a concrete artifact to cite when arguing that reading behavior deserves stronger protection than browsing history.
Third-order effects
- If the pattern holds, unencrypted telemetry in consumer desktop software becomes a standing legal and reputational liability, pushing vendors toward encrypting or minimizing what they collect by default.
- For e-book ecosystems specifically, the episode strengthens the argument that DRM-required readers should be treated as trusted handling of patron records, not just content playback — a governance question libraries will keep raising.
The trend: Desktop applications' silent phone-home telemetry is colliding with rising privacy expectations, and vendors are learning that what gets collected matters as much as whether it gets breached.