Privacy
Last updated: October 2026.
This site is a set of static pages. It has no accounts, no comments, and no advertising. Its only form is an optional email signup for release updates, described below.
What we collect
- Aggregate traffic measurements via Cloudflare Web Analytics, which does not use cookies or local storage, does not fingerprint devices, and gives us page-level counts, referrers, and approximate country. We cannot identify individual visitors from it.
- Server logs are handled by Cloudflare, which hosts the site. Cloudflare’s own privacy policy governs that processing.
- Your email address, if you sign up for updates.
We do not set cookies, and there is no cookie banner because there is nothing to consent to.
Email updates
The signup form is optional. If you use it:
- What is stored. Your email address, and the records our email provider keeps to confirm and deliver a subscription, such as when you signed up and confirmed.
- Who handles it. The list is run on Buttondown, which stores the address and sends the email on our behalf. Buttondown’s privacy policy governs its processing.
- Confirmation. You are not added to the list until you click the link in a confirmation email, so nobody can sign you up without your knowledge.
- What we send. Emails only about FedCourtsAI releases, about two to four times a year, from
updates@fedcourts.ai. - Leaving. Every email has a one-click unsubscribe link.
Third parties
Links on this site go to GitHub, X, and other sites we do not control. Submitting the signup form sends your email address to Buttondown, as described above.
Court records
The ledger contains information from public court dockets, including party names as they appear in public filings. This is public-record information republished from CourtListener and supremecourt.gov. If you believe a record here is inaccurate, open an issue and we will look at the source.
Contact
Questions about this policy, your email subscription, or deleting your address: contact@fedcourts.ai. Corrections to the ledger are best raised as GitHub issues, so the fix is public too.