Is Document Tracking Spyware?
By Oleh Tsyupa, Founder of PDFTrackr · Published 2026-09-14 · Updated 2026-09-14
8 min readAcross 471 validated reading sessions, 42.5% carried a viewer email address — and every one of those sat on a link whose gate had asked for it. On the 269 sessions where no gate was shown, the number carrying a name was 0.
This is the measurement that answers the question in practice rather than in principle. If document tracking worked the way the word "spyware" implies, a reading record would routinely arrive with a name on it that nobody typed. It does not: across 471 validated sessions from 393 distinct visits on 83 share links, 200 sessions carried an address, all 200 of them on the 26 links whose sender had switched an email gate on, and 0 on the 269 sessions that were never asked. An address in a PDFTrackr record is there because the reader typed it into a form that says on the page it is shared with the sender. It is a claim the reader made, not an identification the software performed, and this page says so wherever it matters.
Based on 471 validated reading sessions across 393 distinct visits, 83 share links and 74 documents, 21 Jul – 24 Aug 2026, extracted 26 Aug 2026 — measured from 17:30 on 21 Jul 2026, the moment download counting went live, so no session that could not have been recorded sits in the denominator. One visit is excluded: a single visitor on a single link produced 210 sessions and 180 download clicks on 29 Jul 2026, a pre-deploy test burst rather than a reader; that day's other 41 sessions stay in. Validated means at least one page rendered and the session was not classified as automated. A named session is one carrying a viewer email address — typed by the viewer, not verified.
If you would rather inspect a reading record than read a description of one, the live demo shows the dashboard on sample data with no signup, or you can create a free tracked link and send it to yourself to see exactly what the sender ends up holding.
What spyware actually is
The word has a settled technical meaning and it is narrower than everyday use. Across the three definitions cited at the foot of this page — a standards glossary and two US government agencies — the same elements recur: spyware is software, it is installed onto a system, in the agencies' wording the reader's own computer or phone, and it is put there without the user's knowledge — usually bundled with something else, or delivered by a malicious download. From that position it can reach whatever the device holds: keystrokes, browsing history, files, the camera, other applications' data.
Those elements are about location and concealment. What makes spyware spyware is not that somebody learns something about you; it is that a program is running on your hardware, under your account, outside your control. Analytics on a web page you chose to open meets none of that — no installation, nothing outside that page legible to it — which is also why a website's own analytics are not called spyware even though they count you. And what PDF tracking is sets out the mechanism from the beginning if you have not met it before.
The confusion is a fair one, though. Two different products are sold under the words “document tracking”: a hosted link that measures reading, and DRM, which really does ask the reader to install a viewer to enforce controls after download. DRM is not spyware either, but it is one category where software lands on a reader's machine — and if that is the distinction you came for, DRM versus document tracking separates the two properly.
Where the code runs — four categories, one question
One question separates the whole field: whose machine is the code on? Every row below is sorted by that answer and nothing else, because that is the axis the definition turns on.
| Category | Whose machine runs the code | What it can reach | Survives the browser tab closing |
|---|---|---|---|
| Spyware | The reader's own device, installed there | Anything the device holds — keystrokes, files, other applications, browsing across every site | Yes — persistence is the point |
| A tracked document link (PDFTrackr and the category) | The sender's server; the reader runs an ordinary web page | Only what happened inside that one page — which pages rendered, in what order, for how long. Automated opens are classified at session close and excluded from the counts | No software is installed. What a tracked link can leave in the browser includes what any web page leaves: the site's cookie notice stores the reader's answer, and site analytics set their own cookies on accept, both documented in PDFTrackr's Cookie Policy — and neither is how a reader is identified in the reading record |
| Website analytics on any page you visit | The site's server, with a script in the page | Behaviour on that site, and on other sites where the same third-party script is present | Usually yes, through a cookie or stored identifier |
| DRM with an enforcing viewer | The reader's own device, installed with consent | What the protected file does, and it can refuse to open it | Yes — it has to, or it could not enforce anything after download |
| An email tracking pixel | The sender's server, fetched by the mail client | That a remote image was requested — which is why mail providers that pre-load images break it | No |
The verdict on that table is ours to write and it is narrower than the question suggests: for measuring whether a document you sent was read, a tracked link is the pick, because it is the only row that answers the question without anything landing on the reader's device. Where PDFTrackr wins inside that row is the thing after the comma — the automated opens are separated out rather than counted, and the dashboard shows what the filter removed instead of quietly shrinking the number. Where a pixel wins is reach: it works in a plain email with no link for anyone to click, and no hosted document does that.
What the record holds, named field by named field
A category argument is easy to make and easy to doubt, so here is the specific product, read out of the files that write the row rather than out of a feature list.
No IP address is stored. In backend/src/services/visitIdentity.ts, the insert that creates a reading session writes ipAddressHash: null after the rest of the values are spread in, so a caller that passes one has it dropped rather than persisted. The comment beside it calls that the structural guarantee, which is the right description: it fails closed rather than relying on nobody making a mistake later.
The visitor identifier rotates daily and is then destroyed. The reader is identified by a salted hash of their address and browser string — and the salt is a random value minted fresh for each UTC day, held in Redis with a forty-eight-hour expiry and discarded afterwards. Once that salt is gone the hash cannot be recomputed from anything, so the same reader on two different days is two unrelated rows by construction. There is no cookie and no browser storage involved in it at all.
Location is a country, and it is resolved offline. backend/src/services/geolocation.ts answers with a two-letter country code from a database bundled with the application. No city is populated on that path and no request leaves our servers to ask a third party about the reader. A country is what a reader worried about being located should expect a document link to know about them, and it is the ceiling rather than a starting point.
A name appears only when someone typed one. That is the figure in the box above, and it is worth restating as a rule rather than a statistic: the email gate is something the sender switches on, the reader sees the form, and the form says the address is shared with the sender. Nothing in the record identifies a reader who was not asked.
What it does hold is the reading: the pages that rendered, the order, the time on each, whether a download was clicked, and whether the same visitor came back inside the day. That is more than most senders expect, and the right response is disclosure rather than euphemism.
The part that is uncomfortable, and what to do about it
Here is the asymmetry, stated plainly: the sender decides to measure, and the reader is not told unless the sender chooses to tell them. That is true of PDFTrackr and it is true of the category. No definition rescues it, and a page that answered “is this spyware” with a confident no and stopped there would be dodging the actual worry.
What makes it defensible is that the asymmetry is the ordinary condition of the web and can be closed cheaply by whoever set it up. A sentence in the covering email — this is a tracked link, so I can see whether it arrived and which parts you read — costs nothing, and in practice it tends to help rather than hurt, because a reader who knows a document reports back treats it as a document somebody cares about. We argue that case at length in whether you should disclose document tracking, and it is the single thing most likely to change how this feels to the person on the other end.
If you are the reader, the practical position is calmer than it sounds. Opening a tracked link is opening a web page: it can see that page and nothing else on your device, and closing the tab ends the reading session. If you would rather the sender did not know, the answer is not a privacy tool — it is not opening the link.
When Pro becomes the right choice
Everything described above is on the plan that costs nothing — per-page reading, the email gate, the exclusion of automated opens, 500MB, 50 files, 50 active share links, twelve months of history, no card. Free is the product here rather than a trial, and somebody sending a handful of documents a month never needs to pay us.
Pro becomes the right choice when the volume changes what an answer is worth. Once you are sending the same document to more than a handful of named people at a time, bulk personalised links give each recipient their own link, so the record says who read it rather than leaving you to infer it from a shared URL. Once a document matters enough that a second reading is a signal worth acting on, the return-visit alert tells you the hour it happens instead of in the next morning's digest. And once you pass fifty active links the flat account removes the ceiling. Look at the demo dashboard before deciding whether any of that applies to you.
Frequently asked questions
Does opening a tracked document link install anything on my device?
No. A tracked link opens a web page in the browser you already use. Nothing is downloaded and installed, and no software is left behind to run after you close the tab. That installation element is the one the three definitions cited at the foot of this page turn on — software installed onto a system, surreptitiously and without the user's knowledge — and a hosted document viewer meets none of it. The file being read lives on the sender's server; the page you are looking at is the only thing the sender can see anything about.
Can the sender see my IP address or the other tabs I have open?
Neither. Other tabs, other sites and anything else on your device are invisible to a page in the way they are invisible to any website you visit — that isolation is the browser's, not a courtesy. On the IP address specifically, PDFTrackr does not store one: the insert that creates a reading session writes ipAddressHash: null after every other value, so an address cannot be persisted even by mistake. The address is used once, in memory, to resolve a two-letter country code from a database bundled with the application, and no request leaves our servers to look you up.
Am I identified personally when I open a tracked PDF?
Only if you type your address into a gate that asks for one, and the gate says on the page that the address is shared with the sender. Otherwise you are a rotating anonymous identifier: a salted hash of your address and browser string, where the salt is minted fresh each UTC day and destroyed after forty-eight hours, so the same reader on two days cannot be joined up afterwards. There is no cookie and no browser storage behind it. Measured across 471 validated reading sessions, every session carrying a name sat on a link whose gate had asked for one, and none of the 269 sessions that were never asked carried one. Automated opens from mail scanners and link previewers are classified at session close and excluded from the counts, so a machine fetch is not recorded as you reading.
Is document tracking legal?
Recording how a document you own was read is ordinary web analytics applied to a file, and it sits under the same rules as analytics anywhere else rather than under anti-malware law — the questions that actually bind are proportionality, being able to say what you hold, and not misrepresenting what a link is. This page is not legal advice and the answer varies by jurisdiction and by what you collect: a link that asks for an email address is processing personal data and carries the obligations that come with that, while a bare link with no gate holds no identifier that outlives the day. The practical test that keeps senders out of trouble is whether you could tell the recipient exactly what the link records without wanting to soften it.
How can I tell whether a link I was sent is tracked?
By where it goes. A tracked document link opens a viewer on somebody's hosting domain rather than handing you a file to save, so the address bar will show a service rather than a direct file path. Beyond that, you generally cannot tell from the outside, and it is fair to say so plainly. What you can rely on is the boundary: whatever the link records, it records about that page. If a link asks you to install a viewer before it will show you the document, that is a different category — an enforcing DRM reader — and software is being placed on your machine, with your consent, at that prompt.
Sources
- NIST Computer Security Resource Center — glossary entry for “spyware”: software secretly or surreptitiously installed into an information system to gather information on individuals or organizations without their knowledge; a type of malicious code (sourced there to CNSSI 4009). ⚠️ Channel disclosure: csrc.nist.gov did not answer a direct fetch from our network, so this was read through search-engine retrieval of the glossary entry (accessed 2026-09-14)
- CISA (US Cybersecurity and Infrastructure Security Agency) — Recognizing and Avoiding Spyware, security tip ST04-016: spyware can be installed on your machine without your knowledge, commonly bundled with free downloads and toolbars, and once resident can monitor nearly any activity on the device. ⚠️ Channel disclosure: cisa.gov did not answer a direct fetch from our network, so this was read through search-engine retrieval (accessed 2026-09-14)
- US Federal Trade Commission — Stalkerware: What To Know: stalkerware, also known as spyware, is software somebody installs on your phone or other device without your knowledge, and is designed to avoid detection by the device's owner. ⚠️ Channel disclosure: consumer.ftc.gov did not answer a direct fetch from our network, so this was read through search-engine retrieval (accessed 2026-09-14)
- PDFTrackr — the free plan's limits, the retention windows and the Pro price, published on the site's own pricing surface (accessed 2026-09-14)
Send yourself a tracked link and read your own record
The fastest way to settle what document tracking collects is to be both ends of it. Free: 50 files, 50 links, 12 months of history, no card.
Create a free tracked linkKeep reading: what PDF tracking is, whether you should disclose document tracking, and DRM versus document tracking. Or start with how free PDF tracking works.
Oleh Tsyupa
Founder, PDFTrackr
Has analysed over 3,000 tracked document-viewing sessions on PDFTrackr.