The Corpus Index

Last updated 28 July 2026

Security

Static pages, no database, no accounts, no third-party scripts — and a direct route to report anything you find.

A deliberately small surface

The safest system is the one that is not there. This site is static HTML: no database, no user accounts, no login, no server-side application code, no content management system to keep patched. There is nothing to inject into and no session to steal.

  • HTTPS only, with HTTP requests redirected.
  • No third-party scripts. Fonts, CSS and JavaScript are served from this domain, so no external party observes your visit.
  • No payment data is ever collected here. Invoicing, when it happens, happens elsewhere.
  • No advertising or analytics SDKs, which are the usual route by which a static site starts leaking.

Data we hold

Only what you send us: the contact form fields and the email conversation that follows. That lives in a mailbox with two-factor authentication, not in an application we wrote. Retention and your rights are in the privacy policy.

Reporting a vulnerability

If you find a security problem — in the site, in the delivery of the contact form, or in anything else that carries our name — tell us before telling anyone else:

  • Write to hello@thecorpusindex.com with "security" in the subject.
  • Include enough detail to reproduce it. A proof of concept is welcome.
  • We acknowledge within 2 business days and tell you what we intend to do and when.

What we ask: do not access or modify data that is not yours, do not degrade the service for other people, do not run denial-of-service or spam tests, and give us a reasonable window to fix the issue before publishing. Research done in good faith under those conditions is welcome, and we will not pursue you for it.

We do not run a paid bug bounty. We do credit reporters who want the credit.

Integrity of the numbers

Security here also means the figures cannot be quietly edited. Every edition is generated from a stored run of the pipeline, the source pages are linked so any reader can check our reading, and material corrections are stated on the page rather than applied silently. That is described in the method and in the terms.

Last reviewed 28 July 2026.