End User Licence Agreement

Apex Data Routing — London Market Data Validation Appliance

Version 1.9 · Effective on the earlier of licence activation or first use

0. In one page

This page is a summary for convenience. Clauses 1 to 13 are the agreement.

1. What this software is

The Software is a self-hosted local utility. You run it on infrastructure you control. It is delivered "as is", with no warranty of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, or non-infringement.

The Licensor operates no service on your behalf. There is no hosted endpoint, no uptime commitment, no service level, no support obligation and no maintenance obligation. Nothing in any documentation, demonstration, benchmark or conversation creates one. The remedies in clauses 5.6, 9A and 9B are the only remedies for the Software's performance, and none of them is a service level.

1.1 What it is for. The Software exists to move a document one step closer to the shape the London Market will accept before it is submitted: to check a Core Data Record against the constraints a claim movement has to satisfy, to explain how a bordereau will be read before it is parsed, to route a first notification of loss on what it actually says, to express a validated claim movement as an ACORD ECOT message, and to correct, or put to you, the faults it finds (clause 8A). It finds the faults that are cheap to fix now and expensive to fix after a rejection.

That is a step towards those standards, and is not a certificate of compliance with them. The constraints the Software applies are modelled by the Licensor from published material; they are not a certified specification, and no output of the Software is a Velonetic or Lloyd's sign-off, an underwriting opinion or a clearing guarantee. Clause 2 states what this leaves with you, and clause 8 states what any accuracy figure does and does not mean.

1.2 Formats. The Software reads bordereaux and related returns in the delimited and spreadsheet forms it documents, validates claim movements against the Core Data Record constraints it publishes with each result, and can express a validated movement in the field names of an ACORD ECOT claims message, stating for every field where its value came from. That output is structured data (JSON), not an ACORD XML message: it is not serialised to the ACORD message form and is not validated against an ACORD schema, which is licensed to ACORD members and is not part of the Software. It does not produce, submit or manage an Electronic Claims File (ECF) or any other market workflow, and it submits nothing to Velonetic, Lloyd's, the IUA or any other market system: every output is a document for you to use in your own process. An ECOT message the Software produces is modelled by the Licensor from published ACORD material and is subject to clause 1.1 in the same way as every other output.

2. What it is not

The Software produces decision support, not decisions. It does not provide legal, regulatory, actuarial, underwriting or claims-handling advice, and it is not a substitute for a qualified professional exercising judgement.

You remain solely responsible for every underwriting, binding, settlement, reserving, sanctions and compliance decision made by your organisation, including any decision informed by output from the Software. Any figure the Software returns — a reserve, a risk score, a coverage verdict, a screening result — is an input to your process and must be reviewed by a competent person before it is acted on.

3. Data boundary

This clause is stated precisely, because a general assurance would be less useful to you than an accurate one.

3.1 The Licensor holds nothing. The Licensor does not host, receive, store, process, transmit or view Your Data. No telemetry is collected. No content leaves your infrastructure to reach the Licensor, in any circumstance. The only thing that can ever travel to the Licensor is a document you choose to send by hand, such as the Quality Statement described in clause 9B.3, which carries counts and identifiers and no content.

3.2 The validation appliance makes no network call. The licensed appliance serves /v1/ingest/inspect, /v1/cdr/validate, /v1/cdr/ecot, /v1/claims/triage and /v1/remediate/patch, with the Step 3 reads that return a working copy's query list and corrected document (clause 8A), together with /v1/quality/reports, which keeps a request id, a verdict and your own market reference on your machine, /v1/quality/selftest, which runs the bundled samples through the engines and keeps only pass or fail, and /v1/quality/receipts, which keeps a receipt the Licensor signed and returned to you. These execute entirely within your process and call no external service. This is verifiable rather than promised: run the container with --network none and every one of them continues to work.

3.3 Optional extended editions. The Licensor also builds editions that add document extraction, schema transformation, contract audit, bordereau reconciliation and exposure screening. Those endpoints transmit document content to Anthropic PBC for processing, using API credentials you supply. They are not part of the validation appliance licensed under this Agreement and are not present in the build you receive unless you separately order an edition that includes them. If you do order one:

