SecurityDeclines to elaborate

Described in general terms, deliberately.

The Organization takes security seriously, which is why this page is mostly about what it will not tell you.

One door.

Every service sits behind the same sign-on, held by the network. No service is reachable around it.

Owned, not rented.

The hardware belongs to The Organization. No cloud account stands between a member and a service.

Backups are proven.

Snapshots are taken, archives are shipped to a different machine, and restore drills are run. A backup that has not passed a drill is not counted as one. This page can run one on itself: see Proof, on the home page.

The operator is sealed and gated.

An AI operator carries out changes. It runs inside a hardware enclave that proves what code it is running before anything is sent to it. It proposes. A person approves.

This page is sealed.

When the site is built, the home page’s SHA-256, size and element count are written to a manifest. The drill checks the live page against it. So can you:

curl -s https://extratoum.com/ | sha256sum
curl -s https://extratoum.com/drill/manifest.json

Sealed at build.

Reporting a problem.

If you have found one, you know someone who knows where to send it.

Everything else.

Is the part we are not describing.

toum:main net — sealed LF UTF-8