The annex
Legal and company.
Six standing documents. Each is dated when reviewed and changes only by dated revision, the same discipline as everything else in the house.
01 · The company
Who builds this, and under which number
HEIMLANDR AB, a limited company registered in Sweden, builds and operates Halantir. The registration number, the registered office and the one contact address are printed in full, not held behind a form. The same page carries the source attributions for the record and for the administrative boundaries the map is drawn from, because the footer points here for them and an attribution that lives nowhere is not an attribution.
02 · Privacy
One ledger, and you put yourself in it
The record refuses to model persons, and the same refusal governs the people reading it. Reading stores nothing. Exactly one store in the house holds personal data: the launch notice ledger, which holds an address, an organisation line if one was given, and a timestamp. It is firewalled from the record, no join reaches it, and one mail deletes the row. HEIMLANDR AB is the controller and the Swedish supervisory authority is named.
03 · Terms
What reading the record promises
Promised: that every published figure was read from the named register at the stamped moment and hashes to the stamped hash, and that a figure later shown wrong files as a public correction which stays readable. Not promised: that the register itself is right, current or complete. Reading is free for everyone, forever, including the subject of a record, and replaying a receipt through the public door is part of the product.
05 · Accessibility
The floor, designed in rather than audited on
Text contrast at or above 4.5:1 on every surface, full keyboard operability with a visible focus ring, reduced motion honoured without leaving anything hidden, and a failed read that says so in words instead of spinning. The floor is aligned on WCAG 2.2 AA. No third-party audit has been performed at pre-launch and the page says so. A barrier is a defect and gets fixed like one.
06 · Security
One published surface, and one address for a finding
The public surface is the api schema and nothing else. Write paths answer only to service credentials, the operational schemas answer to no public request, and the one public write door is the launch notice form. Rows cannot be hard-deleted, every change lands in a revision ledger, and every row's content hash can be replayed against its source. The page also lists the one dependency advisory a scan will raise and why it is unreachable here.
07 · The shape
Six documents rather than one
Each answers a different question and each is dated on its own schedule. A single page would date as a block: one correction to the cookie claim would restamp the privacy text nobody touched. Six addresses also mean a reader can link to one claim, and check that claim, without carrying the other five.