• Your Data leaves your infrastructure and is processed by a third party.
• Your relationship with that provider is governed by your agreement with them, to which the Licensor is not a party.
• You are responsible for determining whether that transmission is lawful and appropriate for each class of document, including under UK GDPR, the Data Protection Act 2018, your regulatory obligations and any confidentiality owed to your clients or theirs.
• No configuration setting changes this. If that transmission is unacceptable for a category of document, those endpoints are unsuitable for it.

3.4 Your responsibilities. You are solely responsible for the security of your deployment, your infrastructure, your access controls, and the API credentials you configure. Credentials are read from your environment and never transmitted to the Licensor.

3.5 Sanctions and screening data. No sanctions list data is supplied with the Software. Obtaining current lists, keeping them current, and setting screening thresholds are yours. Where no list is loaded, the Software reports NOT_SCREENED and clear_to_bind: false; it will never report a party as clear on the basis of a check that did not happen. Interpreting a screening result remains a compliance decision you own.

4. Limitation of liability

4.1 Cap. To the fullest extent permitted by applicable law, the Licensor's total aggregate liability arising out of or in connection with this Agreement or the Software, whether in contract, tort (including negligence), breach of statutory duty or otherwise, shall not exceed the total fees you paid for the Software in the twelve months preceding the event giving rise to the claim, or £100, whichever is the greater.

4.2 Excluded losses. The Licensor shall not be liable for loss of profit, loss of revenue, loss of business, loss of anticipated savings, loss or corruption of data, regulatory fines or penalties, or any indirect or consequential loss, however arising.

4.3 What cannot be excluded. Nothing in this Agreement excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot lawfully be excluded or limited.

5. Licence, fees and payment

5.1 Licence granted. Subject to payment and to this Agreement, you are granted a non-exclusive, non-transferable, non-sublicensable licence to install and use the Software within your own organisation for the term purchased.

5.2 Restrictions. You may not: redistribute, resell, sublicense or host the Software as a service for third parties; remove or alter licensing, attribution or expiry mechanisms; or use the Software to build a competing product.

5.3 Fees and terms. The Software is licensed to businesses on one of three plans, priced in pounds sterling and exclusive of any tax that applies:

The plan, the fee and any agreed variation are recorded on the invoice, which forms part of this Agreement and prevails over this clause where they differ.

5.4 Payment and delivery. Invoices are payable within the period stated on the invoice. Delivery is electronic: a container image and a licence key, issued once payment clears, normally within one business day. There is nothing to ship and no physical goods are supplied.

5.5 Cancellation and refunds. On Flexible Operational you may cancel on 30 days written notice, and fees already paid for a completed service period are not refundable. On Annual Committed and Annual Prepaid the minimum term runs for 12 months. The five circumstances in which money is returned are set out in clauses 5.6, 9A.3, 9B.4, 10B and 11; there are no others. Where a refund is due it is made to the original payment method within 14 days.

5.6 30-day performance guarantee. If, within 30 days of licence activation, the Software records no catch after at least 20 unique checks, you may cancel without charge and the fees paid for that period are refunded. A catch is a refused CDR field, a date column whose order cannot be trusted, a contradiction in claim data, or a Step 3 correction or open item of a kind clause 8A.6(a) names. Tidying a value, such as removing stray spaces, is not a catch. A unique check is a distinct file or record. To claim, send the Licensor the Software's guarantee record, shown at /trial, within 7 days after the 30-day period ends.

5.7 Business use only. The Software is licensed only to businesses acting in the course of business. It is not offered to consumers, and no consumer cancellation rights arise.

5.8 Ownership. The Software, its documentation, rules, samples and mock-up catalogue, and all intellectual property rights in them, belong to the Licensor or its licensors. You receive only the licence in clause 5.1. As between us, your input documents, and the outputs and corrected documents the Software produces from them, belong to you; that gives you no right in the Software or its rules. Components of the Software supplied under an open-source licence are listed in the documentation, and that licence governs your use of those components. If you send the Licensor suggestions or comments about the Software, the Licensor may use them freely and without obligation to you, but will not identify you or disclose your confidential information in doing so.

Apex Data Routing is the trading name of an independent software provider. The Software, its documentation, rules and mock-up catalogue are protected by copyright, and all rights not expressly granted in this Agreement are reserved. ACORD, Lloyd's, Velonetic and the IUA are names of third parties; neither the Licensor nor the Software is affiliated with, authorised by or endorsed by any of them, or by any other organisation whose name includes "Apex". References to London Market data standards, the Core Data Record and ACORD messages describe what the Software is compatible with, and imply no connection with the bodies that publish them.

