The short version
There are no accounts, no ads and no forms on this site, so there is nowhere to type anything and nothing you type is sent. We count visits with one analytics service, Amplitude. Below is every event our code sends it and every detail each one carries, what Amplitude's own code adds, and the two other ways your browser can talk to another site from here.
What we count
Your browser sends Amplitude a short event when you:
- open a page: which page, the name of the site that linked you here (its name only, not the address), and the
?ref=tag if the link carried one. If you got there by one of our own onward links (“Next post”, a same-day pair, a random passage and the like), it also says which kind of link and which of our pages it was on; - scroll more than one screen down a page: which page;
- open a card's “Original passage & context”: which card, on which page;
- follow a link to an original document: which card, on which page, which of the card's links you used, and the name of the site the link goes to;
- press Share: which card (on a same-day pair page, which pair), and not where you shared it;
- on a classroom set, press Print or open a whole original: which of the two, which source (for an original), on which set;
- jump to a chapter on the secession page: which chapter you chose, the chapter you were in (or “top”, if you had not reached one yet), and the page.
Those seven are every event our code sends. Our code does not record what you type or where your pointer moves, it switches off Amplitude's automatic capture of clicks and forms, and there is no session recording.
What comes with each event
- A random device number. Amplitude's code stores it in a cookie on this site, set to last a year, so that two visits from the same browser can be told apart from two different people. It is not your name or email, and our code never asks for or sends either.
- Your browser, operating system and language.
- Your IP address. Amplitude's servers receive it. Our reports show an approximate location from it: a city, region and country.
We use these counts to see whether anyone reads the feeds and checks the sources, and to subtract our own visits from the numbers.
What this site does not do
- No ads and no advertising tags.
- No cookie of our own. When you click one of our onward links, our code writes one short note in that browser tab: which kind of link, the page you left, the page it leads to, and the time. The next page of this site you open reads it and deletes it, and clicking any other link deletes it too. It never leaves your browser except as the “which kind of link, on which page” detail above.
- Our code does not read Do Not Track or Global Privacy Control settings. If you block
cdn.amplitude.comwith a content blocker, our code sends nothing, and the pages still work. - We run no server code of our own and do not read request logs. The site is plain files served by Render, whose own logging we do not control.
Other sites
The verification record and its page-image views show scans of the original newspapers, loaded straight from the Library of Congress and the Internet Archive. Opening those pages sends your browser to those sites for the images, so they see your IP address. A link to an original document loads nothing until you click it; after that you are on the archive's site, under its own rules, and your browser may tell it you came from disunionfeed.com.
Questions
Write to david@skylarkcreations.com. Disunion Feed is a Skylark Creations project by Dave Kooi.
Last changed November 6, 2026.