A permanent address for every document you must publish.

Where it is used

One register, entered from the documents you publish.

The register holds a publisher, its products, its documents and their versions, and it does not care what the documents are about. What differs between the pages below is the vocabulary, the document types and the recipients — not the record underneath.

What the register holds

Attached where it belongs, addressed on its own.

A document is attached to a publisher, or to a product somewhere in that publisher's own structure — and to more than one where that is the truth of it. The attachment decides where the document is shown and how it is grouped. It does not decide the address: every document has its own, unchanged by anything that happens to the structure around it.

Each language version is a document in its own right, with its own address and its own publication date. Periodic documents are separate too: the 2023 annual report is not an earlier version of the 2024 one, and both remain current for their year.

The paths are the same whether documents are served from our domain or from yours by CNAME. Slugs are proposed on upload from the identifier, the document type and the language, so the address reads as what it is. Rename a document and the previous slug keeps answering — permanently, and without a redirect, because a redirect is what makes a collector record the wrong address.

Which document types a publisher has, and what they are called, is a property of the publisher and not of our model. The document library for fund and AIF managers is written out on its own page.

Where we fit

After the document is approved. Before it is referenced.

Approved document→Kilospring→Website · Data templates · Recipients

You do not replace your website, your document production, your administrator or your distribution arrangements. The register sits alongside them and holds the one thing none of them holds: the record of what was published, when, and in place of what. Where a publishing chain to data vendors and platforms exists, it is address-based — and a permanent address turns the submission into one made once rather than corrected each time a file is replaced.

Security and data

Your documents, held plainly and kept within reach.

Files and metadata are held in storage restricted to EU jurisdiction, and we hold no personal data beyond your contact people. A file you upload is stored byte for byte and never altered, its hash recorded on arrival. Everything we hold for you — the documents, the version history and the event log — can be exported in full at any time, so leaving costs you a download rather than a negotiation.

The service is deliberately narrow, and that is what makes it easy to approve: it is a technical publication service, not an outsourcing of anything you hold a licence for. We do say mechanical things about our own storage — that the document on file is dated 12 March 2025, or that no file has been uploaded for March 2026 — as fact, never as advice.

We will appear in your register of information as an ICT third-party service provider, and the contractual terms under Article 30 of DORA apply to us however small the service is. The supplier dossier is written before the first conversation rather than after it: contractual annex, registration details, sub-processor list, place of operation within the EU, and an exit plan with a full export.