6. Delivery, activation, renewal and end of term

6.1 Delivery. Once payment clears, the Licensor sends to the address on the invoice: a container image reference with its digest, a licence key file signed by the Licensor, and the run guide. This normally happens within one business day. Nothing is shipped physically and no installation is performed by the Licensor on your systems.

6.2 Activation. You place the licence key where the appliance reads it and start the container. The appliance verifies the signature on your own machine and makes no call to the Licensor to do so; it works with no outbound network access at all. The term runs from activation.

6.3 The key carries the term. The licence key states the expiry date it was signed with. A renewal is a fresh key, issued on payment for the next term. The appliance is not disabled remotely and cannot be: there is no kill switch, because there is no connection to send one down.

Each licence key continues to work for 14 days after the end of the term it was issued for, so that a renewal delayed in reaching you does not stop your processing. Use during those 14 days is licensed only where the renewal has been paid for or is then paid; otherwise the licence has ended and clause 6.5 applies from the end of the term.

6.4 Non-renewal and non-payment. If a term ends without renewal, or the licence is ended under clause 9.2 for an unpaid instalment, no new key is issued and the current key stops working at the end of its 14-day grace period (clause 6.3).

6.5 What happens when the licence ends. On expiry, non-renewal or termination, the appliance you are running:

• refuses the /v1 processing endpoints with HTTP 402 and a message naming the date that passed, so nobody is left guessing why it stopped;
• continues to serve health, documentation, /trial and the Quality Statement, so you can close your own records and evidence any claim under clause 9A or 9B;
• deletes nothing. Your documents, your results, your ledger and your reports stay on your infrastructure and remain yours. The Licensor holds no copy and cannot, because it never received any (clause 3.1);
• sends nothing. Expiry is a date comparison on your machine, not a message to us;
• leaves your own credentials untouched. Any model-provider API key is yours throughout; the Licensor never held it. Remove it when you decommission.

You must then cease using the Software and remove the image and the licence key within 30 days. The expiry is a commercial term, not a security control: circumventing it is a breach of this Agreement whether or not it is technically possible.

6.6 Trial builds. An evaluation build behaves as clause 6.5 describes from the expiry date compiled into it, without a licence key ever being issued.

7. Governing law and disputes

This Agreement is governed by the laws of England and Wales.

The parties shall first attempt to resolve any dispute in good faith through written correspondence. Where a dispute cannot be resolved within 30 days, it shall be referred to arbitration in London under the LCIA Rules, by a sole arbitrator, conducted on documents only unless the arbitrator directs otherwise.

8. Accuracy and benchmarks

Any accuracy figure published by the Licensor is measured over synthetic documents with labels constructed by the Licensor, not over real market documents verified by an independent party. It is a regression baseline. It is not a prediction of accuracy on your traffic, and it is not warranted. The same is true of the mock-up catalogue in the evaluation console (clause 13.3), every document of which is fabricated by the Licensor to exercise one named engine behaviour. It shows how the engines behave; it does not represent your data and it is not a sample of the market. Nor does a correction Step 3 makes to a mock-up (clause 8A) say anything about how often the same correction will be right on your documents.

You are responsible for validating the Software against your own documents before relying on it. Clauses 9A and 9B are how its behaviour on your own traffic is measured once you do.

8A. Step 3: corrections the Software makes, and your approval

In short: where a value has one right answer, the Software puts it right and shows you what it changed. Where it has to assume, it says so, shows you the alternatives and lets you reverse it in one step. Where no single answer is right, it changes nothing and writes the question down for you. Nothing is final until you approve it, and your original file is never changed.

8A.1 What Step 3 does. After a document is checked, the Software prepares a corrected working copy of it and marks every change it made as one of three kinds:

• Applied. The input matches a rule under which, as modelled by the Licensor, it admits only one reading — for example, a currency written in words has one ISO code, stray spaces are not part of a reference, and a date column containing a day above 12 fixes its own order. The Software applies it. An Applied correction is output of the Software under clause 1 and is not warranted.
• Assumed. The input admits more than one valid reading and nothing in it decides between them — a date column in which every value reads both ways, or a syndicate number one digit short. The Software applies the London Market convention (for example, day-month-year for a date column, or a leading zero on a syndicate number), marks the change as assumed, shows every alternative and lets you reverse it in one step. A date convention is decided once for the whole column, never cell by cell.
• Not corrected. Where no single correction would be right — a column that mixes two date conventions, a currency the market does not settle in — the Software changes nothing and records the question instead.

