Service availability
Version 0.1 — 12 August 2026. Status: draft pending review by a Swiss lawyer.
The French version prevails: disponibilité.
1. We do not promise an uptime figure
There is currently no quantified availability commitment on ClaimTrace. No 99.9%, no 99.5%, no automatic service credit.
We would rather write it than let you guess it. A percentage displayed without a public measuring instrument and without an associated penalty is not a commitment: it is decoration. We will publish one on the day we can measure it and stand behind it financially.
This page therefore describes what actually exists.
2. What we do commit to
- Flagging degradation rather than hiding it. When a response is produced in degraded conditions — unreachable source, failing dependency, partial result — the response says so in its warnings field. We prefer an honestly incomplete answer to a smooth and false one.
- Not charging for what was not delivered. Refusals consume no credit (codes
402,403,429). If an outage attributable to us prevented you from using paid credits, we re-credit or refund them (see sales terms, art. 6). - Interface contract stability. The
v1response schema will lose no field, and no field will change meaning, without a new major version and reasonable notice. - Advance notice of planned work likely to interrupt the Service, by email, as soon as we know the date.
- Informing you of a major incident and of its resolution.
3. What the Service depends on
ClaimTrace reads the real web. Its availability therefore depends on factors outside our control:
| Dependency | Effect of an outage |
|---|---|
| Website of the entity queried | The fact cannot be verified: motivated unavailable response |
| Upstream search engine | Falls back to a secondary search, reduced coverage |
| AI model provider | Interpretation unavailable: the request fails rather than returning an approximation |
| Mapping services | Degraded geolocation, reduced discovery |
| Hosting, database | General unavailability |
| Payment provider | Purchases unavailable; the Service remains usable with existing credits |
A third-party source may disappear, close or change format without notice. That is not a defect of the Service: it is the nature of a product that reads sources it does not own.
4. Our rule of conduct during an outage
Faced with a failing dependency, our order of preference is constant:
- first, a correct answer;
- failing that, a motivated absence, explicitly flagged;
- never, a plausible fabricated value to fill the gap.
An empty answer can be detected and recovered from. An invented answer propagates.
5. Support
Support is by email on all plans, at the address in the legal notice. We do not advertise a contractual response time; we reply within a reasonable time, prioritising incidents that block production use.
Where possible, quote the request identifier from the response: it lets us find the processing.
6. Maintenance
Work is preferably carried out outside Swiss business hours. Urgent security fixes may be applied without notice.
7. What is still missing, and we know it
For honesty about the actual state of the Service:
- there is no public status page yet; incidents are communicated by email;
- there is no quantified commitment, hence no automatic service credit;
- usage and latency measurements are internal and not published.
These are open work items, not omissions. This page will be updated as they progress — and a quantified commitment will appear here only on the day it is measurable and enforceable.
Related documents: terms of service · sales terms · legal notice