Privacy
What this site collects when you read it, and who handles it.
What we collect
You can read everything here without signing up or telling us who you are. There are no reader accounts, comments, newsletter, sign-up forms or message-submission forms, and the site does not send you email. Search and filter controls put your choices into the page address, where analytics and request logs can record them.
We use Google Analytics 4 to count page views. When a page loads, your browser sends Google the address of the page, and Google may set cookies and receive information about your device, browser and network, including your IP address. Our code does not load the tag on a direct editor-page visit or send its own page view there.
Like most websites, the services that deliver these pages record requests as they handle them. Those request logs can include your IP address, the page you asked for, the time and your browser's description of itself.
If a message reaches the contact address below, we receive your email address and whatever you put in it. Cloudflare Email Routing is configured to forward the domain's mail to a Google-hosted mailbox, but as of November 7, 2026 we had not completed an end-to-end delivery test for this address.
Why
Page views tell us which reporting people read and how they found it. Request logs keep the site running: they are how we find errors and outages. We do not sell any of this.
Who processes it
- Google runs Google Analytics and receives the page view data described above. Google also hosts the mailbox that receives messages sent to our contact address.
- Vercel hosts the website and keeps logs of the requests it serves.
- Railway hosts the API and the database behind the site. The database holds the reporting you see here, such as statements, sources and funding records about public figures. Railway may log requests that Vercel's server and the editorial tools send to the API.
- Cloudflare is configured to route messages sent to the contact address below. It does not deliver the website itself.
The only cookie this site sets itself is a sign-in cookie for the site's own editors. Readers never receive it.
How long it is kept
A Google Analytics cookie expires after up to two years unless you clear it sooner. A return visit can renew that expiration, so the cookie can remain longer than two years from your first visit. Google Analytics keeps event-level data for either two or fourteen months, depending on the property setting. We have not yet independently verified which setting is active, so you should assume it can be kept for fourteen months.
Vercel Pro makes runtime logs available for one day. Its optional Observability Plus feature can keep them for up to thirty days; we have not verified whether it is active, so assume thirty days. Railway's Hobby dashboard makes seven days of logs available, while Railway has said stored logs, including HTTP logs, may be retained for up to ninety days. Assume ninety days.
We do not copy provider request logs or extend their retention, and the site's database does not store readers' IP addresses. Contact email stays in the mailbox until we delete it; there is no fixed deletion schedule.
Your choices
This site is written for readers in the United States and does not show a cookie banner. You can still decide what your browser shares: block or clear cookies in its settings, use a private window, or install a content blocker that stops Google Analytics from loading. The site works the same either way.
Contact
Questions about privacy go to privacy@hypocrisynowinc.com.