8A.2 Your approval. Every correction is a proposal until you approve it. You may change any correction to another reading the Software offers; you cannot enter an arbitrary value through Step 3, so that every value in the corrected document is one the Software can explain. You approve every correction in a corrected document when you export it. Export means any retrieval of the corrected document from the Software, whether through its interface or through any endpoint, and whether by a person or by your own systems or automation; if your systems retrieve it automatically, that retrieval is your approval. From export onwards the corrected document is your document and its use is your decision (clause 2). An item recorded as not corrected remains open and yours to resolve. You should review Assumed corrections in particular against what you know about the document's source: they are the Licensor's reading of market convention, not a fact about your data. Approval does not prevent a record from being counted under clause 9A as clause 8A.6 describes.

8A.3 The query list. The Software also produces a note, in plain English, of what it corrected, what it assumed and what remains open, for you to send to whoever supplied the document. Whether, when and how to send it is yours.

8A.4 The working copy. The working copy is held in memory only and is never written to disk. It is discarded 30 minutes after it was last used, or when the Software restarts, and a document of more than 5,000 rows is not held. Export anything you want to keep. Your original input is never altered by Step 3. A working copy that expires before you export it is not an Engine Failure under clause 9B.

8A.5 The form of a correction. Corrections are written in the forms London Market systems expect, as modelled by the Licensor: ISO 8601 dates, ISO 4217 currency codes and four-digit syndicate numbers. That is a step towards those standards and not a certificate of compliance with them (clause 1.1).

8A.6 How Step 3 is measured.

(a) An Applied or Assumed correction to a Core Data Record field, a date or a syndicate number, and any item Step 3 records as not corrected, is a catch for clause 5.6. Other corrections, such as removing stray spaces, are not.

(b) A record you export after Step 3 that the market then rejects counts under clause 9A as a record the Software accepted, recorded against the request identifier of the check that preceded Step 3. It is a Missed Fault only where the rejection is caused by a check the Software applied or by an Applied correction it made. A rejection caused by an Assumed correction you approved, a correction you changed, or an item recorded as not corrected is your decision under clause 8A.2 and is not a Missed Fault.

(c) Clause 9B measures the checking engines and not Step 3. A failure of Step 3 to prepare or keep a working copy is not an Engine Failure or a Self-test Failure; where the checking engine completed its run, that run counts as completed.

9. Termination

9.1 Breach. This licence terminates automatically if you breach clause 5.2 (for example by sharing a licence key or redistributing the Software).

9.2 Unpaid instalment. On a plan billed monthly, the Licensor may end the licence by written notice if an instalment remains unpaid 14 days after a written reminder.

9.3 Sanctions. Either party may end the licence immediately where continuing it would breach UK sanctions law.

On termination you must cease use and remove all copies. Clauses 2, 3, 4, 5.8, 7, 8, 8A.2, 10A and 12.5 survive termination.

9A. Quality exit: when the engine's answers disagree with the market

In short: if what the appliance accepts or refuses turns out not to match what the market accepts or refuses, and you record that, either of us can walk away.

9A.1 What is measured. A Missed Fault is a record the Software accepted that the market rejected. A False Refusal is a record the Software refused that the market accepted without change. Each counts once, when you record it against the Software's result, by that result's request identifier, with the market's rejection or acceptance reference (POST /v1/quality/reports). The Quality Shortfall Rate for a calendar month is the Missed Faults and False Refusals recorded against that month's results, divided by that month's unique checks, as shown by the Software at /trial under operational_roi.quality (and, as Market Agreement, one minus that rate). A month with fewer than 20 unique checks has no rate. The Software's behaviour is measured against the rule list it publishes with each result (checked) for the licensed version, not against any other standard.

9A.2 When an exit right arises.

• 2% or less: no exit right arises.
• More than 2%, up to 5%: the Licensor has until the end of the following month to correct. If that month's rate also exceeds 2%, either party may end the licence by written notice.
• More than 5%: either party may end the licence immediately by written notice.

