Skip to the record
The Executive Record

Not legal advice

The registerPrivacy

Privacy

What this site collects, what it deliberately does not, and why. Written from the database schema rather than from a template — if this page and the code ever disagree, the code is the truth.

Last updated 19 August 2026

The short version

  • No IP addresses are stored. There is no column for one in any table, and no code path that reads one.
  • There are no accounts. You cannot sign in, because there is nothing to sign in to.
  • No third-party analytics or advertising trackers run on this site. No Google Analytics, no Meta pixel, no ad network — none.
  • Nothing you do here is sent to an AI model. Summaries are generated ahead of time from the published text of executive orders. Your reading, your searches and your messages are never sent to a model.
  • Two random, anonymous cookies let us count visits without knowing who you are.

Cookies

Two, both strictly for counting. Neither identifies you.

  • ts_sid — a random value marking one visit. Expires after 30 minutes of inactivity.
  • ts_vid — a random value that lets us tell a returning visitor from a new one. Expires after 90 days.

Both are randomly generated. There is no table anywhere that maps either value to a person, an address, or an account — no such table could be built from what we hold. Both are marked HttpOnly and SameSite=Lax, so they are not readable by scripts and are not sent to other sites.

Blocking them is fine. Pages render identically; we simply count less.

What is recorded when you read a page

For each page view we store:

  • which page, as a path — for example /orders/14420
  • the two anonymous cookie values above
  • how you arrived, in coarse terms — whether from a search engine, a social link, another page on this site, or directly, plus the referring site’s host (for example www.google.com) where it came from outside. The rest of the referring address is discarded — a referring URL can contain the words somebody typed into a search engine, and we have no use for that which would justify keeping it.
  • a coarse region, such as US-CA, taken from a header our host provides. It is already coarse when we receive it. The address it was derived from is never read by this application and has nowhere to be stored.
  • whether the visit looks automated — every event is labelled bot, human or unknown, worked out from the browser identification string your software sends and from the pace of requests. This exists to keep search-engine crawlers out of visitor counts, not to profile anyone.
  • the time.

We also record a small number of specific actions:

  • searches, including the words searched for, and how many results came back. Searches that return nothing are the single most useful thing this site can learn. Please do not type anything private into the search box — it is a search box for executive orders, and the text is stored. It is stored for 90 days and then removed; see how long it is kept.
  • which filters were applied, and how many orders they matched
  • when someone follows a link out to the Federal Register
  • when the correction form is opened or sent
  • how long a visit lasted, and which page it ended on.

What is never collected

  • IP addresses. Not stored, not logged by this application, not derivable from anything we keep. The database has no column that could hold one, and the automated test suite fails the build if a new field is added to the analytics table without being reviewed.
  • Names, accounts, passwords, or payment details. None are collected.
  • Precise location. Only the coarse region described above.
  • Cross-site tracking. Nothing here follows you to other websites.
  • Device fingerprinting. We read the browser identification string your software already sends, to tell crawlers from readers. We do not build a device profile from it.

If you contact us or report a summary

Two forms on this site write to the database. Both are optional and neither requires an account.

  • The correction form on each order’s page records which summary you are reporting, what is wrong with it, and an optional note of up to 400 characters. It stores the exact version of the text you read, so a complaint can be told apart from one a later revision already fixed.
  • The contact form records your message, the topic you chose, and an email address only if you supply one. It is optional and exists solely so we can reply — there is no other reason we would have it, and if you leave it blank we simply cannot answer.

Both are rate-limited using the anonymous session cookie so that one visitor cannot flood them. That limit is the only reason the cookie is attached, and it is deliberately not based on an IP address.

Who else can see this

  • Our host and our database provider necessarily process requests and store the data described above on our behalf.
  • The Federal Register — the source links on every order point there. Following one is an ordinary visit to a government website, subject to its own policy, not ours.
  • Anthropic generated the plain-language summaries from the published text of the orders, in a batch, before you arrived. No information about you or your visit is sent to any AI model, ever.

Nothing is sold, and nothing is shared for advertising.

How long it is kept

Nothing is kept indefinitely. Each of these is deleted on a schedule:

  • The words you type into the search box: 90 days. Shorter than everything else on this list, deliberately. It is the only thing we hold that you typed without being asked to, and we have no use for the wording of a search from last year. After 90 days the text is stripped out and the rest of the record — that a search happened, and how many results it found — remains, so we can still see whether search is working without keeping what anybody looked for.
  • Analytics records: 24 months, then deleted outright.
  • Contact messages: 24 months after we have finished dealing with them — or 24 months after they arrive, if we never do. Nothing survives by being forgotten about. Any email address you gave us goes with the message.
  • Correction reports: 24 months, on the same terms.
  • The cookies expire on their own, on the schedule further up this page.

These periods are not a description of our intentions. They are read directly from the same file the deletion job reads, so this paragraph cannot say one thing while the code does another — and the job runs automatically, once a day, rather than when somebody remembers.

You can also ask us to delete a message you sent, at any time and without waiting for the period above, through the contact form.

This will change when advertising is added

No advertising runs on this site today and no ad-network code is loaded. The layout reserves space where advertising will eventually sit, and those spaces render nothing.

When advertising is introduced, an ad network will set its own cookies and collect its own data under its own policy, and this page will be rewritten before that happens, not after. The sections above marked Cookies, Who else can see this and What is never collected are the ones that will change.

Children

This is a reference tool for public records and is not directed to children under 13. We do not knowingly collect information from them — and given that no names, accounts or addresses are collected from anyone, there is very little to collect.

Questions

Use the contact form. It is the route for anything about this policy, including a request to remove a message you sent us.