I made a PDF last week. Nothing dramatic. I opened a document on my laptop and saved it as a PDF document to my local drive. No third-party service. No cloud storage. No upload. I wrote something, and I saved it as a file. Then I opened it with Adobe Acrobat Reader.
Before I could do anything with the file, Acrobat communicated with Adobe’s infrastructure. Not to fetch the file, which was already on my machine. Not to check for an update, which I had not requested. The communication occurred during what appeared to be a purely local action.
The feeling that followed was a low-level unease at the gap between what I thought was happening and what was actually happening. I believed I was reading a document. What was also happening was that my software was in conversation with a company I thought I had not permitted to be involved.
The Same Pattern, Again
I have written before about what it means to no longer own the things I pay for. Music moved to streaming. Software moved to subscriptions. Ownership faded before most of us fully noticed. The shift was gradual and the language around it stayed friendly. Access. Flexibility. Convenience.
What I described in that piece was the financialization of everyday life. The conversion of things I used to own into services I now rent, where control sits with the provider, and risk sits with me. To me, the PDF reader experience is a variation on the same structure. I did not knowingly subscribe to a service. I installed a tool. I expected the tool to work within the boundaries of my device. What it actually did was maintain a relationship with its manufacturer during normal, local use.
For many users, this tradeoff appears to be acceptable. Convenience often outweighs concerns about invisible infrastructure. The problem is that people often make this choice without realizing they are making it. To me, a tool should do what you tell it to do. A service operates within an ongoing relationship, one that typically involves data exchange, monitoring, and terms you did not fully negotiate. When installed software behaves like a service without clearly presenting itself as one, the user loses something real: the ability to understand their own digital environment.
What Was Sent, and Why
Adobe may have legitimate reasons for some of this. License verification is real. Cloud features require connectivity. Some functionality may genuinely depend on server-side processing.
Yet, the experience of opening a locally created file and watching the software reach out to a server before allowing me to work with the document seems to respond to another need than mine. The absence of explanation is part of what makes it uncomfortable. You are not told what was sent before it is sent, or why it was needed.
This behavior may be legal, as it is likely disclosed somewhere in documentation that most people will never read. That does not make the unease unreasonable. It makes the unease more precise: the problem is not that the data exchange happens, but that it happens as a somewhat undeclared default while the user assumes otherwise.
This is the same logic that made the subscription economy so effective. Most people accepted streaming because the convenience was real and the cost of reading the fine print was high. The shift in control happened quietly, wrapped in something that felt like an improvement.
Alienation at the Point of Use
There is a word for the condition of being separated from something that should be yours: Alienation.
Beyond its classical economic definition, alienation can be understood as a crisis of functional transparency. It describes the condition of being separated from the inner workings of our own environment. When we no longer understand how our tools function, the objects we use cease to feel fully ours. It makes us dependent on specialized, external interests to navigate our daily lives.
What I experienced with Acrobat is alienation at the point of use. I was separated not from something I was making, but from something I already had. The file was mine. The machine was mine. Yet a third party was inserted in the interaction, silently, without my awareness or meaningful consent.
This is not a side effect of technical complexity or an oversight in the design. Software that communicated only when necessary, and only with the user’s clear knowledge, would give users more control and companies less. Intentional or not, the result is a system that gives users less control and companies more.
This is where the parallel to the rental economy becomes most visible. In my post, Renting My Own Life, I argued that what gets called the sharing economy is better understood as a rental economy with warmer language. Platforms control the relationship. Individuals carry the risk. The language of empowerment covers a structure of extraction.
The same pattern appears here, compressed into a single interaction. I thought I had a tool. What I had was a tool that also maintained a relationship I did not really choose, on terms I did not negotiate, in a transaction I did not know I had agreed to.
A Small Response
My reaction was not to write a policy paper. It was to stop using Acrobat for basic reading, and eventually to build something minimal for myself: a browser-based PDF reader that processes files locally, sends nothing anywhere, and disappears when you close the tab. It is limited by design. It reads PDFs and does nothing else.
I mention this not as a solution to a systemic problem, because it isn’t one, but because the act of building it clarified something. The reader works without a server relationship because reading a PDF does not require one. The server calls in standard PDF software are not a technical necessity. They are a choice.
Choices that normalize quiet data transmission, made consistently across an industry, reshape what users come to expect as normal. Enough of those choices, and the expectation of a local tool that stays local starts to feel naive rather than reasonable.
Why the Unease Is Worth Keeping
There is a version of this conversation that gets dismissed quickly. Users agreed to the terms. The data is anonymized. Everyone does it. You can turn it off in settings.
These responses are not exactly wrong, but they consistently redirect attention away from the underlying question. Not whether the behavior is technically permitted, but whether it reflects an honest relationship between software and the people who use it.
Feeling uneasy when your PDF reader contacts an external server before letting you work with your own file is not technophobia. It is acknowledging that something happened which was not clearly disclosed in terms most users would recognize as consent. It is also the feeling of being disconnected from your own tools by an interest that was never clearly announced.
That feeling deserves to be taken seriously. Not because every instance of it reveals wrongdoing, but because it is pointing at a genuine and growing gap between what users believe their software does and what it does. Closing that gap requires more than better privacy settings. It requires a different default: software that stays within its stated role unless a user actively chooses to extend it.
That default is unlikely to change. Much of the modern digital environment is built around reducing user sovereignty in favor of ongoing extraction. In a system designed for such a structure, the unease is not a bug in your perception.
AI Transparency Statement: The author defined the core concepts, direction, and arguments for this article. AI tools, including ChatGPT, Gemini, and Claude, assisted with editing, adaptation, and research. All content was reviewed, verified, and finalized by the author.
Leave a Reply