9A.3 What happens on a quality exit. Fees for the service period in which notice is given are refunded. On Annual Prepaid, fees for unused whole months are also refunded. Any minimum term ends with the licence, and neither party owes the other anything further under this Agreement.

9A.4 Evidence. Either party may ask to see the market references behind the recorded reports. A report you cannot evidence does not count.

9B. Monthly quality credit: when the engine fails to do its job at all

In short: clause 9A is about the engine being wrong. This clause is about the engine not running. It is measured by the Software itself, on your machine, and you send the Licensor a page of counts to claim it.

9B.1 Engine Quality Score. For every run of a deterministic engine the Software records, on your machine only, whether the engine completed its job: every applicable rule ran and a verdict was returned. A run the engine did not complete is an Engine Failure: an internal error, or a supported and readable file that a reader could not process. Each distinct input is counted as one Engine Failure however many times it is run that day; a failure the Software could not attribute to an input counts at most once per engine per day. A timeout, a size or row limit, or the resources of your own machine are not Engine Failures. A record the engine judged incomplete, ambiguous, out of scope or non-compliant is a completed run: reporting that is the engine's job, and such runs never count against it. The Engine Quality Score for a calendar month is runs completed divided by runs attempted, as shown by the Software at /trial under operational_roi.engine_quality and on the Quality Statement for that month.

9B.2 Self-test. At startup, once a day, and on request (POST /v1/quality/selftest), the Software runs its bundled samples through its own engines and records whether each produced the answer published with it. A Self-test Failure is a day on which that record shows any sample failing.

9B.3 Quality Statement. For any calendar month the Software produces a Quality Statement at /trial/statement: the daily log, the totals, the Engine Quality Score, the data quality of your inputs, the self-test record, the clause 9A reading and the ledger's hash-chain heads. It holds counts and identifiers only, never the content of any input. You choose whether to send it to the Licensor; the Software never does.

9B.4 When a credit is due. In a calendar month with at least 20 unique checks, a credit of that month's licence fee (on Annual Prepaid, one twelfth of the annual fee) is due where:

• the Engine Quality Score is below 99.5%; or
• there was a Self-test Failure on two or more consecutive days.

The Software marks the statement quality_credit.due when either applies. To claim, send the Licensor the statement for that month within 14 days after the month ends. The credit is set against the next invoice or, where none follows, refunded.

9B.5 Right to decline. After a month in which a credit is due, the Licensor may decline to continue the licence by written notice within 14 days of receiving the statement. That month's fee is credited or refunded as above, any minimum term ends with the licence, and neither party owes the other anything further under this Agreement.

9B.6 Integrity. The statement's hash-chain heads let each month's statement be checked against the one before it. On receiving a statement the Licensor may return a receipt signed with the licence key (POST /v1/quality/receipts records it on the Software), so that each month received sits between the Software's chain and the Licensor's signature. A statement whose chain does not continue from the statement previously received, or whose counts you cannot support from the ledger on request, does not found a credit. This clause is the sole remedy for an Engine Failure or a Self-test Failure and creates no service level (clause 1).

10. Entire agreement

This Agreement, together with the invoice and any addendum to it, is the entire agreement between the parties regarding the Software and supersedes all prior discussions. Where they conflict, the invoice and its addendum prevail. Your own purchase-order or supplier terms do not apply unless the Licensor has accepted them in writing. If any provision is held unenforceable, the remainder continues in force and the unenforceable provision is modified to the minimum extent necessary to make it enforceable. No variation is effective unless made in writing.

10A. Confidentiality

Each party will keep confidential the other's non-public information received under this Agreement — including the Licensor's pricing, licence keys and non-public documentation, and any Quality Statement or market reference you send — use it only for this Agreement, and disclose it only to its own staff and advisers who need it, or where required by law or a regulator. This does not apply to information that is or becomes public other than through a breach of this clause, or that the recipient already had or developed independently. This clause survives termination for three years.

10B. Events beyond control

Neither party is liable for delay or failure in performing its obligations, other than payment, caused by an event beyond its reasonable control, including the illness or incapacity of key personnel, the failure of a third-party email, hosting or payment provider, or a governmental act. The affected party will tell the other as soon as practicable. The grace period in clause 6.3 is there so that such an event does not stop your processing. If the event continues for more than 30 days, either party may end the licence by written notice, and the refund in clause 11 applies.

