For
Insurance distributors, brokers and MGAs
You already document what a customer needed and justify what you recommended — IDD Article 20 requires it. The question is not whether you keep records. It is whether a record you kept can be told apart from one that was corrected afterwards. In a spreadsheet, it cannot. In an append-only, hash-chained ledger, it structurally cannot happen at all.
Where you sit relative to us
Money and the customer relationship stay exactly where they are today. Nothing moves through us.
Your recommendation → RiskRouter prices it server-side and seals it → your file, with a record that cannot be edited — not by you, not by us, not by anyone with database access
The questions your compliance file actually asks
Answered directly, not deferred to a call.
What data do we send?
A risk vertical and the component toggles the customer chose. No name, no email, no identifier of any kind — the payload has no field for one.
What does RiskRouter calculate?
The premium, entirely server-side, from a published rating matrix. A price your own system sends is never read back as the answer.
What gets permanently recorded?
The exact component state, the timestamp, the premium and your distributor id — chained to the entry before it, so editing one breaks every entry after it.
Where is it hosted?
Frankfurt, Germany, inside the EU. See the full data-protection position on the privacy page.
Can we verify it ourselves?
Export your own entries and run two dependency-free Node scripts against them, offline, with no call back to us. See how the tamper check works.
What if RiskRouter disappears?
An export you downloaded last year still verifies after we have stopped answering the phone. That is the actual answer to the actual question, not a promise.
How much engineering work is required?
One HTTP call. No SDK to install, no session to manage. Most integrations are a single afternoon — see the integration guide for two worked examples.
How do we test it before committing?
A sandbox key costs nothing and writes to a separate row from production. Or skip keys entirely and price against the live demo right now.
If you are an MGA rather than a broker
Nothing above changes. The distributor id in the ledger is yours whether you write the recommendation yourself or aggregate it from a panel of agents underneath you — the chain records who was attributed, at the level you issue keys to.
What this replaces
A spreadsheet nobody can date-stamp
A cell that says "reviewed" proves nothing about when, or whether it looked different last month.
An evening spent hoping the file is findable
A three-person practice absorbs Article 20 in evenings. A large network absorbs it in a compliance department. This is built for the first case.
Trusting the operator's word
A database dump is a claim. A chain a holder can verify offline, against a signed head hash, is evidence.