For insurers, MGAs and their compliance teams
When your sales or product decisions are questioned, show the record as it was on the day.
A complaint about a policy sold directly, a supervisor reviewing how a product reached its target market, an ICT incident under review. Each turns on records your own systems hold, and on whether anyone could have changed them since.
- When it is tested
- A complaint escalated to the insurance ombudsman; a supervisory inspection of your distribution and product governance; a review of an ICT incident and of what you reported.
- What you will be asked for
- When you sell directly, the customer’s demands and needs and any advice given (IDD, Article 20); the approval process and target market of each product (IDD, Article 25); for an ICT incident, how it was handled and what was reported (DORA, Articles 17 and 19).
- What goes wrong today
- These records sit in policy administration, CRM and ticketing systems that administrators can edit. Their audit trails are those systems’ own word, and an outside reviewer has to take it.
- What changes
- Each advice note, product-approval decision and incident report is sealed as it is made, from your systems through the API or by hand on this site. A later correction is a new sealed version beside the original. Nothing about your customers reaches us: only a salted fingerprint.
Sealing shows that a record existed unchanged from a given moment; whether your records are enough is yours to judge. What the IDD asks · What DORA asks
Try it in two minutes
- Choose a real file of your own: a product approval record, an advice note or an incident report. It is read in your browser and never uploaded.
- Seal it on Seal a file. A free sandbox key is issued on the page; only a salted fingerprint reaches the log.
- Make a copy, change one character in it, and check both against the receipt at Check. The copy fails; the original passes.
From your own systems it is one API call per record. Integrate · Other industries