11. Withdrawal by the Licensor

The Licensor may decline to continue a licence at any time by written notice, whether or not clause 9A or 9B applies. On such a notice the fee for the service period in which notice is given is refunded, and on Annual Prepaid so are the fees for unused whole months. Any minimum term ends with the licence. This is a right to stop, not a right to withhold: no fee for a period already served is retained, and neither party owes the other anything further.

12. Acceptable use of the appliance

In short: it is yours to run for your own business, on your own machines, on your own data. What it costs you to run, and what you do with what it says, are yours.

12.1 What you may do. Run the Software on infrastructure you control, for the business of your own organisation and the organisations in your own group, for as many of your own users and as much of your own throughput as your machines will carry. There is no per-user, per-record or per-call charge and the Licensor does not meter you — it cannot, because it receives nothing (clause 3.1). Process your own data and any data you are authorised to process.

12.2 What you may not do. You may not:

• run the Software as a bureau, processing the data of third parties as a service, whether or not for a fee, or otherwise make it available to anyone outside your organisation;
• share, publish or reuse a licence key across a legal entity it was not issued to, or issue access to it to anyone outside your organisation;
• remove, alter or work around the licensing, attribution or expiry mechanisms, or run the Software after the licence ends;
• decompile or reverse engineer the Software, except to the extent that applicable law expressly permits it and you have first asked the Licensor for the information you need;
• use the Software, or anything learned from it, to build or assist a competing product;
• submit content you have no lawful right to process, or use the Software for an unlawful purpose or in breach of sanctions law;
• publish a benchmark or comparison of the Software without the Licensor's prior written consent, so that any figure attributed to it is one both parties can stand behind (clause 8).

12.3 Your model credentials, your bill. Where you run an edition that calls a model provider (clause 3.3), you supply your own API credentials and you contract and pay that provider directly. You set your own rate, spend and concurrency limits with them. The Licensor has no visibility of, control over, or responsibility for what you spend there, including spend caused by your own automation, retries, batch jobs or misconfiguration. No consumption by the Software is a cost the Licensor incurs, invoices, shares in or is liable for.

12.4 Your infrastructure, your exposure. How the Software is deployed, secured, reached, monitored and backed up is yours, as clause 3.4 sets out. Whatever your deployment then processes is your responsibility, not the Licensor's.

12.5 Indemnity. You will indemnify the Licensor against any claim brought by a third party, and the losses and reasonable costs (including reasonable legal fees) arising from it, to the extent it arises from: (a) your breach of clause 12.2; (b) data you, or anyone acting for you, submitted to the Software, including data you had no right to process and errors, omissions or ambiguities in data supplied by you, your brokers or your coverholders; or (c) a decision, transaction, placement, submission or notification made by your organisation on the Software's output, or on a corrected document you approved under clause 8A.2 (clause 2); except to the extent the claim is caused by the Licensor's breach of this Agreement or its negligence. The Licensor will tell you promptly of any such claim, let you conduct its defence at your cost, and give reasonable help at your expense. Clause 4.1 limits the Licensor's liability, not yours under this clause. This clause survives termination for six years.

12.6 Consequence. Breach of clause 12.2 terminates the licence under clause 9.1. Termination for breach carries no refund; clause 5.5 and the refund routes it names do not apply to it. Nothing in this clause limits clause 4.3.

13. The evaluation console and the mock-up catalogue

In short: the free console on our website is a demonstration, running on our server. Every document in it is a mock-up we made up. It is not the appliance, and it is not a place for real client data.

13.1 What it is. The Licensor publishes a hosted validation console for evaluation, free of charge and without registration. It runs the same deterministic engines as the appliance, but it runs them on the Licensor's server, not yours. Clause 3.2 describes the appliance you license; it does not describe this page. Use of the console creates no licence, no warranty and no agreement to supply, and is not a purchase.

13.2 Do not send it real client data. The console is for the supplied mock-ups, and for documents that are fictional or from which all information about any identifiable person or client has been removed. Do not paste or upload real policyholder, claimant, broker or client information, and in particular no information about anyone's health, injuries or criminal matters. If you want to try the engines on real documents, ask for an appliance and run it inside your own network, where nothing leaves. Anything you paste is processed on the Licensor's server to produce the result. When the console runs Step 3 (clause 8A), the working copy is held in memory on that server until 30 minutes after it was last used, and is then discarded. The Licensor's systems are designed so that it is not written to disk or logged, and the Licensor does not look at it or use it for any other purpose. If you send real personal data despite this clause, you are responsible for having the right to disclose it. Before the console runs a document you have edited or pasted, it asks you to confirm that it holds no real client or personal information; the supplied mock-ups run without that step.

13.3 Every document in the catalogue is a mock-up, and is labelled as one. The console offers several thousand documents across the classes of business written in the London Market — risk, premium and claims bordereaux, statements of value, aggregate returns, settlement advices, claim movements and first notifications of loss. Every one of them is fabricated by the Licensor. Each firm, insured, reference, premium, sum insured and loss in them is invented; none is a market document; none derives from any client's data; and none implies any relationship with, or statement about, any real firm. The console marks each one as a mock-up on the page and in anything you download from it.

They are fabricated on purpose, and the purpose is narrow. Each document is built to put the engines into one named condition — a clean file, a date column that reads two ways, a column where two offices used different conventions, a three-digit syndicate number, a notification with no cause of loss stated — and the console tells you which condition it is and what a correct engine does with it before you run it. That makes each one a test you can check rather than a demonstration you have to take on trust. It is the engine's behaviour that is being shown, never a claim about the market.

How the number is made. The catalogue is generated, not drafted file by file. There are 9 document types — six bordereau and return formats (risk, premium and claims bordereaux, statements of values, aggregate returns and settlement advices), CDR claim movements, ACORD ECOT claim movements and first notifications of loss. Each type has its own named conditions: 14 for each of the six bordereau and return formats, 12 for CDR claim movements, 14 for ECOT claim movements and 18 for first notifications, 128 in all. Each condition is built in each of 20 classes of business, in 2 variants: 128 × 20 × 2 = 5,120 documents. A document is built on request from its identifier by a fixed rule, so the same identifier always gives the same document. The figure counts combinations of type, condition, class and variant. It is not a count of distinct faults, of which there are 128 conditions including the clean ones, and it is not a claim about how much of the market the catalogue covers.

What this is not: it is not a corpus of real documents, not a benchmark, and not evidence of accuracy on your traffic. Clause 8 governs any figure taken from it. A document passing here says nothing about your own files beyond the fact that the engine applies the same rule to both.

13.3.1 Your own documents run through the same code. The engines hold no list of recognised samples and take no different path for a catalogue document than for anything else. Paste a fictional or fully anonymised record into the console, or better, run the appliance on your real documents inside your own network under clause 3, and the same deterministic checks and the same Step 3 corrections apply to it in the same way, with the same explanation of every format decision. On the hosted console, choosing a file from your own computer and starting from a blank template are both switched off, so that no real return is placed on the Licensor's server; both are available on a licensed appliance. Where a document is one the engines cannot read, they say so and refuse rather than returning a result; that too is the same for a catalogue document and for yours.

You are encouraged to try your own documents on a licensed or evaluation appliance, verify the results against what you know to be true, and send us your feedback at hello@apexdatarouting.co.uk — subject always to clause 13.2, which is about where you run them, not whether you may.

13.4 Acceptable use of the console. Runs are rate-limited per address so one visitor cannot exhaust it for the rest. You may not attempt to circumvent that limit; scrape, mirror or bulk-harvest the console or its catalogue; use it for production processing rather than evaluation; probe, penetration-test or attack it without the Licensor's prior written consent; or use it to build a competing product. The console is provided as is, with no availability commitment, and the Licensor may change, limit or withdraw it at any time without notice.

13.5 What the console counts and receives. Visits and clicks are counted per campaign link, with no cookies. Your IP address is held briefly in memory to apply the rate limit in clause 13.4 and is not kept in the Licensor's visit counts or written to the console's own logs; the hosting provider's network may record it in routine access logs, which are used only to run and secure the service. The console receives what you paste or type into it, which is used only to produce your result and is handled as clause 13.2 describes, and what you send through the enquiry form, which is used to reply to you and for nothing else. The console's privacy notice, linked from every page, gives the details, who else handles the data, and your rights.

Licensing enquiries: hello@apexdatarouting.co.uk